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
As an admin, I want the Kubernetes Cluster setup screen’s ingress settings to be clearer and to give info on ingress defaults, so I can manage my cluster’s ingress settings more easily
Expected Behavior
K8s Cluster setup is updated, including the following:
Change the existing ‘Networking’ title (near the top) to be ‘Networking - Services’
Add a ‘Networking - Ingresses’ title
Move the two ingress toggles out of the expand section (and hence do away with the expand)
Move the ‘Only allow admins to deploy ingresses’ toggle to sit with the other ingress toggles
Add the additional ingress defaults info text
Actual Behavior
K8s Cluster setup could have better layout in certain aspects.
Steps to Reproduce
N/A
Portainer logs or screenshots
No response
Portainer version
2.18.4
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
N/A
OS and Architecture
N/A
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Before you start please confirm the following.
Problem Description
As an admin, I want the Kubernetes Cluster setup screen’s ingress settings to be clearer and to give info on ingress defaults, so I can manage my cluster’s ingress settings more easily
Expected Behavior
K8s Cluster setup is updated, including the following:
Actual Behavior
K8s Cluster setup could have better layout in certain aspects.
Steps to Reproduce
N/A
Portainer logs or screenshots
No response
Portainer version
2.18.4
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
N/A
OS and Architecture
N/A
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: