- About Us
- Get Help
The ability to set up, manage and configure a containerized environment is central to the Platform Engineer's (or SREs) role.
Portainer Business' platform management functionality allows engineers to both configure the orchestrator and then set up configuration 'rules' which define what users of the platform (typically developers) can and can't do inside the environment.
Portainer is tested against Docker on Windows, Docker on Linux/AMD64, Docker on Linux/ARM64, Kubernetes on Linux, and Azure ACI. It is validated against the current version of Docker/Kubernetes at the time of each release as well as being validated on the two prior major versions.
Portainer is platform agnostic and thus doesn’t care if your environment is running on your laptop, in your datacentre or through a managed service. As long as you can deploy the Portainer Agent - which facilitates management of the underlying platform – you can use Portainer. Portainer does not create new clusters for you, instead it manages the clusters you give it access to. You still need to deploy clusters externally, however this process is getting much easier thanks to bootstep tools. Of course, cloud providers make this process completely invisible to you.
Portainer lets you define any number of container registries - public or private, secure or open - and then allows you to assign access to users. Only authorized users are able to pull/push from any given registry which makes Portainer a great way to secure access to your internal container image repositories and a simple way to define and secure access across your organization.
Portainer lets you browse and interact with the remote registry, performing tasks such as image retagging, or deletion; this feature removes the need for additional 3rd party registry management tools as you can perform all essential image management functions from Portainer. Learn more about Registry Management.
From a provisioning perspective, Portainer supports the creation of persistent volumes against either a local path on a docker host, or a CIFS share, or a NFS mount.
Portainer provides authorized users with the ability to browse the persistent volumes attached to containers. Users can interact directly with the volume content, either uploading/downloading files, or renaming/deleting.
In a Kubernetes environment, Portainer allows users to specify the maximum size of their requested volume when created. It then allows the administrator to expand the capacity allocated to their persistent volume. In addition, Portainer displays all volumes for a given backend storage type so as to visually show the allocated capacity.
Making sure applications are properly networked within clusters is critical and Portainer makes it easy. For Docker, you can create and use additional bridge, overlay, or MACVLAN networks. For Kubernetes, you can configure and use Ingress and Load Balancers across the cluster.
Portainer allows users to publish their application via a Kubernetes Ingress controller (reverse proxy) which includes defining the http routes, rewriting headers, or performing SSL offload.
Portainer allows users to publish their application via a Kubernetes Load Balancer (or Swarm Ingress), which provides enables their application to be globally visible across the cluster.
Ensuring Portainer Business customers get the best possible experience is important to us, which is why we've developed a comprehensive Customer Success Programme for all users.
The Programme starts with a virtual one-on-one onboarding session during which a member of the Portainer Customer Success team will evaluate your environment then work with you to ensure Portainer is optimized to give you the insights you need.
Should you run into problems you have access to two tiers of Support – 24x7 or 9x5 depending on what you purchased for the nodes in question. The Support team is highly skilled and fully equipped to deal with any size of issue. You’ll also get regular contact and updates from Portainer to ensure you are getting the absolute best out of your investment.