History

samdulam 3ee87c0b99 Prep Chart for EE2.7 (#68 ) * bump chart ver, agent tag in manifests for ce 2.6 * EE 2.7.0 and chart version bump		2021-07-29 18:29:38 +12:00
..
ee	Prep Chart for EE2.7 (#68 )	2021-07-29 18:29:38 +12:00
README.md	feat(manifests): update README	2020-12-02 08:15:39 +13:00
portainer-agent-edge-k8s.yaml	feat(agent): version files	2021-07-14 13:31:42 +03:00
portainer-agent-k8s-lb.yaml	bump chart ver, agent tag in manifests for ce 2.6 (#65 )	2021-06-25 14:17:24 +12:00
portainer-agent-k8s-nodeport.yaml	bump chart ver, agent tag in manifests for ce 2.6 (#65 )	2021-06-25 14:17:24 +12:00
portainer-ce29-agent-edge-k8s.yaml	feat: update to use the same filenames	2021-07-14 14:10:16 +03:00
portainer-ce29-edge-agent-setup.sh	feat: update to use the same filenames	2021-07-14 14:10:16 +03:00
portainer-edge-agent-setup.sh	feat(agent): version files	2021-07-14 13:31:42 +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.