Aws-iam-authenticator: Helm Chart

Created on 28 Jan 2019 · 10Comments · Source: kubernetes-sigs/aws-iam-authenticator

I've created a PR for a helm chart to install the daemonset. This is pretty directly taken from https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/master/example.yaml and just turned into a chart.

This issue is to:

check that me doing this is fine
give anyone who knows more about the manifests a chance to review that PR or make future alterations to the chart
act as a pointer for anyone who finds this repo and is looking for a helm chart for it

lifecyclrotten

Source

plumdog

All 10 comments

Seems like it's already been merged, as things progress will you be maintaining it?

christopherhein on 20 Apr 2019

Hi @christopherhein,

Indeed, the chart is now merged - see https://github.com/helm/charts/tree/master/stable/aws-iam-authenticator - and can be installed with helm install stable/aws-iam-authenticator.

I'm listed as a maintainer in the Chart.yaml metadata, so I'll get notified when anyone opens a PR to change the chart. But I don't have any plans to monitor aws-iam-authenticator itself for changes that I think would require a change to the chart. I guess if someone creates an issue about it in https://github.com/helm/charts or here and mentions me, I'd be happy to take a look.

In short: I'll try my best at doing reactive maintenance on the chart, but I have no plans to do proactive maintainance.

plumdog on 23 Apr 2019

Okay, good to know. Main reason I ask is as of last week we released the 0.4.0 release, which has a new Docker registry and a couple changed flags.

christopherhein on 23 Apr 2019

I would love to see this maintained - if I had the bandwidth I would chip in, but just wanted to say I appreciate the initial effort!

austince on 8 Jul 2019

👍1

This was my concern as well. Potentially moving the chart into the project would help.

christopherhein on 8 Jul 2019

👍1

Per https://github.com/helm/charts/issues/17126, @nckturner is now a maintainer of the chart in stable. I suspect this will essentially supersede this issue.

plumdog on 15 Sep 2019

👍1

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 14 Dec 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 13 Jan 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 12 Feb 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.