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-8: Add clarity around HTTPS usage by standard Agent deployments

Browse Source
This commit is contained in:
James Carppe
2025-07-28 03:39:54 +00:00
committed by gitbook-bot
parent e0a59953c4
commit f1c95aa20e
5 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
admin/environments/add/docker/agent.md
View File

@@ -45,10 +45,10 @@ The right side of the mount should remain as `/var/lib/docker/volumes`, as that
Once the Agent has been deployed, enter the environment details using the table below as a guide:
| Field/Option | Overview |
| ------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Name | Give the environment a descriptive name. |
| Environment address | Enter the DNS name or IP address to connect to the Portainer Agent along with the port (the default port is `9001`). |
| Field/Option | Overview |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Give the environment a descriptive name. |
| Environment address | Enter the DNS name or IP address to connect to the Portainer Agent along with the port (the default port is `9001`). Do not provide a protocol - communication with the Agent by the Server is performed over HTTPS with certificates generated by the Agent on installation. |
<figure><img src="../../../../.gitbook/assets/2.16-environments-add-docker-agent.png" alt=""><figcaption></figcaption></figure>

8
admin/environments/add/kubernetes/agent.md
View File

@@ -65,10 +65,10 @@ Regardless of the method used, once the agent is running on the Kubernetes host,
Only do this **once** for your environment, regardless of how many nodes are in the cluster. You do **not** need to add each node as an individual environment in Portainer. Adding just one node will allow Portainer to manage the entire cluster.
{% endhint %}
| Field/Option | Overview |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Give the environment a descriptive name. |
| Environment address | Define the IP address or name used to connect to the environment (the Kubernetes host) and specify the port if required (`30778` when using NodePort; `9001` when using Load Balancer). |
| Field/Option | Overview |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Name | Give the environment a descriptive name. |
| Environment address | Define the IP address or name used to connect to the environment (the Kubernetes host) and specify the port if required (`30778` when using NodePort; `9001` when using Load Balancer). Do not provide a protocol - communication with the Agent by the Server is performed over HTTPS with certificates generated by the Agent on installation. |
<figure><img src="../../../../.gitbook/assets/2.15-k8s_env_url.png" alt=""><figcaption></figcaption></figure>

8
admin/environments/add/podman/agent.md
View File

@@ -41,10 +41,10 @@ The right side of the mount should remain as `/var/lib/docker/volumes`, as that
Once the Agent has been deployed, enter the environment details using the table below as a guide:
| Field/Option | Overview |
| ------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Name | Give the environment a descriptive name. |
| Environment address | Enter the DNS name or IP address to connect to the Portainer Agent along with the port (the default port is `9001`). |
| Field/Option | Overview |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Give the environment a descriptive name. |
| Environment address | Enter the DNS name or IP address to connect to the Portainer Agent along with the port (the default port is `9001`). Do not provide a protocol - communication with the Agent by the Server is performed over HTTPS with certificates generated by the Agent on installation. |
<figure><img src="../../../../.gitbook/assets/2.22.0-environments-add-podman-agent.png" alt=""><figcaption></figcaption></figure>

2
admin/environments/add/swarm/agent.md
View File

@@ -81,7 +81,7 @@ Once the agent is running on the Docker Swarm cluster, enter the environment det
Only do this **once** for your environment, regardless of how many nodes are in the cluster. You do **not** need to add each node as an individual environment in Portainer. Adding just one node (we recommend the manager node) will allow Portainer to manage the entire cluster.
{% endhint %}
<table><thead><tr><th width="238">Field</th><th>Overview</th></tr></thead><tbody><tr><td>Name</td><td>Give the environment a descriptive name.</td></tr><tr><td>Environment address</td><td>Enter the IP or DNS name at which the Portainer Server instance can reach the environment along with the port (<code>9001</code>).</td></tr></tbody></table>
<table><thead><tr><th width="238">Field</th><th>Overview</th></tr></thead><tbody><tr><td>Name</td><td>Give the environment a descriptive name.</td></tr><tr><td>Environment address</td><td>Enter the IP or DNS name at which the Portainer Server instance can reach the environment along with the port (<code>9001</code>). Do not provide a protocol - communication with the Agent by the Server is performed over HTTPS with certificates generated by the Agent on installation.</td></tr></tbody></table>
<figure><img src="../../../../.gitbook/assets/2.15-environments-add-swarm-agent-config.png" alt=""><figcaption></figcaption></figure>

2
admin/settings/general.md
View File

@@ -104,7 +104,7 @@ Make sure that your HTTPS configuration is working correctly **before** enabling
{% endhint %}
{% hint style="warning" %}
Ensure that any Edge agents have been correctly configured for HTTPS communication before enabling this.
Ensure that any Edge Agents have been correctly configured for HTTPS communication before enabling this. This setting does **not** affect Standard Agent deployments, as these use HTTPS certificates generated by the Agent on installation.
{% endhint %}
<figure><img src="../../.gitbook/assets/2.15-settings-settings-ssl-force.png" alt=""><figcaption></figcaption></figure>