aws-iam-authenticator
aws-iam-authenticator copied to clipboard
[Feature request]: official helm chart for aws-iam-authenticator
What would you like to be added?
- Update aws-iam-authenticator helm chart from the "old" https://github.com/helm/charts/tree/master/stable/aws-iam-authenticator (from https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/198)
- Publish to an official OCI repo (https://gallery.ecr.aws/ for instance)
Why is this needed?
The old helm chart is not maintained anymore and the repo it is published has long been discontinued
Anything else we need to know?
No response
/assign omerap12
Hey, @joaocc . I want to publish the chart to Artifact hub under the Kubernetes-sigs publisher. (https://artifacthub.io/packages/search?org=kubernetes-sigs&sort=relevance&page=1) Can you help with that? or do you want just to have the chart under this repo? Same with ECR public Gallery - I thought to create a repository and push images under that repository (using the github actions we already have)
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@omerap12 sorry for the delay in answering. Not sure I understand your question, as I don't have any privileges on any of the projects (just a simple potential user of the tech :))
@omerap12
(https://artifacthub.io/packages/search?org=kubernetes-sigs&sort=relevance&page=1) Can you help with that? or do you want just to have the chart under this repo?
Both are great for me. Keep the chart source in the repo for changes and have a helm repo from which to pull.
FWIW, this helm release action might help. https://github.com/helm/chart-releaser-action
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten