During an upgrade, the results indicate a secret is not present.
I have a problem where the upgrade is stuck on or failing to install rabbit. kubectl describe on the pending pods may include:
WarningFailed3m45s (x12 over 5m52s)kubeletError: secret "rabbitmq-ha.forge" not found
Try to create the secret. This is an example of a yaml file for this secret:
$ kubectl get secret -n domino-platform rabbitmq-ha.forge -o yaml
rabbitmq-password: BaseEncodedPassword # generate with echo newpassword |base64 ; echo
rabbitmq-username: Zm9yZ2U= # This maps to 'rabbitmq'
uid: Random string # probably skip this
Create this file - applying a new password and remove the uid line, kubectl apply -f <file>, namespace may be required although it is included in the file.
This is seen in sandboxed environment with no know reason why this as been lost. The secret will be read later by the rabbitmq deployment.