Lab1: Cluster\u00a0 IP type service<\/p>\n
The git clone https:\/\/github.com\/amitopenwriteup\/k8s.git<\/a><\/p>\n Lab 2 : NodePort<\/p>\n Lab3: Service without Selectors<\/p>\n This service definition does not include a This Endpoints definition manually specifies that the Service named Lab4: Headless service<\/p>\n![\"\"](\"https:\/\/www.openwriteup.com\/wp-content\/uploads\/2023\/08\/clustersvc.jpg\")
<\/a><\/p>\n\n
apiVersion<\/code>: The version of the Kubernetes API being used. In this case, it’s v1<\/code>, which is the basic version of the API.<\/li>\nkind<\/code>: The type of Kubernetes resource being defined. Here, it’s a Service<\/code>.<\/li>\nmetadata<\/code>: Metadata about the service resource, including its name<\/code>.<\/li>\nspec<\/code>: The specification for the service, which includes:\n\n
selector<\/code>: A set of labels that are used to identify the pods to which this service should route traffic. In this case, it’s selecting pods with the label app.kubernetes.io\/name: proxy<\/code>.<\/li>\nports<\/code>: The ports that the service should expose. In this case, there’s one port defined:\n\n
name<\/code>: A name for the port.<\/li>\nprotocol<\/code>: The protocol used for the port, in this case, TCP<\/code>.<\/li>\nport<\/code>: The port number as exposed by the service.<\/li>\ntargetPort<\/code>: The port on the pods to which the traffic will be forwarded. http-web-svc<\/code> should be a name or a number representing the port used by the pods.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/a><\/p>\nlabels<\/code> in the pod’s metadata match the selector<\/code> in the previously defined Service. This means that the Service you defined earlier (nginx-service<\/code>) would route traffic to this pod based on the label app.kubernetes.io\/name: proxy.<\/code><\/p>\nkubectl create -f svc.yaml\r\nkubectl get svc\r\nkubectl get ep\r\nkubectl create -f dep.yaml\r\nkubectl get pods\r\nkubectl get ep\r\n\r\n##Delete the service\r\nkubectl delete -f svc.yaml\r\nkubectl detete -f dep.yaml<\/pre>\n
<\/a><\/p>\n\n
selector<\/code>: A set of labels that are used to identify the pods to which this service should route traffic. In this case, it’s selecting pods with the label app.kubernetes.io\/name: proxy<\/code>.<\/li>\nports<\/code>: The ports that the service should expose. In this case, there’s one port defined:\n\n
port<\/code>: The port number as exposed by the service.<\/li>\ntargetPort<\/code>: The port on the pods to which the traffic will be forwarded. This is set to 80<\/code> to match the port the pods are listening on.<\/li>\nnodePort<\/code>: An optional field that allows you to specify a specific port number on the nodes. If not specified, Kubernetes will allocate a port from the default range (typically 30000<\/code> to 32767<\/code>).<\/li>\nnodePort<\/code> (e.g., http:\/\/<Node_IP>:30007<\/code>).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nkubectl create -f dep.yaml\r\nkubectl create -f Nodeport.yaml\r\nkubectl get svc\r\nkubectl get ep\r\n\r\n#Delete the nodeport service\r\nkubectl delete svc my-service<\/pre>\n
<\/a><\/p>\nselector<\/code>, which means it doesn’t specify which pods the service should route traffic to. Without a selector, the service will not be associated with any pods, and it won’t have any effect in terms of routing traffic. We need to mention the endpoint kind object for this service.<\/p>\n<\/a><\/p>\nmy-svc<\/code> should route traffic to the IP address 192.168.40.131<\/code> on port 80<\/code>. This can be useful if you need to route traffic to specific IP addresses and ports that are not automatically managed by Kubernetes Service discovery.<\/p>\n kubectl create -f svcwithoutsel.yaml\r\nkubectl get svc\r\nkubectl get ep\r\nkubectl create -f ep.yaml\r\nkubectl get ep<\/pre>\n