You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The decision regarding how to manage Custom Resource Definitions (CRDs) within the chart structure is critical for ensuring smooth deployment and maintenance of registry-operator.
We need to determine the most efficient and user-friendly approach for handling CRDs within our Helm chart structure for the registry-operator project.
Pros: Simplifies chart structure, Easier to maintain and deploy as a single unit, Ensures CRDs are tightly coupled with the main chart.
Cons: Limited flexibility for managing CRDs independently, Potential conflicts with other resources in the chart directory, CRDs are not automatically upgraded with chart upgrades.
Ask users to manually install CRDs
Pros: Minimal chart complexity, Provides flexibility for users to manage CRDs according to their preferences, Allows for easier integration with existing workflows.
Cons: Increases burden on users, Potential for errors or inconsistencies in CRD installation, Lack of control over CRD versions and updates.
The text was updated successfully, but these errors were encountered:
I want a chart for the CRDs, manually installation won't be efficient.
I support separate CRDs chart, it enables granular access control for custom resources, enhancing security and compliance. Moreover, we don't have to bump up CRDs chart while only small changes in operator are made and the upgrade procedure is safer.
There is also Argo CD which is using crds folder in templates folder. This enables templating and upgradeability.
That said, I think we should start with crds folder in main helm chart repo. It's the most "working out of the box" solution and Helm is natively recognizing this as place for CRDs. When we run into limitations with this approach, then we can consider other options.
Context and Problem Statement
The decision regarding how to manage Custom Resource Definitions (CRDs) within the chart structure is critical for ensuring smooth deployment and maintenance of
registry-operator
.We need to determine the most efficient and user-friendly approach for handling CRDs within our Helm chart structure for the registry-operator project.
Considered Options
Create separate CRD chart and add it as a dependency to main chart (see Helm Best Practices - Custom Resource Definitions)
Add CRDs to
crd
directory in the main chart (see Helm Best Practices - Custom Resource Definitions)Ask users to manually install CRDs
The text was updated successfully, but these errors were encountered: