aws-load-balancer-controller icon indicating copy to clipboard operation
aws-load-balancer-controller copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

NLB Certificates Discovery

Open sergeyshevch opened this issue 1 year ago • 5 comments

Is your feature request related to a problem? It will be great to have ACM certificates discovery for kind:Service. In my case, I have multiple clusters in different accounts. I want to specify some annotation with host name and then controller can select appropriate certificate with same logic as for ALB https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.5/guide/ingress/cert_discovery/

Describe the solution you'd like

Some annotation like service.beta.kubernetes.io/aws-load-balancer-ssl-domain: rest.mycompany.com,second-domain.mycompany.com

Describe alternatives you've considered

sergeyshevch avatar May 23 '23 16:05 sergeyshevch

/kind feature

we currently only have it for ALB, but good to extend to NLB. we welcome PRs for this feature :D

M00nF1sh avatar May 24 '23 22:05 M00nF1sh

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-triage-robot avatar Jan 21 '24 04:01 k8s-triage-robot

/remove-lifecycle stale

sergeyshevch avatar Jan 21 '24 15:01 sergeyshevch

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-triage-robot avatar Apr 20 '24 16:04 k8s-triage-robot

/remove-lifecycle stale

sergeyshevch avatar Apr 21 '24 10:04 sergeyshevch