You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How do you enable SSL Passthrough in the ingress deployment #6403
Can't answer your question, but I can offer a workaround:
Disable ingress addon minikube addons disable ingress
If you are using Helm 3, add stable repo helm repo add stable https://kubernetes-charts.storage.googleapis.com/
Install nginx ingress controller with "ssl-passthrough" enabled
I also get the feeling like you are trying to run Strimzi kafka on minikube with ingress external like I did, so here's a working example just in case:
Install ingress controller like previously described.
Install strimzi operator.
Apply a kafka cluster configuration with ingress external, TLS and some user:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Reacted by Yang Hanlin, Jhonatan Macazana, JMatt Peterson, Kingdon Barrett, chrimutz, Rex Wu, kristjanJak, Richard Morel⁺, Alexey Markevich, Yun Hao and 4 more
Activity
avif commentedon Feb 7, 2020
Can't answer your question, but I can offer a workaround:
Disable ingress addon
minikube addons disable ingressIf you are using Helm 3, add stable repo
helm repo add stable https://kubernetes-charts.storage.googleapis.com/Install nginx ingress controller with "ssl-passthrough" enabled
You could do this without Helm too, but you get the point.
Ref
avif commentedon Feb 7, 2020
I also get the feeling like you are trying to run Strimzi kafka on minikube with ingress external like I did, so here's a working example just in case:
Install ingress controller like previously described.
Install strimzi operator.
Apply a kafka cluster configuration with ingress external, TLS and some user:
Extract ca-cert & my-user cert:
Create truststore & keystore (use any or no password):
Use the following configs when connecting to the cluster (use 443 port):
tstromberg commentedon Mar 18, 2020
If there are any ingress experts in the house, it'd be wonderful to see a tutorial written up for this similar to:
https://minikube.sigs.k8s.io/docs/tutorials/nginx_tcp_udp_ingress/
fejta-bot commentedon Jun 16, 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot commentedon Jul 16, 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with
/remove-lifecycle rotten.Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Huskehhh commentedon Jul 29, 2021
If you find yourself in this situation, I was able to solve it with minikube via...
minikube kubectl -- patch deployment -n ingress-nginx ingress-nginx-controller -p='{"spec":{"template":{"spec":{"containers":[{"name":"controller","args":["/nginx-ingress-controller","--ingress-class=nginx","--configmap=$(POD_NAMESPACE)/ingress-nginx-controller","--report-node-internal-ip-address","--tcp-services-configmap=$(POD_NAMESPACE)/tcp-services","--udp-services-configmap=$(POD_NAMESPACE)/udp-services","--validating-webhook=:8443","--validating-webhook-certificate=/usr/local/certificates/cert","--validating-webhook-key=/usr/local/certificates/key","--enable-ssl-passthrough"]}]}}}}'Which just patches the deployment of the ingress-nginx-controller with an extra argument
--enable-ssl-passthrough.It seems it also auto-redeploys after a patch, so it should pop back up fairly quick after the patch!
christianh814 commentedon Nov 8, 2022
I've done it using
jsontype patching that's a little easieretimoshenko commentedon Feb 27, 2024
You can just enable it from values.yaml