Hello! First off, as a former AWX developer, thank you for your work keeping in keeping the project (or something close to it) usable and updated for the general public. It means a lot to me, to see my work still accessible and usable by the greater community and I appreciate it!
Issues are disabled on the ascender-operator repo, or I would open this there instead.
Essentially, I wanted to ask if you'd be open to a PR on that repo which enables publishing a helm repo (i.e. from .helm/starter) to GitHub Pages during release.
Of course, with something like Flux, it's possible to just point to the git repo and install the helm chart to a cluster from there. But nevertheless, I think publishing an official helm repo would be nice and I suspect not too much work (I believe there are official Github Actions to automate almost all of it).
Happy to work out details with you if you have thoughts on it :) - Theoretically it could also be maintained as a separate repo (I think upstream does this nowadays, though I haven't followed anything upstream in about a year). But I would say probably unless there's a reason not to, maybe it's easier to start with just making it part of the release GHA workflow in the existing repo.
Hello! First off, as a former AWX developer, thank you for your work keeping in keeping the project (or something close to it) usable and updated for the general public. It means a lot to me, to see my work still accessible and usable by the greater community and I appreciate it!
Issues are disabled on the ascender-operator repo, or I would open this there instead.
Essentially, I wanted to ask if you'd be open to a PR on that repo which enables publishing a helm repo (i.e. from
.helm/starter) to GitHub Pages during release.Of course, with something like Flux, it's possible to just point to the git repo and install the helm chart to a cluster from there. But nevertheless, I think publishing an official helm repo would be nice and I suspect not too much work (I believe there are official Github Actions to automate almost all of it).
Happy to work out details with you if you have thoughts on it :) - Theoretically it could also be maintained as a separate repo (I think upstream does this nowadays, though I haven't followed anything upstream in about a year). But I would say probably unless there's a reason not to, maybe it's easier to start with just making it part of the release GHA workflow in the existing repo.