centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-17: C9S-22 - New banner policy + whats new page

Browse Source
This commit is contained in:
Hannah Cooper
2026-03-19 00:45:53 +00:00
committed by gitbook-bot
parent 94e33c378e
commit 451d08806a
10 changed files with 62 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
.gitbook/assets/2.40-warning-confirmation-box.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

BIN
.gitbook/assets/2.40.0-Default-confirm-box.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

BIN
.gitbook/assets/2.40.0-banner-and-change-policy.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 89 KiB

BIN
.gitbook/assets/2.40.0-banner-example.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 100 KiB

BIN
.gitbook/assets/2.40.0-error-confirmation-box.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 32 KiB

4
SUMMARY.md
View File

@@ -258,11 +258,13 @@
* [Create a Kubernetes security policy](admin/environments/policies/kubernetes-policies/kubernetes-security-policy.md)
* [Create a Kubernetes setup policy](admin/environments/policies/kubernetes-policies/kubernetes-setup-policy.md)
* [Create a Kubernetes registry policy](admin/environments/policies/kubernetes-policies/kubernetes-registry-policy.md)
* [Docker Policies](admin/environments/policies/docker-policies/README.md)
* [Docker, Swarm, or Podman Policies](admin/environments/policies/docker-policies/README.md)
* [Create a Docker, Swarm or Podman RBAC policy](admin/environments/policies/docker-policies/rbac-policy.md)
* [Create a Docker, Swarm or Podman security policy](admin/environments/policies/docker-policies/security-policy.md)
* [Create a Docker, Swarm or Podman setup policy](admin/environments/policies/docker-policies/setup-policy.md)
* [Create a Docker, Swarm or Podman registry policy](admin/environments/policies/docker-policies/registry-policy.md)
* [Policies for all environment types](admin/environments/policies/any-environment-type-policies/README.md)
* [Create a banner and change confirmation policy](admin/environments/policies/any-environment-type-policies/create-a-banner-and-change-confirmation-policy.md)
* [Tags](admin/environments/tags.md)
* [Update & Rollback](admin/environments/update.md)
* [Registries](admin/registries/README.md)

4
admin/environments/policies/README.md
View File

@@ -34,6 +34,10 @@ After selecting a policy type, select **Continue** at the bottom of the page to
[docker-policies](docker-policies/)
{% endcontent-ref %}
{% content-ref url="any-environment-type-policies/" %}
[any-environment-type-policies](any-environment-type-policies/)
{% endcontent-ref %}
## View policy details
From the menu, under **Environment-related**, select **Policies**. The policies page lists all existing policies. To see the details of an existing policy, click on the policy name. 

8
admin/environments/policies/any-environment-type-policies/README.md Normal file
View File

@@ -0,0 +1,8 @@
# Policies for all environment types
The following section describes the details of creating a policy that can be applied to any environment type.
{% content-ref url="create-a-banner-and-change-confirmation-policy.md" %}
[create-a-banner-and-change-confirmation-policy.md](create-a-banner-and-change-confirmation-policy.md)
{% endcontent-ref %}

27
admin/environments/policies/any-environment-type-policies/create-a-banner-and-change-confirmation-policy.md Normal file
View File

@@ -0,0 +1,27 @@
# Create a banner and change confirmation policy
Define a policy that allows you to display a custom banner with your chosen text and color across a specified group of environments, helping users clearly distinguish between them.
This policy also lets you configure a confirmation prompt that appears whenever a user applies a change to those environments, adding an extra layer of protection for sensitive workloads.
To create a banner and change confirmation policy, in the menu, under **Environment-related**, select **Policies** then select **Create policy**. From the policy type list, navigate to the **All (Kubernetes, Docker, Podman and Swarm)** > **Banner and change confirmation** section, select either a predefined template or the **Custom** policy, then select **Continue** to begin configuring the policy.
| Field/Option | Overview |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Define a name for this policy. |
| Environment groups | <p>Select one or more environment <a href="../../groups.md">groups</a> from the dropdown menu.<br>If the selected group is already included in an existing policy, a warning icon will appear next to the group name.</p> |
| Highlight environment | Enable this option to display a colored border around all pages for environments within the selected environment groups. |
| Highlight color | Specify the color of the border. You can select a color using the color picker or enter a hex code directly. |
| Banner message | Optionally specify a message to display within the border. |
| Enable change confirmation | Enable this option to display a confirmation dialog whenever changes are made in environments within the selected environment groups. |
| Confirmation title | Specify the title displayed in the confirmation dialog. |
| Confirmation message | Specify the message displayed within the confirmation dialog. |
| Confirmation style | Select the style of the confirmation dialog. See below for examples of each style. |
<figure><img src="../../../../.gitbook/assets/2.40.0-banner-and-change-policy.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../../.gitbook/assets/2.40.0-banner-example.png" alt=""><figcaption></figcaption></figure>
### Example banner styles
<table data-header-hidden><thead><tr><th></th><th data-type="image"></th></tr></thead><tbody><tr><td>Default</td><td><a href="../../../../.gitbook/assets/2.40.0-Default-confirm-box.png">2.40.0-Default-confirm-box.png</a></td></tr><tr><td>Warning</td><td><a href="../../../../.gitbook/assets/2.40-warning-confirmation-box.png">2.40-warning-confirmation-box.png</a></td></tr><tr><td>Error</td><td><a href="../../../../.gitbook/assets/2.40.0-error-confirmation-box.png">2.40.0-error-confirmation-box.png</a></td></tr></tbody></table>

21
whats-new.md
View File

@@ -16,4 +16,23 @@ You can read more about our release principles in our [lifecycle policy](https:/
## New in this release
###
### Docker Compose to Kubernetes migration ![](.gitbook/assets/button_be.png) ![](.gitbook/assets/button_ce.png)
We've added an experimental feature that allows you to [migrate Docker Compose workloads to Kubernetes](user/docker/stacks/migrate.md#docker-compose-to-kubernetes-migration). Using the [Kompose conversion tool](https://kompose.io/), Portainer can translate your existing Docker Compose definitions into Kubernetes resources, helping streamline the transition between platforms. As this feature is experimental, it is not recommended for production use, and we strongly advise taking a backup before starting any migration.
<figure><img src=".gitbook/assets/2.40.0-Migrate-to-K8s.png" alt="" width="375"><figcaption></figcaption></figure>
### Banner and Custom Change Confirmation policy ![](.gitbook/assets/button_be.png)
Portainer 2.40.0 introduces a new [Banner and Custom Change Confirmation policy](admin/environments/policies/any-environment-type-policies/create-a-banner-and-change-confirmation-policy.md).
This policy allows you to display a custom banner with your chosen text and color across a specified group of environments, helping users clearly distinguish between them. It also lets you configure a confirmation prompt that appears whenever a user applies a change to those environments, adding an extra layer of protection for sensitive workloads.
By combining visual identification with enforced confirmation, this policy helps reduce the risk of unintended changes while improving environment awareness.
<figure><img src=".gitbook/assets/2.40.0-banner-and-change-policy.png" alt=""><figcaption></figcaption></figure>
<figure><img src=".gitbook/assets/2.40.0-banner-example.png" alt=""><figcaption></figcaption></figure>
<figure><img src=".gitbook/assets/2.40-warning-confirmation-box.png" alt="" width="364"><figcaption></figcaption></figure>