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

[Feature request]: official helm chart for aws-iam-authenticator #704

Open
joaocc opened this issue Apr 1, 2024 · 5 comments
Open

[Feature request]: official helm chart for aws-iam-authenticator #704

joaocc opened this issue Apr 1, 2024 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@joaocc
Copy link

joaocc commented Apr 1, 2024

What would you like to be added?

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

@joaocc joaocc added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 1, 2024
@omerap12
Copy link

/assign omerap12

@omerap12
Copy link

omerap12 commented Apr 27, 2024

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)

@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2024
@joaocc
Copy link
Author

joaocc commented Jul 26, 2024

@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 :))

@jmcgrath207
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

5 participants