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
After going in the Container/OCI registry and then selecting a specific Registry provider, the registry URL section cannot be edited and it is locked.
👟 Reproduction steps
Go to Global Configurations.
Select Container/OCI registry.
Add Registry.
In registry provider, in the dropdown menu, select the Docker, Quay or GCR or any aption that auto-fills the Registry URL section
which lies just below that.
Hover your cursor on the Registry URL section. (It's locked)
👍 Expected behavior
After selecting a specific Registry provider that auto-fills the Registry provider section, the registry URL section should allow edit and should not get locked when we hover on it.
👎 Actual Behavior
After selecting a specific Registry provider that auto-fills the Registry provider section, the registry URL section cannot be edited and is locked.
☸ Kubernetes version
any
Cloud provider
any
🌍 Browser
Chrome
🧱 Your Environment
QA
✅ Proposed Solution
NA
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
After going in the Container/OCI registry and then selecting a specific Registry provider, the registry URL section cannot be edited and it is locked.
👟 Reproduction steps
which lies just below that.
👍 Expected behavior
After selecting a specific Registry provider that auto-fills the Registry provider section, the registry URL section should allow edit and should not get locked when we hover on it.
👎 Actual Behavior
After selecting a specific Registry provider that auto-fills the Registry provider section, the registry URL section cannot be edited and is locked.
☸ Kubernetes version
any
Cloud provider
any
🌍 Browser
Chrome
🧱 Your Environment
QA
✅ Proposed Solution
NA
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#9669
The text was updated successfully, but these errors were encountered: