Setup

You can make changes to your environment's Kubernetes configuration by selecting Cluster from the menu then selecting Setup.

Networking

Allow users to use external load balancer

To use this feature, you need to ensure that your cloud provider allows you to create load balancers. Using this feature may incur costs from your cloud provider.

Enabling the load balancer feature will allow users to expose applications they deploy over an external IP address assigned by their cloud provider.

Ingress controllers

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 IngressClass defined in the cluster.

Change Window Settings

This setting allows you to specify a window within which automatic updates to your applications can be applied.

If this setting is enabled and an update is made to an application outside of this window, it will not be applied.

Security

Restrict access to the default namespace

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.

Resources and Metrics

Allow resource over-commit

Enabling this feature lets you allocate more resources to namespaces than are physically available in the cluster.

Enable resource over-commit if you need to assign more resources to namespaces than are physically available in the cluster. This may lead to unexpected deployment failures if there are insufficient resources to meet the demand.

Disable resource over-commit (highly recommended) if you are only able to assign resources to namespaces that are less (in aggregate) than the cluster total, minus any system-resource reservation.

Enable features using metrics server

Ensure that the Kubernetes metrics server or Prometheus is running inside your cluster.

Enabling this feature will allow users to use specific features that leverage the metrics server component.

Available storage options

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.