You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zadig version:
1.18
ops stage:
When building the deployment, I used a private image, but found that it couldn't be pulled because the default-registry-secret was not created in the namespace, so it couldn't be pulled. At present, it has been found that default-registry-secret is only created when creating a new environment, so I would like to ask how to solve this problem?
Normally, when building tasks, the cluster will be checked every time to see if the default-registry-secret has been created. If it has not been created, it should need to be created.
The text was updated successfully, but these errors were encountered:
zadig version:
1.18
ops stage:
When building the deployment, I used a private image, but found that it couldn't be pulled because the default-registry-secret was not created in the namespace, so it couldn't be pulled. At present, it has been found that default-registry-secret is only created when creating a new environment, so I would like to ask how to solve this problem?
Normally, when building tasks, the cluster will be checked every time to see if the default-registry-secret has been created. If it has not been created, it should need to be created.
The text was updated successfully, but these errors were encountered: