These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Container & K8s Management
- Implementation and migration
How a Container & K8s Management rollout works
Start with a named cluster and service, then rehearse evidence and decisions.
Set the operating boundary
Choose the first clusters, services and workloads. Name their owners and agree which outside systems provide live readings and deployment execution.
Map identities and records
Link People to Users, Services to owners and Assets, and deployment observations to Clusters. Preserve stable event identifiers during any import.
Configure the pilot
Use a production and a test cluster with a recognizable workload. Record an observation, open an incident for the affected service and assign the responder.
Rehearse decisions
Have the Change Approver judge a planned window and rollback plan. Test an approved and rejected request, a rolled-back change and a failed integration receipt.
Review and release
Compare source events and imported records, check role access, and confirm that later observations and incident updates explain the operating outcome.
What the customer provides
- Cluster names, environment labels, provider details and responsible people.
- Services, criticality, owners and asset tags linked to those services.
- A representative workload, namespace and dated desired and ready replica readings.
- The people who respond to incidents and decide changes and service requests.
- Source event identifiers and connection details for any telemetry or deployment systems.
Changing it afterwards
Use Proto to prepare new mappings, views or access rules for review. Test them against the same cluster and service case before release. Keep earlier observation times, incident updates and change outcomes interpretable after a configuration change.
Set up Container & K8s Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.