Containers & Developer Tools
Managed Kubernetes
A managed cluster service that simplifies Kubernetes.
Enterprise Kubernetes Platform Deployment & Operations
Run your containerized applications and virtual machines on one platform
The enterprise Kubernetes platform is installed in your environment and handed over running, with a container registry, monitoring and a delivery pipeline. After installation, upgrades, capacity and incident tracking can stay within the service.
Service scope
Containers and virtual machines together
An application that can’t move to containers runs as a virtual machine on the same platform, and you modernize in the order you choose.
Container registry
Your container images are kept in a registry in your own environment and scanned for known vulnerabilities.
Delivery pipeline
Code is tested when it is pushed, and the approved release is deployed automatically.
Monitoring and logs
Cluster, application and virtual machine metrics and logs are collected in one place, and crossed thresholds raise alerts.
Identity and access
The platform connects to your identity system, and each team sees only the resources in its own space.
Planned upgrades
New releases are tested in a test environment first, then rolled into production in a planned window.
How to get started
- 1
Discovery
Your applications, teams, current virtual machines and release process are mapped.
- 2
Design
Network, storage, identity integration and environment separation (development, test, production) go into a written design.
- 3
Installation
The platform is installed with its registry, monitoring, log collection and delivery pipeline, following the design document.
- 4
First applications
A containerized application and a virtual machine chosen with your team move onto the platform, and the pipeline is proven on real work.
- 5
Operations
Upgrades, capacity tracking and incident response run within the service; the scope is written into the contract.
Who does what
| Included in the service | On your side |
|---|---|
| Platform design and installation | Application code and container images |
| Registry, monitoring and pipeline setup | Deployment definitions and environment settings |
| Release upgrades and security patches | Users, teams and permissions |
| Capacity tracking and incident response | The content of application data |
| Documentation and team training | Approval to release to production |
Related products
Containers & Developer Tools
CI/CD Pipeline
A managed pipeline that builds, tests and deploys code.
Monitoring & Management
Monitoring & Alerts
Metrics, alerts and health status for your VMs.
Frequently asked questions
- We have no Kubernetes specialists. Can we use this platform?
- Yes. The platform is delivered with working defaults: your team connects its application to the pipeline, and running the cluster stays within the service. Hands-on training is part of the installation.
- Do we have to rewrite our current virtual machines?
- No. Virtual machines move onto the platform as they are and talk to containers on the same network. Converting an application to containers is optional and happens on your timeline.
- Do our applications stop during an upgrade?
- Upgrades are tested in a test environment first, then nodes are updated one by one in a planned window. Applications running with more than one replica keep serving throughout.
- Are we locked in to the provider?
- No. The platform uses standard Kubernetes interfaces, and your application definitions and container images stay yours. When the service ends, the platform can be handed to your team.
- How is the service scope defined?
- Which components are monitored, how incidents are handled and the release calendar are written into the service contract.
- How is it priced?
- Installation is priced as a project by platform size and scope; operations are a separate monthly item.
About the related products
Managed Kubernetes
- What are the benefits of Managed Kubernetes?
- The cluster, network, load balancer and container registry come ready, so your teams spend their time on applications instead of infrastructure.
- How long does a cluster take to be ready?
- About 20 minutes after the quote is approved.
CI/CD Pipeline
- How long does a release take to reach production?
- About 2 minutes after the release tag is created.
Take the next step
Tell us about your applications and teams; a written design and price proposal follows the call.