This repository has been archived.
Portainer 2.0 includes support for Kubernetes, head to https://www.portainer.io/installation/ for more details about how to install it.
This repository has been specifically created to capture the community feedback around Portainer for Kubernetes BETA version.
This "point in time" version of Portainer allows you to manage one or more Kubernetes cluster(s) through the familiar Portainer experience. It's primary goal is to make it simple for any user to deploy and troubleshoot their applications inside a Kubernetes environment.
In this special build, we have removed all Docker Standalone and Docker Swarm management functionality, so as to focus solely on obtaining feedback on Kubernetes features. This is ONLY FOR THIS BETA build.
The release version of Portainer CE (2.0) will include support for Docker Standalone, Docker Swarm AND Kubernetes, within the one instance.
The entire purpose of this BETA is to gather feedback from the Portainer user community. It will not have any new releases or patches (unless critical), and this BETA version will be removed post BETA.
Be sure to read the FAQ section below for current known limitations and other sections for more information.
Depending on your Kubernetes cluster provider, follow the instructions available in the Kubernetes manifests repository.
Be wary that this a BETA version and as such, might contain some bugs. It is not recommended to deploy this version in a production environment.
IF you have an issue with the deployment of this version inside your Kubernetes cluster, please comment on the deployment topic.
If you have feedback, positive or negative about the BETA version of Portainer for Kubernetes we welcome this with open arms.
We are building to a product usability principle of KISS (Keep it Simple, Stupid), so the UX/UI will remain uncluttered with as little Kubernetes jargon as possible. For this reason, feedback will be viewed through the lens of "how can we add that whilst remaining true to our principles".
To make it simpler for everyone to provide and follow feedback, we have created a list of topics around different areas that you can comment about.
-
Want to report a bug with this BETA? Use the following bug report template to report it.
-
Would you like to report a feature/enhancement request and you haven't found any topics to comment in? Use the following enhancement request template.
-
We also have a generic feedback template for any feedback that would not fit into the categories specified above.
You can also join us on Slack to discuss it in our #kubernetes-beta channel.
This version of Portainer has been successfully deployed inside the following cloud provider Kubernetes clusters:
- DigitalOcean
- Azure AKS
It has also been successfully deployed through the following local cluster providers:
- minikube
- kind
Currently tested against the following Kubernetes versions:
- 1.15.7
- 1.16.2
- 1.17.4
NOTE: This version has not been tested against Kubernetes 1.18 as of yet.
We would really value input on "known good" deployments, so we can expand this list above in conjunction with our users. If you have deployed Portainer successfully and validated all features/functions work well, please let us know.
You can comment in one of our platform related topics or open a new feedback request.
This version of Portainer will be open to feedback between the 1st of April 2020 until the 30th of April 2020.
Our plan is to merge support for Kubernetes inside the Portainer CE version 2.0 around June 2020.
More information about our plan to support Kubernetes inside Portainer in our Kubernetes roadmap.
Feel free to contribute in there too!
In the BETA, we have not configured Portainer to persist its configuration. This is, in part, to discourage its use in Production environments. However, if you wish to persist the data, you need to manually edit the deployment instructions to persist the /data container folder.
Why am I not seeing all the deployed applications running inside my cluster in the Applications list?
In this current BETA, Applications will only display the following Kubernetes workloads: Deployments, StatefulSets and DaemonSets.
We'll add support for isolated pods in a future version, see portainer/portainer#4011