-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Add ingress resource, use ClusterIP by default #1562
Conversation
can you please add this little config to ingress object too: {{- if .Values.ingress.ingressClassName }}
ingressClassName: {{ .Values.ingress.ingressClassName }}
{{- end }}
rules:
... ? |
This needs to be rebased, also hoping that @ilpianista has some time to review it. |
@den-is I added an option to set IngressClassName, custom annotations, TLS, and some standard precautions against different Kubernetes API versions. |
Set ClusterIP service type for Hub and Router components, NodePort could be set explicitly, but the default is ClusterIP. Add enabled by default ingress resource, which exposes either Hub or Router service. In the case of LoadBalancer or NodePort set explicitly, you shall turn off ingress explicitly as well. To turn off: --set ingress.enabled=false End-user shall supply the hostname for the ingress. There is an option to use an empty host instead. Be aware of the consequences of accepting traffic from all hosts. Fixes SeleniumHQ#1546
@diemol I rebased. Awaiting for review. |
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 am going to merge this and release a new chart so we can use these changes, hopefully you can be around as my helm is a bit rusty, in case issues are reported.
Thank you, @lorantalas!
@diemol if the issue is reported please ping me in the comments. |
Description
Set ClusterIP service type for Hub and Router components, NodePort could be set explicitly, but the default is ClusterIP.
Add enabled by default ingress resource, which exposes either Hub or Router service.
In the case of LoadBalancer or NodePort set explicitly, you shall turn off ingress explicitly as well.
To turn off:
--set ingress.enabled=false
End-user shall supply the hostname for the ingress. There is an option to use an empty host instead.
Be aware of the consequences of accepting traffic from all hosts.
Motivation and Context
See issue #1546.
Types of changes
Checklist