Name:             envoy-gateway-gateway-helm-certgen-c25dz
Namespace:        envoy-gateway-system
Priority:         0
Service Account:  envoy-gateway-gateway-helm-certgen
Node:             <none>
Labels:           app=certgen
                  batch.kubernetes.io/controller-uid=a58b7f4f-23f9-4524-81e2-16d7719419bf
                  batch.kubernetes.io/job-name=envoy-gateway-gateway-helm-certgen
                  controller-uid=a58b7f4f-23f9-4524-81e2-16d7719419bf
                  job-name=envoy-gateway-gateway-helm-certgen
Annotations:      <none>
Status:           Pending
IP:               
IPs:              <none>
Controlled By:    Job/envoy-gateway-gateway-helm-certgen
Containers:
  envoy-gateway-certgen:
    Image:           docker.io/envoyproxy/gateway:v1.7.0
    Port:            <none>
    Host Port:       <none>
    SeccompProfile:  RuntimeDefault
    Command:
      envoy-gateway
      certgen
    Environment:
      ENVOY_GATEWAY_NAMESPACE:    envoy-gateway-system (v1:metadata.namespace)
      KUBERNETES_CLUSTER_DOMAIN:  cluster.local
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-pmzlb (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  kube-api-access-pmzlb:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    Optional:                false
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age                 From               Message
  ----     ------            ----                ----               -------
  Warning  FailedScheduling  4s (x2 over 5m18s)  default-scheduler  0/3 nodes are available: 3 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.