Kubernetes吊舱之间的通信

我的豆荚很结实。当我进入其中一个播客并尝试ping它的主机名时。它起作用了。但是，如果我尝试从当前容器ping其他pod的主机名，那么这些主机名将无法解析。我也有无头服务。有人能告诉我在集群级别或者在服务或状态集的yaml中需要做些什么来实现通信吗。一个工作的例子或一些工作图表链接来尝试，将是有益的。我能挺过去

服务：

apiVersion: v1
kind: Service
metadata:
  name: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}"
  labels:
    app: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}"
{{ include "metadata.labels.standard" . | indent 4 }}    
spec:
  clusterIP: None
  selector:
   tier: backend

状态集：

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-myapp1"
  labels:
    app: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-myapp1"
    tier: backend
spec:
  replicas: 2
  selector:
    matchLabels:
      app: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-myapp1"
  serviceName: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}"
  template:
    metadata:
      labels:
        app: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-myapp1"
        tier: backend
      volumes:
        - name: configmap-r
          configMap:
           name: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-configmap"
      imagePullSecrets:
        - name: {{ .Values.image.pullSecret }}
      containers:
        - name: "{{ .Chart.Name }}-{{ .Chart.AppVersion | replace "." "" }}-myapp1"
          image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
          imagePullPolicy: Always
          ports:
            - containerPort: 8080
          volumeMounts:
            - name: configmap-r
              mountPath: /home/xyz/

豆荚：

pod/calico-kube-controllers-59fc8847c-vv9bt 1/1运行0 3H27米
pod/calico-node-4gktj 1/1运行距离为0 3H27米
pod/coredns-5c98db65d4-tctgk 1/1运行13 63d
pod/coredns-5c98db65d4-v8gtv 1/1运行13 63d
吊舱/etcd小型工棚1/1运行2 63d
pod/kube插件管理器minikube 1/1运行2 63d
pod/kube apiserver minikube 1/1运行0 15d
pod/kube控制器管理器minikube 1/1运行6 63d
pod/kube-proxy-qc9nx 1/1运行1 63d
pod/kube调度程序minikube 1/1运行6 63d
pod/存储供应器1/1运行3 63d
pod/tiller-deploy-6b9c575bfc-z7dgs 1/1运行162D
名称类型CLUSTER-IP外部IP端口年龄
service/kube dns ClusterIP xx.xx.xx.xx 53/UDP、53/TCP、9153/TCP 63d
服务/舵柄部署群集IP xx.xx.xx.xx 44134/TCP 62d
名称所需的当前就绪最新可用节点选择器年龄
daemonset.apps/calico-node 1 beta.kubernetes.io/os=linux 3h27m
daemonset.apps/kube-proxy 1 beta.kubernetes.io/os=linux 63d
姓名就绪最新可用年龄
deployment.apps/calico-kube-controllers 1/1 3h27m
deployment.apps/coredns 2/2 63d
deployment.apps/tiller-deploy 1/162d
名称所需的当前就绪年龄
replicaset.apps/calico-kube-controllers-59fc8847c 1 3h27m
replicaset.apps/coredns-5c98db65d4 2 63d
replicaset.apps/tiller-deploy-6b9c575bfc 1 62d

---

`

要在集群内公开服务，请将类型值用作clusterIP。而不是使用 规格： 集群：无

使用以下命令：

---

类型：ClusterIP

添加您的服务definition@EfratLevitanaddedc是否可以添加statefulset YAML，以及如何查询其他pod（使用了整个命令）？@Ezwig添加了YAML。像这样，我有另一个相同的yaml用于myapp2。我将进入myapp1并尝试启动此命令$ping@Nish您用于查询其他POD可能有有用信息的整个命令，请检查并创建Dashrath建议的服务，并让我们知道这是否有效？

pod/calico-kube-controllers-59fc8847c-vv9bt   1/1     Running            0          3h27m
pod/calico-node-4gktj                         1/1     Running            0          3h27m
pod/coredns-5c98db65d4-tctgk                  1/1     Running            13         63d
pod/coredns-5c98db65d4-v8gtv                  1/1     Running            13         63d
pod/etcd-minikube                             1/1     Running            2          63d
pod/kube-addon-manager-minikube               1/1     Running            2          63d
pod/kube-apiserver-minikube                   1/1     Running            0          15d
pod/kube-controller-manager-minikube          1/1     Running            6          63d
pod/kube-proxy-qc9nx                          1/1     Running            1          63d
pod/kube-scheduler-minikube                   1/1     Running            6          63d
pod/storage-provisioner                       1/1     Running            3          63d
pod/tiller-deploy-6b9c575bfc-z7dgs            1/1     Running            1          62d


NAME                           TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)                  AGE
service/kube-dns               ClusterIP   xx.xx.xx.xx     <none>        53/UDP,53/TCP,9153/TCP   63d
service/tiller-deploy          ClusterIP   xx.xx.xx.xx     <none>        44134/TCP                62d

NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
daemonset.apps/calico-node   1         1         1       1            1           beta.kubernetes.io/os=linux   3h27m
daemonset.apps/kube-proxy    1         1         1       1            1           beta.kubernetes.io/os=linux   63d

NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/calico-kube-controllers   1/1     1            1           3h27m
deployment.apps/coredns                   2/2     2            2           63d
deployment.apps/tiller-deploy             1/1     1            1           62d

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/calico-kube-controllers-59fc8847c   1         1         1       3h27m
replicaset.apps/coredns-5c98db65d4                  2         2         2       63d
replicaset.apps/tiller-deploy-6b9c575bfc            1         1         1       62d