-
- One or more of the selected Edge group contains Edge Docker endpoints that cannot be used with a Kubernetes Edge stack.
-
-
+
+ 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.
+
-
-
-
-
- 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.
-
+
+
+
+
+ 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.
+
@@ -38,6 +44,7 @@
identifier="compose-editor"
placeholder="# Define or paste the content of your docker compose file here"
on-change="($ctrl.onChangeComposeConfig)"
+ read-only="$ctrl.hasKubeEndpoint()"
>
No Edge groups are available. Head over to the Edge groups view to create one.
+
+ 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.
+
-
-
-
-
- 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.
-
-
-
-
+
+
@@ -88,6 +99,7 @@
-
-
-
-
- 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.
-
-
In a forthcoming Portainer release, we plan to remove support for docker-compose format manifests for Kubernetes deployments, and 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.
-
+
+
+
+
+ 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.
+
+
+
@@ -1345,9 +1354,9 @@
-
Actions
+
Actions
-
+
-
-
-
diff --git a/app/portainer/views/settings/settingsController.js b/app/portainer/views/settings/settingsController.js
index 3db3eca34..91cb02d02 100644
--- a/app/portainer/views/settings/settingsController.js
+++ b/app/portainer/views/settings/settingsController.js
@@ -1,14 +1,10 @@
import angular from 'angular';
import { FeatureId } from '@/react/portainer/feature-flags/enums';
-// import trackEvent directly because the event only fires once with $analytics.trackEvent
-import { trackEvent } from '@/angulartics.matomo/analytics-services';
import { options } from './options';
angular.module('portainer.app').controller('SettingsController', [
'$scope',
- '$analytics',
- '$state',
'Notifications',
'SettingsService',
'ModalService',
@@ -16,7 +12,7 @@ angular.module('portainer.app').controller('SettingsController', [
'BackupService',
'FileSaver',
'Blob',
- function ($scope, $analytics, $state, Notifications, SettingsService, ModalService, StateManager, BackupService, FileSaver) {
+ function ($scope, Notifications, SettingsService, ModalService, StateManager, BackupService, FileSaver) {
$scope.customBannerFeatureId = FeatureId.CUSTOM_LOGIN_BANNER;
$scope.s3BackupFeatureId = FeatureId.S3_BACKUP_SETTING;
$scope.enforceDeploymentOptions = FeatureId.ENFORCE_DEPLOYMENT_OPTIONS;
@@ -57,7 +53,6 @@ angular.module('portainer.app').controller('SettingsController', [
$scope.formValues = {
customLogo: false,
- ShowKomposeBuildOption: false,
KubeconfigExpiry: undefined,
HelmRepositoryURL: undefined,
BlackListedLabels: [],
@@ -83,33 +78,6 @@ angular.module('portainer.app').controller('SettingsController', [
});
};
- $scope.onToggleShowKompose = async function onToggleShowKompose(checked) {
- if (checked) {
- ModalService.confirmWarn({
- title: 'Are you sure?',
- message: `
In a forthcoming Portainer release, we plan to remove support for docker-compose format manifests for Kubernetes deployments, and 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.