For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.us.ovhcloud.com/en/public-cloud/managed-kubernetes/objects.md.
  • English

Managed Kubernetes objects (services, deployments, pods...)

View as Markdown

These objects are created either at cluster creation or at node creation, and they enable cluster operations and management.

Please refrain from deleting or otherwise altering them!

 

Namespaces

There are several existing namespaces running in your cluster:

  • default: namespace by default
  • kube-node-lease: for heartbeat Node's lease object
  • kube-public: reserved mainly for cluster usage & in case of specific resources which should be publicly available
  • kube-system: for objects created by Kubernetes

The following resources are running in these namespaces.

 

Services

Several management services are running in your cluster:

  • kubernetes
  • kube-dns
  • metrics-server
  • wormhole

In my example cluster, I get:

$ kubectl get services --all-namespaces
NAMESPACE     NAME                        TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)                  AGE
default       kubernetes                  ClusterIP      10.3.0.1       <none>           443/TCP                  14d
kube-system   kube-dns                    ClusterIP      10.3.0.10      <none>           53/UDP,53/TCP,9153/TCP   14d
kube-system   metrics-server              ClusterIP      10.3.224.150   <none>           443/TCP                  14d
kube-system   wormhole                    ClusterIP      10.3.0.2       <none>           443/TCP                  14d

 

Deployments

To implement these services, you will find several deployment objects:

  • coredns
  • kube-dns-autoscaler
  • metrics-server

In my example cluster, I get:

$ kubectl get deployments --all-namespaces
NAMESPACE     NAME                        READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   coredns                     2/2     2            2           14d
kube-system   kube-dns-autoscaler         1/1     1            1           14d
kube-system   metrics-server              1/1     1            1           14d

 

Daemon sets

There are also several daemonsets to define the pods that will be deployed on every node:

  • canal
  • kube-proxy
  • wormhole

In my example cluster, with 5 nodes, I get:

$ kubectl get daemonsets --all-namespaces
NAMESPACE     NAME         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
kube-system   canal        3         3         3       3            3           beta.kubernetes.io/os=linux   14d
kube-system   kube-proxy   3         3         3       3            3           <none>                        14d
kube-system   wormhole     3         3         3       3            3           <none>                        14d

 

Replica sets

There are also several replicasets to define the pods that will run on several instances:

  • coredns-*
  • kube-dns-autoscaler-*
  • metrics-server-*

In my example cluster, I get:

$ kubectl get replicaset --all-namespaces
NAMESPACE     NAME                                   DESIRED   CURRENT   READY   AGE
kube-system   coredns-77b9fbd56                      2         2         2       14d
kube-system   kube-dns-autoscaler-ddf4c7d5b          1         1         1       14d
kube-system   metrics-server-66bb5cd998              1         1         1       14d

 

Pods

You will find one instance of the following pods running in every node of your cluster:

  • canal
  • proxy
  • wormhole

You will also find one global instance of:

  • kube-dns-autoscaler
  • metrics-server

And several instances of:

  • coredns

In my example cluster, with 3 nodes, I get:

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                         READY   STATUS    RESTARTS      AGE
kube-system   canal-lcmmw                                  2/2     Running   2 (14d ago)   14d
kube-system   canal-ljcfj                                  2/2     Running   2 (14d ago)   14d
kube-system   canal-x56p5                                  2/2     Running   1 (14d ago)   14d
kube-system   coredns-77b9fbd56-4s8mb                      1/1     Running   0             14d
kube-system   coredns-77b9fbd56-fslpn                      1/1     Running   0             14d
kube-system   kube-dns-autoscaler-ddf4c7d5b-chzvs          1/1     Running   0             14d
kube-system   kube-proxy-5qs2t                             1/1     Running   0             14d
kube-system   kube-proxy-qb8h9                             1/1     Running   0             14d
kube-system   kube-proxy-xws7j                             1/1     Running   0             14d
kube-system   metrics-server-66bb5cd998-rs46p              1/1     Running   0             14d
kube-system   wormhole-7cbmc                               1/1     Running   0             14d
kube-system   wormhole-7dt6x                               1/1     Running   0             14d
kube-system   wormhole-vh7pk                               1/1     Running   0             14d

 

Go further

Browse all the Managed Kubernetes Service (MKS) guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Managed Kubernetes on the OVHcloud US website.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.