Skip to content

Remove CRD Checking on Start of the Operator #1054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
csviri opened this issue Mar 21, 2022 · 1 comment
Closed

Remove CRD Checking on Start of the Operator #1054

csviri opened this issue Mar 21, 2022 · 1 comment
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@csviri
Copy link
Collaborator

csviri commented Mar 21, 2022

Currently on startup Operator checks if the CRD is present on the cluster. This is because it could be hard to recognize the real problem based on the error message from the client. On the other hand it requires read access on the cluster for the custom resource, what is not desirable in general.

@csviri csviri self-assigned this Mar 21, 2022
@csviri csviri added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 21, 2022
@csviri csviri linked a pull request Mar 21, 2022 that will close this issue
@csviri
Copy link
Collaborator Author

csviri commented Mar 23, 2022

Set default to false for now.

@csviri csviri closed this as completed Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant