-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Adding support of ingressClassParams in helm charts #2478
Conversation
Hi @haouc. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2478 +/- ##
==========================================
- Coverage 53.38% 53.38% -0.01%
==========================================
Files 140 140
Lines 7985 7988 +3
==========================================
+ Hits 4263 4264 +1
- Misses 3405 3406 +1
- Partials 317 318 +1 ☔ View full report in Codecov by Sentry. |
@@ -173,6 +173,7 @@ The default values set by the application itself can be confirmed [here](https:/ | |||
| `serviceAccount.name` | Service account to be used | None | | |||
| `terminationGracePeriodSeconds` | Time period for controller pod to do a graceful shutdown | 10 | | |||
| `ingressClass` | The ingress class to satisfy | alb | | |||
| `ingressClassParams.name` | The created ingressClassParams object name (referred in ingressClass) | "" | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: "" not needed
@@ -87,6 +87,11 @@ enableCertManager: false | |||
# ingresses without ingress class annotation and ingresses of type alb | |||
ingressClass: alb | |||
|
|||
# The ingressClassParams the ingress class refers to and enforce settings for a set of Ingresses when using with ingress Controller. | |||
ingressClassParams: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not create IngressClassParams resource and refer from the IngressClass instead? users will be able to specify the ingress class params spec during chart installation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since the params spec can be user specific and vary, would that be better to let users create ingress class params resources and just refer their name in charts during install/upgrade? That could be easier to maintain and less error-prone?
@@ -87,6 +87,11 @@ enableCertManager: false | |||
# ingresses without ingress class annotation and ingresses of type alb | |||
ingressClass: alb | |||
|
|||
# The ingressClassParams the ingress class refers to and enforce settings for a set of Ingresses when using with ingress Controller. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: please use the following format for comments
# ingressClassParams specifies the IngressClassParams ...
@@ -7,4 +7,7 @@ metadata: | |||
{{- include "aws-load-balancer-controller.labels" . | nindent 4 }} | |||
spec: | |||
controller: ingress.k8s.aws/alb | |||
{{- if or .Values.ingressClassParams.create .Values.ingressClassParams.name }} | |||
{{ include "aws-load-balancer-controller.ingressClassParameters" . }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets include the spec directly instead of using a template function
/ok-to-test |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haouc, kishorj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…2478) * Adding support of ingressClassParams in helm charts * Update charts to let users to create ingressClassParams with specs * Simplying the spec in values yaml * Adding support for customer's ingressClassParams * Using values fields directly instead of function * eks1.19 doesn't allow null spec and need move if check out from spec block.
Issue
Fixes #2328
Description
We want to add support for ingressClassParams in ingressClass spec parameters in helm charts.
The ingressClassParams was added into values and ingressClass chart. Charts version and README were also updated. Local tests were done from the charts by
helm install
. The namespaceSelector and group.name were tested with 2048 game ingress.Update:
Tested for the use cases:
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯