Portainer no longer supports docker-compose format manifests for Kubernetes deployments, and we have removed the Kompose conversion tool which enables this. The reason for this is because Kompose now poses a security risk, since it has a number of Common Vulnerabilities and Exposures (CVEs).
Unfortunately, while the Kompose project has a maintainer and is part of the CNCF, it is not being actively maintained. Releases are very infrequent and new pull requests to the project (including ones we've submitted) are taking months to be merged, with new CVEs arising in the meantime.
We advise installing your own instance of Kompose in a sandbox environment, performing conversions of your Docker Compose files to Kubernetes manifests and using those manifests to set up applications.
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.
This field is required.
This field must consist of lower case alphanumeric characters or '-', contain at most 63 characters, 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.
Value must be between {{ ctrl.state.sliders.memory.min }} and {{ ctrl.state.sliders.memory.max }}
Instance count is required.
Instance count must be greater than 0.
{{ ctrl.getNonScalableStorage() }}
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 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 label is already defined.