Any special steps needed to upgrade from 1.2.0 to 1.4.0?

Hey @stmh ,

You should be able to upgrade without making any changes to the credentials file. We haven't changed the format or the fields inside that file since the initial release.

Couple questions:
1. Prior to running the upgrade, did you already create a Kubernetes secret named op-credentials?
2. Did you try providing the credentials file to the helm chart with this flag:
--set-file connect.credentials=<path/to/1password-credentials.json>
(src: https://github.com/1Password/connect-helm-charts/tree/main/charts/connect#values)

Hi @David_ag ,

thanks for the clarification. Then it seems I didnt keep a copy of the credentials-file. And somehow I do not have the op-credentials on the cluster. But somehow the connect-api is working without problem.

Is there a way to restore it from the deployed pod somehow? Or recreate the credentials file for an existing integration?

Unfortunately there's currently no way to recreate the credentials file.

I'm not completely familiar with the Kubernetes Secrets internals, but you may wan to try listing the Kubernetes secrets in the namespace where the operator is running. You may wan to consult the https://github.com/1Password/connect-helm-charts/tree/connect-1.2.0/charts/connect and see if you can discover where the credentials file is living in your cluster.

Ok, fortunately found a backup of the credential file. Thank you for your support.

On behalf of David, you are very welcome @stmh, and thank you for the update :)