ExternalName service type in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the ExternalName service type in Kubernetes?

ExternalName service type maps a Kubernetes service to an external DNS name. It allows pods to access services outside the cluster using a simple service name.

intermediate

How does Kubernetes resolve an ExternalName service?

Kubernetes returns a CNAME record pointing to the external DNS name specified in the ExternalName service. The client then resolves this DNS name outside the cluster.

beginner

Which field must be specified in the ExternalName service manifest?

The 'externalName' field must be set to the DNS name you want to map to, for example 'my.database.example.com'.

intermediate

Can ExternalName services be used with selectors or endpoints?

No, ExternalName services do not use selectors or endpoints because they do not manage pods. They only provide DNS mapping to an external name.

beginner

Give an example YAML snippet for an ExternalName service.

apiVersion: v1 kind: Service metadata: name: my-external-service spec: type: ExternalName externalName: example.com

What does the ExternalName service type in Kubernetes do?

A Manages endpoints for internal services

B Creates a load balancer inside the cluster

C Exposes pods directly via IP addresses

D Maps a service to an external DNS name

ExternalName service type maps a Kubernetes service to an external DNS name, allowing access to services outside the cluster.

Which field is required in an ExternalName service manifest?

A clusterIP

B externalName

C selector

D ports

The 'externalName' field specifies the external DNS name to map the service to.

Can ExternalName services use selectors to find pods?

A No, ExternalName services do not use selectors

B Yes, selectors are mandatory

C Only if the service type is ClusterIP

D Only if endpoints are manually created

ExternalName services do not use selectors because they do not manage pods or endpoints.

What DNS record type does Kubernetes return for an ExternalName service?

A TXT record

B A record

C CNAME record

D MX record

Kubernetes returns a CNAME record pointing to the external DNS name specified.

Which Kubernetes service type would you use to access an external database by DNS name?

A ExternalName

B NodePort

C ClusterIP

D LoadBalancer

ExternalName service type is designed to map a service to an external DNS name, perfect for external databases.

Explain how an ExternalName service works in Kubernetes and when you would use it.

Think about how Kubernetes lets pods reach outside services using DNS.

Describe the key differences between ExternalName and other Kubernetes service types like ClusterIP or LoadBalancer.

Focus on how ExternalName handles service discovery differently.