We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
i'm using jenkins by deploying the service type as loadbalancer.
I want to apply TLS, but I can't find apply options at values.yaml
I am not considering ingress because it is not available on my env
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE jenkins LoadBalancer 10.109.101.163 211.39.158.247 80:31538/TCP 148d jenkins-agent ClusterIP 10.98.63.81 <none> 50000/TCP 148d
NAME TYPE DATA AGE jenkins Opaque 2 148d jenkins-tls-secret kubernetes.io/tls 2 52m
k describe pod -n jenkins jenkins-0 |grep -i jenkins-tls Return none
- Helm: - Kubernetes:
jenkins-5.3.1
1. 2. 3. ...
No response
The text was updated successfully, but these errors were encountered:
TLS would be done under ingress, loadbalancer should just be for the inbound agent port if you're using that and exposing it outside the cluster.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
i'm using jenkins by deploying the service type as loadbalancer.
I want to apply TLS, but I can't find apply options at values.yaml
I am not considering ingress because it is not available on my env
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE jenkins LoadBalancer 10.109.101.163 211.39.158.247 80:31538/TCP 148d jenkins-agent ClusterIP 10.98.63.81 <none> 50000/TCP 148d
NAME TYPE DATA AGE jenkins Opaque 2 148d jenkins-tls-secret kubernetes.io/tls 2 52m
k describe pod -n jenkins jenkins-0 |grep -i jenkins-tls
Return none
Version of Helm and Kubernetes
Chart version
jenkins-5.3.1
What happened?
What you expected to happen?
No response
How to reproduce it
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: