K
Q

In what order does Skaffold start up deployments and is there a way to specify order?

1/20/2020

Basically, I need the database deployment to spin up before the API deployment. If the database isn't running, it throws an error in the API.

I've messed with the order in artifacts: and also in:

deploy:
  kubectl:
    manifests:
      - manifests/ingress.yaml 
      - manifests/postgres.yaml      
      - manifests/client.yaml
      - manifests/api.yaml

But it doesn't seem to have any bearing on the order they startup.

The only thing I can think is that it is alphabetical. I used to not have an issue: the database would startup 49/50 before the api. Now it is about the opposite. The only thing I've changed is a new computer and I renamed the server to api which puts it first alphabetically.

So two questions:

  1. How is the deployment order determined in Skaffold?
  2. Is there a way to set the order?
-- eox.dev
kubernetes
skaffold

Similar Questions

Presto cluster on Kubernetes error worker bind port 8080
Is there a command to list all the kubernetes cluster's configuration files
Is is possible to run multiples instances of Traefik v2 with DNSchallenge
Metric sent to DataDog not shown on UI
Argo workflow stuck in pending due to liveness probe fail?
How can I limit access to a website that is deployed in a gke cluster to only be accessible by an IP range?
Kubectl: error: proto: mismatching end group marker

1 Answer

1/30/2020

What I had to do was setup a livenessProbe and a readinessProbe.

          livenessProbe:
            tcpSocket:
              port: 5000
            initialDelaySeconds: 2
            periodSeconds: 2
          readinessProbe:
            tcpSocket:
              port: 5000
            initialDelaySeconds: 2
            periodSeconds: 2

This looks for Django to fail (i.e. can't connect to the database) and if it does it keeps trying to redeploy it until it doesn't. This was the only way that I could find.

-- eox.dev
Source: StackOverflow