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.

Sign up for GitHub

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

Jump to bottom

Set prefix list through IngressClassParams #3859

Open
gdlx opened this issue Sep 23, 2024 · 2 comments · May be fixed by #3860
Open

Set prefix list through IngressClassParams #3859

gdlx opened this issue Sep 23, 2024 · 2 comments · May be fixed by #3860
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.

Comments

@gdlx
Copy link

gdlx commented Sep 23, 2024 •
edited
Loading

Is your feature request related to a problem?
I'm providing an ingress class to my users to deploy ALBs dedicated to inbound traffic from an external CDN whose outbound IPs are listed in a prefix list, but I currently need to ask them to add the alb.ingress.kubernetes.io/security-group-prefix-lists annotation on every CDN ingress.

Describe the solution you'd like
I'd like to be able to set the prefix list in the IngressClassParams resource to avoid having to set it on every ingress using this ingress class.

Describe alternatives you've considered
My current workaround is to patch every ingress using this ingress class with Kyverno to add the alb.ingress.kubernetes.io/security-group-prefix-lists annotation.
@gdlx gdlx linked a pull request Sep 23, 2024 that will close this issue
Open
6 tasks
@shraddhabang
Copy link
Collaborator

Thank you for the contribution. We will review this soon.

@shraddhabang shraddhabang added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 25, 2024
@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 Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add PrefixListsIDs field to IngressClassParams gdlx/aws-load-balancer-controller
4 participants
@gdlx @shraddhabang @k8s-ci-robot @k8s-triage-robot