Question: In gitops-type OES installation, halyard pod is stuck in "podinitializing" stage for more than 5-10 minutes.

Answer: This means that the halayrd daemon is not coming-up.  A common reason is missing or incorrect "halyard.yaml" in the gitops repo.


An init container in the halyard-pod copies contents of the gitrepo specified in the values.yaml into the pod-memory. We can check if this copy was successful using a command similar to this one:


kubectl -n opsmx-isd logs isd-spinnaker-halyard-0 -c create-halyard-local


Any errors shown will indicate the correct solution.