add external name kind to helm #15
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An ExternalName service is a way to provide an alias for an external resource outside the Kubernetes cluster. Instead of mapping to a selector and forwarding traffic to a set of pods, an ExternalName service acts as a DNS CNAME record.
When you define an ExternalName service, Kubernetes does not create any endpoints or proxies for the service. Instead, it simply returns a DNS record with the specified external name value. When the Kubernetes cluster attempts to reach the service by its name, it resolves the name to the associated external name value, typically a DNS name or IP address.
This type of service is useful when you want to map a Kubernetes service to an external resource, such as an external database, external load balancer, or any other service residing outside the cluster. It allows you to reference the external resource using a service name within the cluster, abstracting the underlying network details.
Note that an ExternalName service only supports the TCP and UDP protocols and cannot provide load balancing or scaling features like other service types such as ClusterIP or NodePort