Portainer is an open-source tool for Building and Managing docker environments with ease. It has been widely adopted by the community over time with over 2 billion downloads.
Guess whatPortainer for KUBERNETES (beta edition) has been released and this is a really good deal out there for developers. In this post, we will discuss how to setup Portainer for kubernetes in less than 60 seconds using ARKADE.
It is with great delight that I am able to announce the public BETA release of Portainer, with support for Kubernetes.
We have just pushed the images to Docker Hub, published the release notes, created all the backing documentation to support user feedback, and have completed our functional testing.
Hi Portainer fans... time for a little update..
Sorry for the long delay between blog posts, but our little team has been kept quite busy building support for Kubernetes into Portainer, working on our next release, and extending our Edge Compute functionality.
As we have been completing extensive testing of the upcoming Portainer 1.23.2 release, we have struggled to workaround four persistent issues with Docker when running atop of Windows 10 and Windows Server 2019.
If you are using Portainer on Windows Server 2019, and you are running in SWARM MODE, then you dont need to worry, as these bugs do not impact you.
If you are reading this post, i will assume by now that you have heard/read the news of Docker EE’s acquisition by Mirantis, and their eventual sun-setting of Swarm within the next 2 years.
It’s important to me to explain to our user community that this does not materially impact Portainer or our vision.
Before a release is initiated, the entire Portainer team dedicate time to complete comprehensive testing of the portainerci/portainer:develop & portainerci/agent:develop images.
By popular demand, i will quickly show you the process to get Portainer and the Portainer Agent running in a Docker Swarm environment atop Windows Server 2016 or 2019.
Deploying Portainer and the Portainer Agent to manage a Windows 2016 (1803) or Windows 2019 (1903) Swarm cluster is easy !
This procedure ONLY works if you are running Docker EE 19.03.5 or later, so if you are not, update before continuing.
Now that the edge agent has been released, let me give a brief overview of how it works. Note that deep technical documentation will be made available in the agent repo on github in due course.
In standard deployments, the central Portainer instance and any endpoints it manages are assumed to be on the same network, that is, Portainer and the agents are able to seamlessly communicate to one another.
With the adoption of containers continuing to accelerate, we are seeing deployments of the Docker engine extending beyond the server. Containers are making an appearance in everything from storage devices and Ethernet switches, though to IOT monitoring/control equipment.
We have been asked for over a year now what our "Kubernetes Strategy" is, and our answer has always been the same:
"Portainer's sole reason for being is to simplify container platform operations; when Kubernetes gets simplified, we will integrate it into Portainer".
Well, we have come to a point where we now believe that its impossible to simplify Kubernetes to a level where we can verbosely pass through and visualize its plethora of functions 1:1, akin to what Kubernetes' native dashboard does.