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 helm prefix to helm chart artifact #133

Closed
wants to merge 2 commits into from
Closed

Conversation

rajatjindal
Copy link
Member

@rajatjindal rajatjindal commented Mar 6, 2024

fixes #124

Copy link

github-actions bot commented Mar 6, 2024

This PR now has an image available for testing:

  ttl.sh/spoopy-operator-pr-133:24h

@rajatjindal rajatjindal requested a review from vdice March 6, 2024 11:54
@@ -120,7 +120,7 @@ jobs:
echo "CHART_VERSION=$(echo -n ${{ github.ref_name }} | sed -rn 's/(v)?(.*)/\2/p')" >> $GITHUB_ENV
else
# TODO: swap '0.0.0' with '$(git describe --tags --abbrev=0 | sed -rn 's/(v)?(.*)/\2/p')' when we have our first tag
echo "CHART_VERSION=0.0.0-${{ env.APP_VERSION }}" >> $GITHUB_ENV
echo "CHART_VERSION=helm-0.0.0-${{ env.APP_VERSION }}" >> $GITHUB_ENV
Copy link
Contributor

@vdice vdice Mar 6, 2024

Choose a reason for hiding this comment

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

Unfortunately, the helm CLI is strict about chart versions being valid semver (eg must start with [0-9]+.[0-9]+.[0-9]+ and can optionally include prerelease/build metadata as we attach here), so this would break some helm install modes. (See also https://github.com/spinkube/spin-operator/blob/main/Makefile#L139-L142)

I was assuming from #124 (comment) that the ask was to rename the published chart name itself to something like helm-spin-operator... but I could be misunderstanding.

Copy link
Contributor

Choose a reason for hiding this comment

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

#124 (comment) was asking for the helm releases to be explicit in the image list - because right now it's not clear what is software bits and what is helm bits unless you happen to know the schema

Copy link
Contributor

@michelleN michelleN left a comment

Choose a reason for hiding this comment

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

Would it be possible to instead move chart artifacts to a different repository in ghcr https://ghcr.io/spinkube/spin-operator-chart ?

I want to be able to install for example: ghcr.io/spinkube/spin-operator-chart:0.0.1

@endocrimes
Copy link
Contributor

that's indeed an option

Signed-off-by: Rajat Jindal <rajatjindal83@gmail.com>
Signed-off-by: Rajat Jindal <rajatjindal83@gmail.com>
@rajatjindal
Copy link
Member Author

rajatjindal commented Mar 8, 2024

I did some tests for the behavior here:

for ghcr.io/spinkube/spin-operator-chart:0.0.1, I think we will have to rename the chart itself.

Instead we might be able to doghcr.io/spinkube/helm/spin-operator:0.0.1 or ghcr.io/spinkube/charts/spin-operator:0.0.1

@vdice what do you think?

@rajatjindal rajatjindal marked this pull request as ready for review March 8, 2024 09:26
@vdice
Copy link
Contributor

vdice commented Mar 8, 2024

I'd be in favor of ghcr.io/spinkube/charts/spin-operator:0.0.1 👍

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.

prefix chart artifacts with helm-
4 participants