K
Q

how to communicate with daemonset pod from another pod in the same node?

6/12/2019

i want a daemonset-redis where every node will have it's own caching and each deployment pod will communicate with it's local daemonset-redis how to achieve it? how to reference daemonset pod in the same node from within docker-container?

UPDATE: i rather not use service option and make sure each pod access its local daemonset

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: redislocal
spec:
  selector:
    matchLabels:
      name: redislocal
  template:
    metadata:
      labels:
        name: redislocal
    spec:
      hostNetwork: true
      containers:
      - name: redislocal
        image: redis:5.0.5-alpine
        ports:
        - containerPort: 6379
          hostPort: 6379
-- Oren Lalezari
daemonset
kubernetes

Similar Questions

kubernetes networkpolicy namespaceSelector select when namespace has no labels
Jenkins on Kubernetes node is complaining its plug-ins need newer version of Jenkins, but don't want to lose data
Somehow my deployment was gone, is there any place which tracked the ‘gone/delete’ operation?
ASP.net Core OData serving HTTPS in Kubernetes with a certificate provided by an Ingress
Kubernetes - two pods (2/4) receiving same request

2 Answers

8/2/2019

There is a way of not using a service.

You can Expose Pod Information to Containers Through Environment Variables.

And you can use status.hostIP to know the ip address of node where pod is running. This was introduced in Kubernetes 1.7 link

You can add that to your pod or deployment yaml:

env:
- name: HOST_IP
  valueFrom:
    fieldRef:
      fieldPath: status.hostIP

It will set an variable HOST_IP which will have a value of node ip on which the pod is running, then you can use it to connect to a local DeamonSet.

-- Crou
Source: StackOverflow
6/12/2019

you should define a service ( selecting all redis pods ) and then communicate with redis from other pods

-- P Ekambaram
Source: StackOverflow