GITBOOK-70: --set tls.true info message

This commit is contained in:
Hannah Cooper
2026-02-17 07:12:31 +00:00
committed by gitbook-bot
parent 8b44bbe57a
commit a68a922bcc

View File

@@ -5,9 +5,9 @@ Always match the agent version to the Portainer Server version. In other words,
{% endhint %}
{% hint style="warning" %}
Starting from Portainer CE 2.9 and BE 2.10, HTTPS is enabled by default on port `9443`. These instructions will configure Portainer to use both `9443` for HTTPS and `9000` for HTTP. You can choose to [completely disable HTTP](../../admin/settings/#force-https-only) after the update. 
Starting from Portainer CE 2.9 and BE 2.10, HTTPS is enabled by default on port `9443`. These instructions will configure Portainer to use both `9443` for HTTPS and `9000` for HTTP. You can choose to [completely disable HTTP](../../admin/settings/#force-https-only) after the update.
Before you make Portainer HTTPS only, make sure you have all your Agents and Edge Agents already communicating with Portainer using HTTPS. 
Before you make Portainer HTTPS only, make sure you have all your Agents and Edge Agents already communicating with Portainer using HTTPS.
{% endhint %}
{% hint style="danger" %}
@@ -18,6 +18,10 @@ Select the Portainer update method which matches the original installation metho
## Method 1: Updating using Helm
{% hint style="info" %}
This article assumes that you installed originally using our [install instructions](../install/server/kubernetes/baremetal.md#deploy-using-helm).
{% endhint %}
Add the Portainer Helm repository by running the following commands. Ignore any warnings about the repo already being there:
```
@@ -83,7 +87,7 @@ https://downloads.portainer.io/ce-lts/portainer-agent-k8s-nodeport.yaml
If you have set a custom `AGENT_SECRET` on your Portainer Server instance (by specifying an `AGENT_SECRET` environment variable when starting the Portainer Server container) you must remember to explicitly provide the same secret to your Agent in the same way (as an environment variable) in the YAML when updating your Agent:
`environment:`\
  `- AGENT_SECRET: yoursecret`
`- AGENT_SECRET: yoursecret`
{% endhint %}
{% endtab %}
@@ -121,12 +125,12 @@ If you have set a custom `AGENT_SECRET` on your Portainer Server instance you mu
`environment:`
  `- AGENT_SECRET: yoursecret`
`- AGENT_SECRET: yoursecret`
{% endhint %}
{% endtab %}
{% endtabs %}
Log into Portainer and connect to the Kubernetes environment where Portainer is installed. From the menu select **Applications** then select **Create from manifest**. Toggle **Use namespace(s) specified from manifest** to on, then enter `portainer` in the **Name** field. 
Log into Portainer and connect to the Kubernetes environment where Portainer is installed. From the menu select **Applications** then select **Create from manifest**. Toggle **Use namespace(s) specified from manifest** to on, then enter `portainer` in the **Name** field.
{% hint style="warning" %}
If you used a different name for your Portainer deployment, use that instead.
@@ -172,7 +176,7 @@ kubectl apply -n portainer -f https://downloads.portainer.io/ce-lts/portainer-ag
If you have set a custom `AGENT_SECRET` on your Portainer Server instance (by specifying an `AGENT_SECRET` environment variable when starting the Portainer Server container) you must remember to explicitly provide the same secret to your Agent in the same way (as an environment variable) in the YAML when updating your Agent:
`environment:`\
  `- AGENT_SECRET: yoursecret`
`- AGENT_SECRET: yoursecret`
{% endhint %}
{% endtab %}
@@ -210,7 +214,7 @@ If you have set a custom `AGENT_SECRET` on your Portainer Server instance you mu
`environment:`
  `- AGENT_SECRET: yoursecret`
`- AGENT_SECRET: yoursecret`
{% endhint %}
{% endtab %}
{% endtabs %}