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
What is the feature request? What problem does it solve?
With the introduction of the deploymentSupportedPythonVersions configuration, the fqdn of the image registry became part of the configuration map, instead of the previously used composite configuration approach.
This causes a situation, where the registry and its associated credentials need to be set in a separate configuration, thus leading to the possibility of unexpected errors, as mentioned in #2075 (comment)
We need to figure out a way to validate that the registries in the deploymentSupportedPythonVersions configuration are the same as the ones used for setting up the secrets.
Suggested solution
TBD
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
What is the feature request? What problem does it solve?
With the introduction of the deploymentSupportedPythonVersions configuration, the fqdn of the image registry became part of the configuration map, instead of the previously used composite configuration approach.
This causes a situation, where the registry and its associated credentials need to be set in a separate configuration, thus leading to the possibility of unexpected errors, as mentioned in #2075 (comment)
We need to figure out a way to validate that the registries in the deploymentSupportedPythonVersions configuration are the same as the ones used for setting up the secrets.
Suggested solution
TBD
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: