-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Communication between pods should happen through SSL on Openshift/K8S when I set "secured"service annotation to true #1141
Comments
That doc is specific to the load balancer not service discovery. Do you have an https port defined in your service resource? |
Yes I have it and the name is "main". I also configured spring cloud discovery to use main as primary port with the appropriate configuration. I also tried renaming that port in "Https". I hacked that class reading the secured annotation value and it works but this is just a bad patch and I do not want to put that in production. |
Can you tell me how you are using the discovery client to make the request? |
I'm using these deps:
The rest call is executed using Feign. The client spring boot service has this configuration:
this is the serice definition of the target service to be called with https
Let me know if I can give you more info. F |
Thanks. How are you making the http request to the service? |
Using feign
|
Would you be interested in submitting a PR? |
Of course, I'm going to do that. Thank you. |
HI, do you know approximatively when the spring-cloud-kubernetes version 2.1.6 (that should contains this fix) will be pushed on official maven repositories? thank you. f |
@fgapito you can find tentative release dates here https://github.com/spring-cloud/spring-cloud-release/milestones |
Hi, I tought it was DONE in 2021.0.5 but it seems not. Did something go wrong or should I wait for 2021.0.6? |
2021.0.5 was released on November 3rd, we didn't merge this till December 6th it will be included in 2021.0.6 |
Hi,
I'm facing with this possible issue when I try to establish a https/ssl connection from A->B (B has secured annotation on k8s service annotation). It seems that the annotation it is loaded but it is not used to set secure = true inside the KubernetesServiceInstance object. I checked in the KubernetesInformerDiscoveryClient and I see this at line 163 (v 2.1.3)
You can see that secure constructor parameter is always false.
Is it normal? Why, even if I put annotation on service description, the service B is called through http instead of https?
This is the reference to the documentation where secured annotation is mentioned:
https://docs.spring.io/spring-cloud-kubernetes/docs/2.1.1/reference/html/#loadbalancer-for-kubernetes
Thank you
Kind Regards
f
The text was updated successfully, but these errors were encountered: