History

Chaim Lev-Ari 75860ddfb3 fix(edge): take agent_secret		2022-04-12 17:46:34 +03:00
..
ee	fix(edge): take agent_secret	2022-04-12 17:46:34 +03:00
README.md	feat(manifests): update README	2020-12-02 08:15:39 +13:00
portainer-agent-edge-k8s.yaml	refactor: revert changes to current files	2022-04-12 10:59:17 +03:00
portainer-agent-k8s-lb.yaml	Bump version to 2.11.1 (#96 )	2022-02-08 11:44:59 +13:00
portainer-agent-k8s-nodeport.yaml	Bump version to 2.11.1 (#96 )	2022-02-08 11:44:59 +13:00
portainer-ce211-agent-edge-k8s.yaml	refactor: revert changes to current files	2022-04-12 10:59:17 +03:00
portainer-ce211-edge-agent-setup.sh	refactor: revert changes to current files	2022-04-12 10:59:17 +03:00
portainer-ce213-agent-edge-k8s.yaml	fix(edge): take agent_secret	2022-04-12 17:46:34 +03:00
portainer-ce213-edge-agent-setup.sh	fix(edge): take agent_secret	2022-04-12 17:46:34 +03:00
portainer-edge-agent-setup.sh	refactor: revert changes to current files	2022-04-12 10:59:17 +03:00

Agent

The manifests used to deploy the Portainer agent inside a Kubernetes cluster.

NOTE: Manifests to deploy the Portainer agent Enterprise Edition are available in the ee folder.

To deploy an Edge agent inside your Kubernetes cluster, it is recommended to follow the instructions available inside your Portainer instance.

Usage

If your cloud provider supports external load balancers, you can use the following command to deploy the regular Portainer agent (not Edge):

kubectl ... apply -f portainer-agent-k8s-lb.yaml

This will deploy the Portainer agent and create an external load balancer which you'll be able to use to connect to the agent on port 9001.