Hello, I have a pod with 3 kublets one of the kublet had an issue and I had
a `CrashLoopBackOff` but the rolling update continued, so the application
failed and became un available.
What is the correct way to prevent this from happening?
here is my yaml file:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: app-dev
labels:
pod: app
track: develop
annotations:
scheduler.alpha.kubernetes.io/affinity: >
{
"nodeAffinity": {
"requiredDuringSchedulingIgnoredDuringExecution": {
"nodeSelectorTerms": [
{
"matchExpressions": [
{
"key": "beta.kubernetes.io/instance-type",
"operator": "In",
"values": ["c4.large"]
}
]
}
]
}
}
}
spec:
replicas: 3
template:
metadata:
labels:
pod: app
track: develop
spec:
containers:
- name: trint-api
image: quay.io/nkhine/api:develop
imagePullPolicy: Always
ports:
- containerPort: 3000
- name: media
image: quay.io/nkhine/media:develop
imagePullPolicy: Always
ports:
- containerPort: 4000
- name: phantom
image: docker.io/wernight/phantomjs:2.1.1
command: ["phantomjs", "--webdriver=8910", "--web-security=no",
"--load-images=false", "--local-to-remote-url-access=yes"]
ports:
- containerPort: 8910
resources:
requests:
memory: 1000
restartPolicy: Always
imagePullSecrets:
# we download these from quay.io account
- name: my-pull-secret
in my case the :media kublet had an issue and it failed to start.
any advise is much appreciated
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
