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

operator: moved CRD to subchart #1560

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

AndrewChubatiuk
Copy link
Contributor

  • moved operator CRD to subchart
  • replaced flag crd.enabled to crds.plain, which instead of disabling CRDs templating, changes a mode in which CRDs should be rendered: as plain text CRDs or as templates

@github-actions github-actions bot added k8s-stack k8s-stack helm chart related issue operator operator helm chart related issue labels Oct 4, 2024
Copy link
Contributor

@zekker6 zekker6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you describe some benefits or issues which new type of CRDs deployment solves?
I'm not sure if I completely understand what exactly this PR addresses.

Comment on lines -31 to +35
crd:
# -- Enables CRD creation and management. With this option, if you remove this chart, all CRD resources will be deleted with it.
create: true
crds:
# -- check if plain or templated CRDs should be created.
# with this option set to `false`, all CRDs will be rendered from templates.
# with this option set to `true`, all CRDs are immutable and require manual upgrade.
plain: false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like this change makes it impossible to disabled CRDs deployment completely. Is that expected?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, next step is CRD management removal from k8s-stack

@AndrewChubatiuk
Copy link
Contributor Author

Could you describe some benefits?

single place, with CRDs instead of having them both in operator and k8s stack managed differently (as templates in operator and as plain CRDs in k8s-stack)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s-stack k8s-stack helm chart related issue operator operator helm chart related issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants