-
Notifications
You must be signed in to change notification settings - Fork 41
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
svclb pod not returning SSL Certificates. #12
Comments
If all the |
More info for you:
|
You port-forward port's 43 port to localhost 7443 port and certificate works well. While in pod yaml there is no 43 container port declared: - containerPort: 15021
protocol: TCP
- containerPort: 8080
protocol: TCP
- containerPort: 8443
protocol: TCP
- containerPort: 15012
protocol: TCP
- containerPort: 15443
protocol: TCP
- containerPort: 15090
name: http-envoy-prom
protocol: TCP istio-ingressgateway service declared 443 to pod's 8443, so your pod ports and make it sync with those of service. |
@murphye , did you figure why this happened? I am facing the same issue, standard Istio install with |
@juniorz No. I have not tried this in a long time. You may want to try MetalLB. |
I am using k3d v4.2.0, but have narrowed down to this being a Klipper svclb issue. I am using the Istio proxy service, and port 80 is working fine. However when I enable SSL/TLS for routing to 443, I cannot connect properly because the SSL certificate is not being returned to the client.
I am starting my k3d cluster with this command:
k3d cluster create --registry-create --k3s-server-arg '--no-deploy=traefik' -p "9080:80@loadbalancer" -p "9443:43@loadbalancer" istio-workshop
If I connect to the
istio-ingressgateway
directly, it's fine. If I connect tosvclb-istio-ingressgateway
that is where the problem begins.Connecting to
svclb-istio-ingressgateway
withopenssl
. No certificate returned. Error.Connecting to
istio-ingressgateway
withopenssl
. Certificate returned. Correct.Logs from
svclb-istio-ingressgateway
.svclb-istio-ingressgateway
pod spec.istio-ingressgateway
pod spec.The text was updated successfully, but these errors were encountered: