With all the fanfare surrounding Kubernetes, I often wonder why a product so operationally complex is winning hearts and minds of IT folk so easily.
To be clear, when I say "Kubernetes" what I mean is self-built/managed deployments, not the "as a service" Kubernetes powered offerings from Cloud Providers, which to be fair, remove 95% of the complexity.
With the release of Docker for Windows 10, more and more users are wanting to experiment, and many want to use Portainer as a UI to manage the Docker daemon.
Unfortunately, Docker to make exposing the Daemon externally all that straight forward, so I will show you how its done (note that I DO NOT recommend exposing the Daemon without any TLS authentication, you should always configure your Daemon with TLS to ensure only authorised people can manipulate your Docker Daemon):
REVISED MARCH 2020
Portainer can be configured to accept Lightweight Directory Access Protocol (LDAP) authentication if your organization has implemented LDAP or Active Directory authentication. When users attempt to log into Portainer, the application will authenticate them against your LDAP directory or Active Directory.
Storage is Changing; analytics, file stores, research data, disk to disk backups and other new workloads are placing a strain on traditional IT storage technology. New workloads demand new protocols and APIs like S3, Swift and Hadoop, but it’s not always silos.
One of the great benefits of Docker is that it enables a seamless CI/CD process; Containers are simply a running read only instance of a Docker Image, and updating a container is as simple as updating the image file and then redeploying the container from the updated image.
Containers have become one of the major themes in the IT industry, following the rise to prominence of Docker and its platform. The technology has found popularity because it meshes well with a need for greater efficiency, reduction in IT costs, and increasing agility in development and IT operations.
Configuration Management is a process whereby infrastructure services are provisioned and configured remotely either through remote agents, REST API or command line tools based on machine-readable definition files. This enables an entire, fully functional, application ready environment to be deployed and started with a single command line.
With the release of Portainer 1.13.2 we now have the ability to create and assign "Secrets" to Docker Swarm Services. This is a big improvement in security as it means sensitive information (such as passwords) do not need to be passed to containers through plain-text environment variables.
With the release of Portainer 1.13, we have extended the RBAC function to include Team management. This new feature means that you can now assign users into teams, authorise teams to access endpoints, enable containers/services/volume management at the team level, and really, just provide fine grained access control.