Kong Operator Charts Release Strategy

[tao12345666333]

Problem Statement

Currently, our charts-sync.yaml workflow automatically syncs the charts/kong-operator directory to the Kong/charts repository whenever changes are pushed to the main branch. While this keeps both repositories in sync, it creates challenges for the release process.

The Issue: When we want to release a new version of the kong-operator Helm chart in Kong/charts that only contains chart configuration changes (e.g., values.yaml, templates, bug fixes), we're forced to include any CRD updates that have been synced from the main branch, even if those CRDs are not ready for release.

Proposed Solution

proposal: https://docs.google.com/document/d/1D93Uk06OUIybIhnZnbMR6t7u8RMzFN6bd2cEb4dbs9g/edit?usp=sharing

Additional Information

...

Acceptance Criteria