Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using ExternalName service type with KubernetesDiscoveryClient
See original GitHub issueImagine you have a setup when services running in K8S need to access services running outside.
I want to create an ExternalName service:
apiVersion: v1
kind: Service
metadata:
name: my-service
namespace: prod
spec:
type: ExternalName
externalName: my.service.example.com
After that I should be able to resolve service call http://my-service/doCall into http://my.service.example.com/doCall
So instead of relying only on endpoints in KubernetesDiscoveryClient, check if service type is ExternalName, then return single service instance with hostname: my.service.example.com.
Does it make sense to contribute this enhancement?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@muralidharan-rade there is already a PR open here https://github.com/spring-cloud/spring-cloud-kubernetes/pull/512
That would be great!
I would start by looking at the class
KubernetesDiscoveryClient.