admission-controller-webhook-demo icon indicating copy to clipboard operation
admission-controller-webhook-demo copied to clipboard

Timeout error

Open salimkapadia opened this issue 6 years ago • 0 comments

Hi there,

When I ran deploy.sh, it created the deployment but not the pod.

kubectl -n webhook-demo get events

LAST SEEN   TYPE      REASON              KIND         MESSAGE
25m         Warning   FailedCreate        ReplicaSet   Error creating: Timeout: request did not complete within requested timeout 30s
17m 

kubectl -n webhook-demo get deployments

NAME             READY   UP-TO-DATE   AVAILABLE   AGE
webhook-server   0/1     0            0           20m

kubectl -n webhook-demo describe deployment webhook-server

Name:                   webhook-server
Namespace:              webhook-demo
CreationTimestamp:      Fri, 13 Sep 2019 02:11:36 -0400
Labels:                 app=webhook-server
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=webhook-server
Replicas:               1 desired | 0 updated | 0 total | 0 available | 1 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=webhook-server
  Containers:
   server:
    Image:        admissioncontrollerwebhook2:v1.0.0
    Port:         8443/TCP
    Host Port:    0/TCP
    Environment:  <none>
    Mounts:
      /run/secrets/tls from webhook-tls-certs (ro)
  Volumes:
   webhook-tls-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  webhook-server-tls
    Optional:    false
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      False   MinimumReplicasUnavailable
  Progressing    False   ProgressDeadlineExceeded
OldReplicaSets:  <none>
NewReplicaSet:   webhook-server-7c6767cc65 (0/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  22m   deployment-controller  Scaled up replica set webhook-server-7c6767cc65 to 1

kubectl -n webhook-demo describe rs webhook-server-7c6767cc65

Name:           webhook-server-7c6767cc65
Namespace:      webhook-demo
Selector:       app=webhook-server,pod-template-hash=7c6767cc65
Labels:         app=webhook-server
                pod-template-hash=7c6767cc65
Annotations:    deployment.kubernetes.io/desired-replicas: 1
                deployment.kubernetes.io/max-replicas: 2
                deployment.kubernetes.io/revision: 1
Controlled By:  Deployment/webhook-server
Replicas:       0 current / 1 desired
Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  app=webhook-server
           pod-template-hash=7c6767cc65
  Containers:
   server:
    Image:        admissioncontrollerwebhook2:v1.0.0
    Port:         8443/TCP
    Host Port:    0/TCP
    Environment:  <none>
    Mounts:
      /run/secrets/tls from webhook-tls-certs (ro)
  Volumes:
   webhook-tls-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  webhook-server-tls
    Optional:    false
Events:
  Type     Reason        Age   From                   Message
  ----     ------        ----  ----                   -------
  Warning  FailedCreate  24m   replicaset-controller  Error creating: Timeout: request did not complete within requested timeout 30s

salimkapadia avatar Sep 13 '19 06:09 salimkapadia