Publish helm charts #1791
Open
Publish helm charts #1791
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes two significant changes to the operator helm chart release process: - The Operator Chart is now published to *both* docs.altinity.com and helm.altinity.com when new releases are created. (NB: The release name must match the release tag or the release workflow will fail) - The Operator Chart is renamed from `altinity-clickhouse-operator` to `clickhouse-operator` which is cleaner when next to a repo named `altinity`. Because of the way that Chart Releaser works, only *new* releases are merged with the existing helm index.yaml from helm.altinity.com. For the new workflow to work: - An actions variable `HELM_GITHUB_REPOSITORY` must exist and point to the `helm-charts` repository. - An actions secret `HELM_GITHUB_TOKEN` must exist and contain a GitHub PAT with read/write permissions on the `helm-charts` repository.
Signed-off-by: Josh Lee <[email protected]>
Slach
reviewed
Aug 14, 2025
There was a problem hiding this comment.
Do you have access to add new secrets into clickhouse-operator ? did you ask @alex-zaitsev or @sunsingerus about adding it?
If I understood correctly we still publish to https://docs.altinity.com/clickhouse-operator but also publish into https://helm.atlinity.com?
I don't have access to add secrets, I'll reach out and ask. Yes, you're correct, for now this publishes the chart to both locations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes two significant changes to the operator helm chart
release process:
helm.altinity.com when new releases are created. (NB: The release
name must match the release tag or the release workflow will fail)
altinity-clickhouse-operatortoclickhouse-operatorwhich is cleaner when next to a repo namedaltinity.Because of the way that Chart Releaser works, only new releases are
merged with the existing helm index.yaml from helm.altinity.com.
For the new workflow to work:
HELM_GITHUB_REPOSITORYmust exist and point tothe
helm-chartsrepository.HELM_GITHUB_TOKENmust exist and contain a GitHubPAT with read/write permissions on the
helm-chartsrepository.Important items to consider before making a Pull Request
Please check items PR complies to:
next-releasebranch, not intomasterbranch1. More info--
1 If you feel your PR does not affect any Go-code or any testable functionality (for example, PR contains docs only or supplementary materials), PR can be made into
masterbranch, but it has to be confirmed by project's maintainer.