search
Get Started
search
IBM Cloud Kubernetes Service - Containerization
zoom_in Click to enlarge

IBM Cloud Kubernetes Service

language

description IBM Cloud Kubernetes Service Overview

IBM Cloud Kubernetes Service is a managed Kubernetes offering for deploying and operating containerized applications on IBM Cloud. IBM manages the Kubernetes control plane, while customers define worker nodes, networking, storage, application deployments, and access policies within their clusters. The service is intended for development and operations teams that want standard Kubernetes APIs and tooling without building the entire cluster-control infrastructure themselves.

help IBM Cloud Kubernetes Service FAQ

Which part of IBM Cloud Kubernetes Service does IBM manage for me?

IBM manages the Kubernetes master or control plane, including monitoring and updates, while customers define worker nodes, workloads, networking, storage, and access policies. IBM's documentation describes three master replicas for high availability in classic and VPC clusters. [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-overview)

Can IBM Cloud Kubernetes Service run on VPC, classic infrastructure, or Satellite?

Yes, IBM documents cluster options for VPC, classic infrastructure, and Satellite. VPC clusters use IBM Cloud virtual machines, classic clusters can use virtual or bare-metal workers, and Satellite can place worker nodes in a customer's location or another cloud. [IBM infrastructure options](https://cloud.ibm.com/docs/containers?topic=containers-overview)

What is the difference between a worker pool and a worker node in IBM Cloud Kubernetes Service?

A worker node is an individual compute host that runs Kubernetes pods, while a worker pool groups nodes with the same CPU, memory, operating-system, and storage profile. The Kubernetes master schedules deployments onto nodes with enough available capacity. [IBM Kubernetes concepts](https://cloud.ibm.com/docs/containers?topic=containers-overview)

Will persistent storage survive deleting a pod or worker node?

IBM says data on persistent storage remains even when the container, worker node, or cluster is removed. Non-persistent storage can disappear when its container, worker node, or cluster is removed. [IBM storage overview](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan)

Reviews & Comments

Write a Review

rate_review

Be the first to review

Share your thoughts with the community and help others make better decisions.

Save to your list

Save your favorites and follow how their scores change over time.

Save favorites
Track changes
Compare scores

Already have an account? Sign in

Compare Items

See how they stack up against each other

Comparing
VS
Select 1 more item to compare