zxcvbnius / k8s-30-day-sharing Goto Github PK

I tried to follow your steps in day13. However I found an issue during my first deploy. When we creating the Pod, it started wordpress first, then started mysql. After the deploy competed, the wordpress one shows

wordpress:

Container ID:   docker://8cc5543acbb8b15fde01e32428456a2af2010cb15234e8ffe373775b8f99736d
Image:          wordpress:4-php7.0
Image ID:       docker-pullable://wordpress@sha256:c24c534fa99c17f7b0923d6ffa791b0f7fb43a821de5bc09564e46ae09d9966a
Port:           80/TCP
Host Port:      0/TCP
State:          Running
  Started:      Sun, 03 Feb 2019 23:06:19 -0500
Last State:     Terminated
  Reason:       Error
  Exit Code:    1
  Started:      Sun, 03 Feb 2019 23:05:25 -0500
  Finished:     Sun, 03 Feb 2019 23:05:55 -0500
Ready:          True
Restart Count:  1
Environment:
  WORDPRESS_DB_PASSWORD:  <set to the key 'db-password' in secret 'wordpress-secret'>  Optional: false
  WORDPRESS_DB_HOST:      127.0.0.1
Mounts:
  /var/run/secrets/kubernetes.io/serviceaccount from default-token-mktkm (ro)

It was because the MySQL is not ready when wordpress tried to connect database.

Do we have any approach to order the container start up sequence when define the deployment file like depends_on in docker compose file?

app: my-deployment:latest

spec.template.labels: Invalid value: "my-deployment:latest": a valid label must be an empty string or consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9])?')

3. 所以，當我們創建一個新的Pod後，收到使用者發送的request時，ks8內部會發生什麼事呢
   should be k8s

In day 5 tutorial, kubectl get pods --show-all is introduced, however,
Flag --show-all has been deprecated, will be removed in an upcoming release

Show all is the default now, -a is not required