Monday, March 18, 2019

Debugs... Lo explico despues!

 MYSQL_USER:                      Optional: false
      MYSQL_PASSWORD:              Optional: false
      MYSQL_ROOT_PASSWORD:    Optional: false
      MYSQL_DATABASE:                  Optional: false
    Mounts:
      /var/lib/mysql/data from mysql-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-75wrh (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  mysql-data:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  default-token-75wrh:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-75wrh
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  node-role.kubernetes.io/compute=true
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
  Type     Reason          Age               From                               Message
  ----     ------          ----              ----                               -------
  Normal   Scheduled       33s               default-scheduler                  Successfully assigned qq/mysql-1-j4k96 to qqmelo1c.mylabserver.com
  Warning  Failed          6s (x8 over 30s)  kubelet, qqmelo1c.mylabserver.com  Error: Couldn't find key database-name in Secret qq/mysql
  Normal   SandboxChanged  5s (x8 over 29s)  kubelet, qqmelo1c.mylabserver.com  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          2s (x9 over 30s)  kubelet, qqmelo1c.mylabserver.com  Container image "docker-registry.default.svc:5000/openshift/mysql@sha256:c825717ffe30b7816006d95b8bb0bab7f462bdf9658a0092fc0149339037b0ee" already present on machine

No comments: