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

Helm chart versioning #22

Open
oraNod opened this issue Sep 19, 2024 · 3 comments
Open

Helm chart versioning #22

oraNod opened this issue Sep 19, 2024 · 3 comments
Assignees

Comments

@oraNod
Copy link
Contributor

oraNod commented Sep 19, 2024

Current discussion ongoing in the forum about versioning the helm chart: https://forum.ansible.com/t/awx-operator-helm-versioning/8228

The purpose of this issue is to track the discussion so we have a link to the outcome captured somewhere in this repo. If you have comments or input on the versioning, please add your thoughts to the forum topic.

This also relates to #7 but that is specific to the borked ci check, which is something we can fix after we figure out the new versioning.

@oraNod oraNod self-assigned this Sep 19, 2024
@oraNod
Copy link
Contributor Author

oraNod commented Oct 15, 2024

Poll for versioning scheme here: https://forum.ansible.com/t/awx-operator-helm-versioning/8228/4

@schen1
Copy link
Collaborator

schen1 commented Oct 16, 2024

An initial tag was created: https://github.com/ansible-community/awx-operator-helm/releases/tag/24.42.0 which resolves the CI pipeline.

However, we need to map the appVersion correctly so that 24.42.X tag from the helm chart can clone the 2.19.X tags from the awx-operator.

Future versions of the helm chart (e.g. 25.3.X) should map to new versions of awx-operator only and not to 2.19.X.

Any ideas on how to do that is welcome.

@timhaak
Copy link

timhaak commented Nov 26, 2024

Hi

Is there anywhere where we can see a list of versions? And their map to the wax-operator version.

It would help quite a bit.

If it could be added to https://artifacthub.io/, I imagine it would also help quite a few people.

Thanks

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 a pull request may close this issue.

3 participants