vuppuluri sriramsubhash:
apiVersion: apps/v1
kind: Deployment
metadata:
creationTimestamp: null
labels:
app: deploy-important
id: very-important
name: deploy-important
namespace: project-tiger
spec:
replicas: 3
selector:
matchLabels:
app: deploy-important
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
app: deploy-important
spec:
containers:
- image: nignx:1.17.6-alpine
name: nignx
resources: {}
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: 'app'
operator: In
values:
- 'deploy-important'
topologyKey: <http://topology.kubernetes.io/zone|topology.kubernetes.io/zone>
status: {}
vuppuluri sriramsubhash:
No I understand the concept of daemon sets this is a question in killer.sh where they kind of create the concept of daemon set but with limited replicas using deployment and pod anti affinity
Ranga Reddy:
anti affinity does not stop to create multiple pods on same node , if single worker node is running and has enough resources so it can deploy multiple pods
unnivkn:
@vuppuluri sriramsubhash sorry, I misunderstood your question… hope the above solution helps for you.