Question: and is the service headless? or is it clusterIP?

Asked By
foxie
Asked At
2018-05-11 06:58:03

Found 15 possible answers.

User Answered At Possible Answer
anton015 2018-05-11 06:58:37 headless I think let me check
foxie 2018-05-11 06:58:41 be sure :slightly_smiling_face:
anton015 2018-05-11 06:59:30
Name:              vault-svc
the pod names in the stateful set is vault-0 and vault-1
But yea, it is a ClusterIP service :slightly_smiling_face:
both should be “hittable”
The service exposes 2 ports
I pasted the 
kubectl describe svc vault-svc
 as a thread comment to your reply
Events: Session Affinity: None Endpoints: 10.200.3.30:8201,10.200.37.39:8201 TargetPort: 8201/TCP Port: cluster 8201/TCP Endpoints: 10.200.3.30:8200,10.200.37.39:8200 TargetPort: 8200/TCP Port: http 8200/TCP IP: None Type: ClusterIP Selector: app=vault Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"vault"},"name":"vault-svc","namespace":"default"},"spec":{"clusterIP" ... Labels: app=vault Namespace: default
praveena 2018-05-11 07:08:46 Hi Just create new kubeadm cluster on AWS and deployed sample application. Pods and node are up and running but getting following error Error from server (NotFound): pods "searcher-d7bbc8f47-vqkx7" not found ubuntu@ip-172-31-1-31:~/production$ kubectl exec searcher-d7bbc8f47-vqkx7 bash
chosi 2018-05-11 07:10:38 -n?
shmarnev 2018-05-11 07:11:00 and kubectl -it most probably as @chosi mentioned, take a look at the namespaces
praveena 2018-05-11 07:12:46 ok
chosi 2018-05-11 07:13:09 check the namespace your pod is running in with kubectl get pods --all-namespaces
praveena 2018-05-11 07:13:13 ubuntu@ip-172-31-1-31:~/production$ kubectl exec -it searcher-d7bbc8f47-vqkx7 bash its running checked it Error from server (NotFound): pods "searcher-d7bbc8f47-vqkx7" not found
vexoon 2018-05-11 07:13:35 my dnsmasq container randomly crashes throughout the day, the only error/ event I can find is Liveness probe failed: HTTP probe failed with statuscode: 503 ... but nowhere a msg why it failed in the logs itself
praveena 2018-05-11 07:13:52 tize-production scheduler-6869dfc6d7-vbcx4 1/1 Running 0 10m
xmudrii 2018-05-11 07:15:04 Looks like it's in tize-production namespace
shmarnev 2018-05-11 07:15:06 so “kubectl exec -it searcher-d7bbc8f47-vqkx7 /bin/sh -n tize-production”
xmudrii 2018-05-11 07:15:25 Add -n tize-production to the command
praveena 2018-05-11 07:15:32 yes Thanks a lot its working

Related Questions