-
Notifications
You must be signed in to change notification settings - Fork 4
feat: add configurability of external dependencies and their configma… #10
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
base: main
Are you sure you want to change the base?
Changes from all commits
46ecc63
e80503f
3422042
b06d736
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -4,10 +4,15 @@ kind: Ingress | |||||
| metadata: | ||||||
| name: {{ .Release.Name }}-http-lb | ||||||
| namespace: {{ .Release.Namespace }} | ||||||
| {{- with .Values.loadbalancer.http.annotations }} | ||||||
| annotations: | ||||||
| {{ toYaml . | nindent 4 }} | ||||||
| {{- end }} | ||||||
| spec: | ||||||
| ingressClassName: nginx | ||||||
| rules: | ||||||
| - http: | ||||||
| ingressClassName: {{ .Values.loadbalancer.http.ingressClassName | default "nginx" }} | ||||||
| rules: | ||||||
| - host: {{ .Values.loadbalancer.http.host | default "\"\"" }} | ||||||
|
Cyanopus marked this conversation as resolved.
|
||||||
| - host: {{ .Values.loadbalancer.http.host | default "\"\"" }} | |
| - host: {{ .Values.loadbalancer.http.host | default """" }} |
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 a lot for the contribution and for aiming to add SSL/TLS support for HTTP ingress with host and certificate configuration. We really appreciate it.
We have already merged a number of related changes internally (external Redis, external Kafka, LB annotations with user-wins merge, provider-specific ingress updates), so parts of this PR now overlap. To keep history clean and the scope clear, could you please resubmit a focused PR just for the HTTP TLS feature?
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,19 @@ | ||
| {{- if and (eq .Values.loadbalancer.type "nginx") .Values.loadbalancer.mqtt.enabled }} | ||
| {{- if and (eq .Values.loadbalancer.type "nginx") .Values.loadbalancer.mqtt.enabled -}} | ||
| {{- $serviceType := .Values.loadbalancer.mqtt.type | default "LoadBalancer" }} | ||
| apiVersion: v1 | ||
| kind: Service | ||
| metadata: | ||
| name: {{ .Release.Name }}-mqtt-lb | ||
| namespace: {{ .Release.Namespace }} | ||
| {{- with .Values.loadbalancer.mqtt.annotations }} | ||
| annotations: | ||
| {{ toYaml . | nindent 4 }} | ||
| {{- end }} | ||
|
Comment on lines
+8
to
+11
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don’t see There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will add. |
||
| spec: | ||
| type: LoadBalancer | ||
| type: {{ $serviceType }} | ||
| {{- if or (eq $serviceType "NodePort") (eq $serviceType "LoadBalancer") }} | ||
| externalTrafficPolicy: Local | ||
| {{- end }} | ||
| selector: | ||
| app: {{ include "tbmq.node.label" . }} | ||
| ports: | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,3 +1,4 @@ | ||||||
| {{- if and (empty .Values.postgresql.existingConfigMap) .Values.postgresql.enabled }} | ||||||
|
||||||
| {{- if and (empty .Values.postgresql.existingConfigMap) .Values.postgresql.enabled }} | |
| {{- if and (empty .Values.postgresql.existingConfigMap) (default true .Values.postgresql.enabled) }} |
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.
I don’t see
loadbalancer.http.ingressClassNamein values.yaml, but the template reads it. Could you share why we need to make the class name configurable here?Today we hardcode the class per provider (nginx → nginx, Azure → azure/application-gateway, GCP → gce, AWS → ALB via annotations). This keeps provider files simple and avoids an extra, undocumented knob.
If the goal is to support a different Ingress controller/class (e.g., a custom NGINX class, Traefik, or another AGIC class), can you add a brief use case? With that context we can either:
Happy to go with whatever best matches your use case — just want to keep the chart predictable and well-documented.
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.
The main reason is that you can have many ingress controllers in the kubernetes cluster, for instance we have one for the management and one for external exposure. ingress ClassName is different if you have separate controllers. Most of times today, this is the reality and most production clusters are like that.