0

I use OS Centos 7. My Pod:

apiVersion: v1
kind: Pod
metadata:
  name: tomcat
spec:
  containers:
  - image: ec2-73-99-254-8.eu-central-1.compute.amazonaws.com:5000/tom
    name: tomcat
    command: ["sh","-c","/opt/tomcat/bin/deploy-and-run.sh"]
    volumeMounts:
    - mountPath: /maven
      name: app-volume
    ports:
    - containerPort: 8080
  volumes:
  - name: app-volume
    hostPath:
      path: /maven

My Sevice:

apiVersion: v1
kind: Service
metadata:
  name: tomcat
spec:
  ports:
    - name: http
      port: 80
      targetPort: 8080
      protocol: TCP
  selector:
    name: tomcat

Services looks like:

# kubectl get svc
NAME         CLUSTER_IP      EXTERNAL_IP   PORT(S)   SELECTOR      AGE
kubernetes   10.254.0.1      <none>        443/TCP   <none>        14h
tomcat       10.254.206.26   <none>        80/TCP    name=tomcat   13h

And Pods:

# kubectl get pod
NAME      READY     STATUS    RESTARTS   AGE
tomcat    1/1       Running   0          13h

And when I run Curl:

curl 10.254.206.26
curl: (56) Recv failure: Connection reset by peer

Kube-proxy logs at that moment show somthing like this:

kube-proxy[22273]: Couldn't find an endpoint for default/tomcat:http: missing service entry
kube-proxy[22273]: Failed to connect to balancer: missing service entry

But when I run curl directly to the pod ip address and port 8080 - it works fine. When I run command kubectl get endpoints

NAME         ENDPOINTS             AGE
kubernetes   195.234.109.11:6443   14h
tomcat       <none>                14h

Field ENDPOINTS in this output with "none" looks strange. What's wrong?

cizixs
  • 12,931
  • 6
  • 48
  • 60
Valentyn Tymku
  • 3
  • 2

1 Answers1

0

Services work by matching labels. You are attempting to match based on the name of your pod. Try changing the metadata for your pod to

metadata:
  name: tomcat
  labels:
    name: tomcat

and see if that helps.

Robert Bailey
  • 17,866
  • 3
  • 50
  • 58