Applications > Create an application Namespaces > {{ ctrl.application.ResourcePool }} > Applications > {{ ctrl.application.Name }} > Edit
Namespace
This namespace has exhausted its resource capacity and you will not be able to deploy the application. Contact your administrator to expand the capacity of the namespace.
You do not have access to any namespace. Contact your administrator to get access to a namespace.

Portainer uses Kompose to convert your Compose manifest to a Kubernetes compliant manifest. Be wary that not all the Compose format options are supported by Kompose at the moment.

You can get more information about Compose file format in the official documentation.

This feature allows you to deploy any kind of Kubernetes resource in this environment (Deployment, Secret, ConfigMap...).

You can get more information about Kubernetes file format in the official documentation.

Application

This field is required.

This field must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name', or 'abc-123').

An application with the same name already exists inside the selected namespace.

Stack
Portainer can automatically bundle multiple applications inside a stack. Enter a name of a new stack or select an existing stack in the list. Leave empty to use the application name.
Environment
add environment variable
name
value

Environment variable name is required.

This field must consist of alphabetic characters, digits, '_', '-', or '.', and must not start with a digit (e.g. 'my.env-name', or 'MY_ENV.NAME', or 'MyEnvName1'.

This environment variable is already defined.

Configurations
add configuration
Portainer will automatically expose all the keys of a configuration as environment variables. This behavior can be overriden to filesystem mounts for each key via the override button.
The following keys will be loaded from the {{ config.SelectedConfiguration.Name }} configuration as environment variables: {{ key }}{{ $last ? '' : ', ' }}
configuration key
path on disk

Path is required.

This path is already used.

Persisting data
No storage option is available to persist data, contact your administrator to enable a storage option.
add persisted folder
path in container
requested size
storage
volume

Path is required.

This path is already defined.

Size is required.

This value must be greater than zero.

Volume is required.

This volume is already used.

Specify how the data will be used across instances.
Resource reservations
Resource reservations are applied per instance of the application.
A resource quota is set on this namespace, you must specify resource reservations. Resource reservations are applied per instance of the application. Maximums are inherited from the namespace quota.
This namespace has exhausted its resource capacity and you will not be able to deploy the application. Contact your administrator to expand the capacity of the namespace.

Maximum memory usage (MB)

Value must be between {{ ctrl.state.sliders.memory.min }} and {{ ctrl.state.sliders.memory.max }}

Maximum CPU usage

These reservations would exceed the resources currently available in the cluster.
Deployment
Select how you want to deploy your application inside the cluster.

Instance count is required.

Instance count must be greater than 0.
This application will reserve the following resources: {{ ctrl.formValues.CpuLimit * ctrl.formValues.ReplicaCount | kubernetesApplicationCPUValue }} CPU and {{ ctrl.formValues.MemoryLimit * ctrl.formValues.ReplicaCount }} MB of memory.
This application would exceed available resources. Please review resource reservations or the instance count.
The following storage option(s) do not support concurrent access from multiples instances: {{ ctrl.getNonScalableStorage() }}. You will not be able to scale that application.
Auto-scaling

This feature is currently disabled and must be enabled by an administrator user.

Server metrics features must be enabled in the environment configuration view.

Minimum instances Maximum instances Target CPU usage (%)

Minimum instances is required.

Minimum instances must be greater than 0.

Minimum instances must be smaller than maximum instances.

Maximum instances is required.

Maximum instances must be greater than minimum instances.

Target CPU usage is required.

Target CPU usage must be greater than 0.

Target CPU usage must be smaller than 100.
This application would exceed available resources. Please review resource reservations or the maximum instance count of the auto-scaling policy.
Placement preferences and constraints
add rule
Deploy this application on nodes that respect ALL of the following placement rules. Placement rules are based on node labels.

This label is already defined.

Specify the policy associated to the placement rules.
Publishing the application
Select how you want to publish your application.
publish a new port
When publishing a port in cluster mode, the node port is optional. If left empty Kubernetes will use a random port number. If you wish to specify a port, use a port number inside the default range 30000-32767.
At least one published port must be defined.
container port
node port
load balancer port
ingress
hostname
route

Container port number is required.

Container port number must be inside the range 1-65535.

Container port number must be inside the range 1-65535.

This port is already used.

Node port number must be inside the range 30000-32767.

Node port number must be inside the range 30000-32767.

This port is already used.

Ingress selection is required.

Route is required.

This field must consist of alphanumeric characters or the special characters: '-', '_' or '/'. It must start and end with an alphanumeric character (e.g. 'my-route', or 'route-123').

This route is already used.

Load balancer port number is required.

Load balancer port number must be inside the range 1-65535.

Load balancer port number must be inside the range 1-65535.

This port is already used.

Actions