This repository contains all the manifests you can use to deploy the Portainer for Kubernetes BETA version.
For any feedback regarding the BETA version, please head to the portainer for Kubernetes BETA repository.
These manifests have been tested on:
Have any feedback on the deployment of Portainer inside Kubernetes? Please head to the deployment feedback topic.
Supported platforms:
If your cloud provider supports external load balancers, you can use the following commands to deploy Portainer:
curl -LO https://raw.githubusercontent.com/portainer/portainer-k8s/master/portainer.yaml
kubectl apply -f portainer.yaml
This will deploy the Portainer application and create an external load balancer which you’ll be able to use to access Portainer on port 9000.
If you prefer to access Portainer via a specific port on a node of your cluster, use the following commands:
curl -LO https://raw.githubusercontent.com/portainer/portainer-k8s/master/portainer-nodeport.yaml
kubectl apply -f portainer-nodeport.yaml
This will expose Portainer on the port 30777
inside your cluster (30776
for Edge tunnel server). You can change these ports inside the manifest if you wish.
Work-in-progress.
In order to manage a remote Kubernetes cluster, you’ll need a Portainer for Kubernetes BETA instance already deployed inside a Kubernetes cluster and connect it to a Portainer agent running inside the remote cluster.
If your cloud provider supports external load balancers, you can use the following command to deploy the regular Portainer agent (not Edge):
curl -LO https://raw.githubusercontent.com/portainer/portainer-k8s/master/agent/portainer-agent.yaml
kubectl apply -f agent/portainer-agent.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.
If you wish to deploy the Edge agent inside your Kubernetes cluster, it is recommended to follow the instructions available inside your Portainer instance.
If you wish to deploy Portainer or the agent inside a Kubernetes cluster running on arm, please use the tag linux-arm
instead of linux-amd64
.