Skip to content
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

Add OperatorConfig option to indicate deployment with OLM #547

Merged
merged 4 commits into from
Jun 30, 2023

Conversation

burmanm
Copy link
Contributor

@burmanm burmanm commented Jun 30, 2023

What this PR does:
Alternative approach to #545 , instead of polling the Kubernetes API if we actually deployed with the ServiceAccount, we use OperatorConfig to modify the OLM deployment to indicate deployment scenario.

This reduces Role requirements for the operator as well as call to api-server (even if cached read).

controller_manager_config.yaml receives this additional line:

olmDeployment: false

Which is set to true in the bundle creation. We still add nonroot Role & required ServiceAccounts

Which issue(s) this PR fixes:
Fixes #541

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CHANGELOG.md updated (not required for documentation PRs)
  • CLA Signed: DataStax CLA

burmanm added 4 commits June 30, 2023 12:44
…fig. If cass-operator has this configuration parameter set, it will set a default serviceAccount to cass-operator-cassandra-default-sa
@burmanm burmanm requested a review from a team as a code owner June 30, 2023 10:07
@burmanm burmanm merged commit 640a4db into k8ssandra:master Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

datastax/cass-config-builder pull error on OCP
2 participants