When changing the cloud credentials on a cluster, it no longer updates the credentials under the image registry tab to match.
Hello @colin,
Can you give me more details on your problem?
What are the steps you took to encounter this problem?
Can you also share with us your console URL please?
Regards,
Charles-Edouard
Yesterday we changed our cluster’s AWS credentials in the “credentials” tab of the cluster. I then deactivated the old keys. Then when our cluster updated and tried to deploy new versions of our app it failed. It failed saying that it no longer had access to our container repository even though the new credentials did provide that access. Turns out that under the “Image Registry” tab, it did not update to using the new keys and was still trying to use the old deactivated keys. I thought that in the past I only had to update credentials in one spot and everything worked, but this time I had to update them in two spots. I would think it would just update both and cause less room for error.
Hello @colin ,
Thank you for your feedback.
Today, this is the normal behavior because some users have different AWS credentials for the cluster and the registry.
I will forward your feedback to the Product team and we will review the flow.
Do you think a message box asking if you also want to change the registry credentials would be a good idea?
Regards,
Charles-Edouard
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.