Sorry, a typo - its a 3.7 cluster not 3.6 ~> oc version
oc v3.7.2+282e43f kubernetes v1.7.6+a08f5eeb62 features: Basic-Auth Server openshift v3.7.0+7ed6862 kubernetes v1.7.6+a08f5eeb62 On Sun, 2 Dec 2018 at 18:39 Cameron Braid <came...@braid.com.au> wrote: > I have a strange issue in my 3.6 cluster. I create a extensions/v1beta1 > Deployment > and nothing happens. No pods are created. oc describe shows > > oc -n drivenow-staging-x describe deployment strimzi-cluster-operator > Name: strimzi-cluster-operator > Namespace: drivenow-staging-x > CreationTimestamp: Sun, 02 Dec 2018 01:33:10 +1100 > Labels: app=strimzi > Annotations: <none> > Selector: name=strimzi-cluster-operator > *Replicas: 1 desired | 0 updated | 0 total | 0 available | 0 unavailable* > StrategyType: Recreate > MinReadySeconds: 0 > Pod Template: > Labels: name=strimzi-cluster-operator > Service Account: strimzi-cluster-operator > Containers: > strimzi-cluster-operator: > Image: strimzi/cluster-operator:0.6.0 > Port: <none> > Limits: > cpu: 1 > memory: 256Mi > Requests: > cpu: 200m > memory: 256Mi > Liveness: http-get http://:8080/healthy delay=10s timeout=1s > period=30s #success=1 #failure=3 > Readiness: http-get http://:8080/ready delay=10s timeout=1s > period=30s #success=1 #failure=3 > Environment: ... > Mounts: <none> > Volumes: <none> > OldReplicaSets: <none> > NewReplicaSet: <none> > Events: <none> > > All nodes are ready, schedulable and there doesnt appear to be antyhing in > the logs. > > I've tried restarting origin-node, origin-master-api and > origin-master-controllers on all nodes and that has no impact. > > I'm out of ideas. > > Cameron >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
