Hi,
I applied a Deployment object to an OpenShift 3.7 cluster which just
doesn't start to rollout:
---
# cat kube-state-metrics.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: kube-state
spec:
selector:
matchLabels:
app: kube-state
template:
metadata:
name: kube-state
labels:
app: kube-state
spec:
containers:
- image: gcr.io/google_containers/kube-state-metrics:v1.2.0
name: kube-state
ports:
- containerPort: 8080
name: kube-state
# oc apply -f kube-state-metrics.yaml
# oc get deployments
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
kube-state 1 0 0 0 41m
# oc get rs
No resources found.
# oc rollout status deployment/kube-state
Waiting for deployment spec update to be observed...
# oc version
oc v3.7.9
kubernetes v1.7.6+a08f5eeb62
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://console
openshift v3.7.14
kubernetes v1.7.6+a08f5eeb62
---
Rolling out the same image using a DeploymentConfig works perfectly fine:
---
# cat kube-state-metrics-dc.yaml
kind: DeploymentConfig
apiVersion: v1
metadata:
name: kube-state
spec:
template:
metadata:
name: kube-state
labels:
app: kube-state
spec:
spec:
containers:
- image: gcr.io/google_containers/kube-state-metrics:v1.2.0
name: kube-state
ports:
- containerPort: 8080
name: kube-state
replicas: 1
strategy:
type: Rolling
revisionHistoryLimit: 2
minReadySeconds: 0
# oc apply -f kube-state-metrics-dc.yaml
# oc get dc
NAME REVISION DESIRED CURRENT TRIGGERED BY
kube-state 1 1 1 config
---
Any idea how I could debug this and what the issue could be?
Best,
Tobias
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
