You can make changes to your environment's Kubernetes configuration by selecting Cluster from the menu then selecting Setup.
Enabling the load balancer feature will allow users to expose applications they deploy over an external IP address assigned by their cloud provider.
Configuring ingress controllers will allow users to expose applications they deploy over a HTTP route.
Portainer auto detects and lists any Ingress Classes defined in the cluster and are allowed by default. As an admin you may choose to disable Ingress Classes as needed.
Enable the Configure ingress controller availability per namespace toggle under More settings to be able control Ingress Class availability further at the namespace level.
Enabling Allow Ingress class to be set to "none" will let users create ingress objects without specifying any Ingress Class. This is useful for Kubernetes implementations where there is no
IngressClassdefined in the cluster.
By default, a Kubernetes cluster will instantiate a default namespace when provisioning the cluster to hold the default set of pods, services, and deployments used by the cluster. If this option is enabled, the only users with the power to run applications in the default namespace are Portainer administrators.
Enabling this feature lets you allocate more resources to namespaces than are physically available in the cluster.
Enabling this feature will allow users to use specific features that leverage the metrics server component.
Select which storage options will be available for use when deploying applications. Take a look at your storage driver documentation to figure out which access policy to configure, and whether or not the volume-expansion capability is supported.