diff --git a/.gitbook/assets/2.40.0-configmap.png b/.gitbook/assets/2.40.0-configmap.png new file mode 100644 index 00000000..54148810 Binary files /dev/null and b/.gitbook/assets/2.40.0-configmap.png differ diff --git a/.gitbook/assets/2.40.0-create-configmap.gif b/.gitbook/assets/2.40.0-create-configmap.gif new file mode 100644 index 00000000..c8bfd6cb Binary files /dev/null and b/.gitbook/assets/2.40.0-create-configmap.gif differ diff --git a/.gitbook/assets/2.40.0-secrets (1).png b/.gitbook/assets/2.40.0-secrets (1).png new file mode 100644 index 00000000..ea7a5372 Binary files /dev/null and b/.gitbook/assets/2.40.0-secrets (1).png differ diff --git a/.gitbook/assets/2.40.0-secrets.png b/.gitbook/assets/2.40.0-secrets.png new file mode 100644 index 00000000..ea7a5372 Binary files /dev/null and b/.gitbook/assets/2.40.0-secrets.png differ diff --git a/user/kubernetes/configurations/README.md b/user/kubernetes/configurations/README.md index 63e212ee..b0a91710 100644 --- a/user/kubernetes/configurations/README.md +++ b/user/kubernetes/configurations/README.md @@ -19,13 +19,13 @@ This page is split into two tabs - [ConfigMaps](./#configmaps) and [Secrets](./# This tab displays the ConfigMaps that exist within your Kubernetes cluster. By default, system resources are hidden. To view them, click the three dot menu on the right hand side and check **Show system resources**. -
+
You can filter the display of ConfigMaps by namespace by clicking **Filter** and checking the namespaces you want to see. -A ConfigMap with the **external** flag was created outside of Portainer, which means Portainer has limited knowledge on it compared to one created within Portainer. A label of **unused** means that Portainer cannot see any applications that are using this ConfigMap. This label may also appear on **external** resources because of the limited information available. +A ConfigMap with an **External** flag was created outside of Portainer, which means Portainer has limited knowledge on it compared to one created within Portainer. A label of **Unused** means that Portainer cannot see any applications that are using this ConfigMap. This label may also appear on external resources because of the limited information available. -To add a new ConfigMap via a form, click the **Add with form** button. To add via a manifest, click **Create from manifest**. +To add a new ConfigMap via a form, click the **Add with form** button. To add via a manifest or Helm chart, click **Create from code**. {% content-ref url="add.md" %} [add.md](add.md) @@ -37,13 +37,15 @@ To remove a ConfigMap, check the box next to the ConfigMap you want to remove an This tab displays the secrets that exist within your Kubernetes cluster. By default, system resources are hidden. To view them, click the three dot menu on the right hand side and check **Show system resources**. -
+
You can filter the display of secrets by namespace by clicking **Filter** and checking the namespaces you want to see. -A secret with the **external** flag was created outside of Portainer, which means Portainer has limited knowledge on it compared to one created within Portainer. A label of **unused** means that Portainer cannot see any applications that are using this secret. This label may also appear on **external** resources because of the limited information available. +A secret with the **External** flag was created outside of Portainer, which means Portainer has limited knowledge on it compared to one created within Portainer. A label of **Unused** means that Portainer cannot see any applications that are using this secret. This label may also appear on external resources because of the limited information available. -To add a new secret via a form, click the **Add with form** button. To add via a manifest, click **Create from manifest**. +A secret also shows labels for any associated registries. For admin users, these labels act as links to the registry. + +To add a new secret via a form, click the **Add with form** button. To add via a manifest or Helm chart, click **Create from code**. {% content-ref url="add-1.md" %} [add-1.md](add-1.md) diff --git a/user/kubernetes/configurations/add-1.md b/user/kubernetes/configurations/add-1.md index 841396d8..c04b4f93 100644 --- a/user/kubernetes/configurations/add-1.md +++ b/user/kubernetes/configurations/add-1.md @@ -10,10 +10,10 @@ metaLinks: From the menu select **ConfigMaps & Secrets**, ensure the **Secrets** tab is selected, then click **Add with form**. {% hint style="info" %} -Secrets can also be added [using a manifest](../applications/manifest/) by clicking **Create from manifest**. +Secrets can also be added [using a manifest or Helm chart](../applications/manifest/) by clicking **Create from code**. {% endhint %} -
+
Define the secret, using the table below as a guide. diff --git a/user/kubernetes/configurations/add.md b/user/kubernetes/configurations/add.md index bb83a594..d5053dba 100644 --- a/user/kubernetes/configurations/add.md +++ b/user/kubernetes/configurations/add.md @@ -10,10 +10,10 @@ metaLinks: From the menu select **ConfigMaps & Secrets**, ensure the **ConfigMaps** tab is selected, then click **Add with form**. {% hint style="info" %} -ConfigMaps can also be added [using a manifest](../applications/manifest/) by clicking **Create from manifest**. +Change hint settingsConfigMaps can also be added using a manifest or Helm chart by clicking **Create from code**. {% endhint %} -
+
Define the ConfigMap, using the table below as a guide.