<pclass="col-sm-12 vertical-center help-block small text-warning"ng-if="$ctrl.model.DeploymentType === undefined">
<pr-iconicon="'alert-triangle'"mode="'warning'"></pr-icon> There are no available deployment types when there is more than one type of environment in your edge group
selection (e.g. Kubernetes and Docker environments). Please select edge groups that have environments of the same type.
<pclass="col-sm-12 vertical-center help-block small text-warning"ng-if="$ctrl.model.DeploymentType === $ctrl.EditorType.Compose && $ctrl.hasKubeEndpoint()">
<pr-iconicon="'alert-triangle'"mode="'warning'"></pr-icon> Edge groups with kubernetes environments no longer support compose deployment types in Portainer. Please select
edge groups that only have docker environments when using compose deployment types.
Portainer no longer supports <ahref="https://docs.docker.com/compose/compose-file/"target="_blank">docker-compose</a> format manifests for Kubernetes deployments, and we
have removed the <ahref="https://kompose.io/"target="_blank">Kompose</a> 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).
</p>
<p
>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.</p
>
<p>
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