Aws-load-balancer-controller: Add official chart to the kubernetes/charts repo

Created on 11 Apr 2018 · 8Comments · Source: kubernetes-sigs/aws-load-balancer-controller

Add an official chart to the kubernetes/charts repo. I'd rather install the chart the native way using helm install stable/alb-ingress (like helm installstable/nginx-ingress) than installing a plugin for helm.

kinfeature lifecyclrotten

Source

sean-krail

👍12

Most helpful comment

I can open a kubernetes/charts PR, I'm just not sure if there are any legal considerations that need to be taken with copying the alb-ingress-controller-helm directory over. It'll also require updates to the release process which would have to be addressed by this repo's owners.

rifelpet on 19 Jul 2018

👍2

All 8 comments

Any chance this could happen before 1.0?

sstarcher on 19 Jul 2018

rifelpet on 19 Jul 2018

👍2

The AWS ALB Ingress Controller is now for two months in the Helm Charts Incubator repository. It would be nice if the AWS ALB Ingress Controller Chart could be promoted to the Helm Chart Stable repository.

Jeeppler on 18 Feb 2019

It looks like its just a matter of promoting the chart using the documented process in charts repo:

https://github.com/helm/charts/blob/master/PROCESSES.md#promoting-a-chart-from-incubator-to-stable

rifelpet on 18 Feb 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 19 May 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 18 Jun 2019

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 18 Jul 2019

@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.