Kubernetes Cluster API

Transcript

1. KUBERNETES Cluster API erkan_erol_
2. About me - Live in Istanbul/Türkiye - Platform Engineer @ Giant Swarm - Netaş -> SAP -> Red Hat - Kubernetes ~ 5 years - Kubernetes operators ~ 3 years - Cluster API ~ 1 year Erkan Erol
3. Disclaimer - This presentation contains some icons from flaticon.com - This talk contains some copy-paste content from Marcel Müller (twitter.com/MueMarcel)’s old talk. Scope For Cluster API users, not for provider maintainers.
4. The story How did we get to this point?
5. Everything started with its birth…
6. Installation was not easy. There were many tools.
7. People were implementing systems to manage lifecycle of Kubernetes clusters. Kubernetes Cluster WEB UI STORAGE API AUTOMATION (consumes the tools) CLI
8. People started to use k8s to deploy standard workloads by using built-in types. Kubernetes DEPLOYMENT STATEFULSET
9. People liked Kubernetes paradigm. : I desire this state. : Here it is.
10. CONTROLLER PATTERN In robotics and automation, a control loop is a non-terminating loop that regulates the state of a system.
11. CONTROLLER PATTERN In Kubernetes, controllers are control loops that watch the state of your cluster, then make or request changes where needed. YAML POD
12. Control Plane Node etcd api-server controller-manager scheduler kubelet kube-proxy … Kubernetes Architecture is actually so simple …
13. Control Plane Node etcd api-server controller-manager scheduler kubelet kube-proxy … storage(etcd) + common api + controllers …
14. Control Plane Node etcd api-server controller-manager scheduler kubelet kube-proxy … Why don’t we add yet another controller? … custom-controller
16. Operator Pattern - aims to capture the key aim of a human operator - how the system ought to behave - how to deploy it - how to react if there are problems - k8s operator = one or more controllers for a specific thing - e.g. MySql Operator, Prometheus Operator etc.
17. People ♥liked♥ this more : I desire this : Here it is. prometheus-operator
18. Not only k8s resources but also external resources too. : Here it is. : I desire this crossplane
19. WHY DON’T WE USE OPERATORS TO MANAGE KUBERNETES CLUSTERS?
20. LET’S STANDARDIZE!
21. And it was born
22. Cluster API Fundamentals The Tortoise Trainer
23. Cluster API Controllers Cluster 1 I desire this Clusters watch manage Management Cluster (MC) Cluster 2 Cluster 3 Workload Cluster (WC) CRs
24. To understand the solution, Let’s think about the problem at first.
25. What do we need to create a k8s cluster?
26. 1. We need infra resources Machines / VMs Networking Storage Infrastructure Provider
27. Current Infrastructure Providers • AWS • Azure • Azure Stack HCI • BYOH • CloudStack • DigitalOcean • Equinix Metal • GCP • Hetzner • Outscale • IBM Cloud • 🤍KubeVirt🤍 • MAAS • Metal3 • Microvm • Nested • Nutanix • OpenStack • OCI • Sidero • Tencent Cloud • vcluster • Virtink • VMware Cloud Director • vSphere We will use it as an example in the upcoming slides
28. 2. We need to convert machines to k8s nodes Bootstrap Provider Node - certificates - joining tokens - kubelet
29. Current Bootstrap Providers • EKS • Kubeadm • Talos We will talk about only this one
30. 3. We need a control-plane to join our nodes Control Plane etcd api-server controller-manager scheduler … ControlPlane Provider
31. ControlPlane Provider Types • Self-provisioned ➢ In WC, controlled by Cluster API ➢ e.g. KubeadmControlPlane • Pod-based ➢ In external cluster, pod based, exposed by a k8s service • External or Managed ➢ controlled by another system like GKE, AKS, EKS, etc. We will talk about only this one
32. Cluster API components are interchangeable! Core Infrastructure Provider Bootstrap Provider ControlPlane Provider Always the same! Full interchangeable (In theory)
33. MC WC 1 manage WC 2 WC 3 Core Operator Infrastructure Operator Bootstrap Operator ControlPlane Operator kubectl clusterctl BIG PICTURE
34. clusterctl - The clusterctl CLI tool handles the lifecycle of a Cluster API management cluster. - It automates fetching the YAML files defining provider components and installing them.
35. clusterctl init example
36. clusterctl move MC 1 WC 1 is managing MC 2 will manage
37. DREAM vs REALITY THIS NAIVE BOY
38. DREAM vs REALITY There is no one or few common CRs for all providers. Each provider has its own CRs.
39. Deep Dive
40. Deep Dive Stack - Core Operator - Openstack as infra provider - Kubeadm as bootstrap provider - KubeadmControlPlane as controlplane provider These are just examples to understand the concepts. Don’t forget
41. I want to create a cluster with Cluster API. How can I do it?
42. kind: Cluster - Managed by “capi-controller-manager” (Core Operator) - Main CR - Give reference to infra provider - Give reference to controlplane provider (Optional)
43. kind: Cluster : Spec apiVersion: cluster.x-k8s.io/v1beta1 kind: Cluster spec: … controlPlaneRef: apiVersion: controlplane.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane name: demo1 namespace: org-multi-project infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackCluster name: demo1 namespace: org-multi-project As as Cluster API user I want to have a cluster With this control plane provider On this infra provider
44. kind: InfraCluster - e.g. OpenStackCluster - Managed by “capo-controller-manager” (Infra Operator) - CR to declare common/primary infra resources for the cluster - Project / Account in infra provider - Credentials to access infra provider - VPC / Network configuration - Region / Availability Zone / Failure Domains
45. kind: InfraCluster : Spec apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackCluster identityRef: kind: Secret name: cloud-config managedSecurityGroups: true apiServerLoadBalancer: enabled: true externalNetworkId: 43fb-b0a9-312f0abf8f12 network: demo1-example-network nodeCidr: 10.6.0.0/24 controlPlaneAvailabilityZones: - gb-lon-1 Authentication Networking Failure Domains Infra Specific Security Settings Infra specific CR
46. With Cluster + InfraCluster, we created some basics like project, vpc, security groups, LB for k8s api etc. but we still don’t have any machine! VPC / Network WE NEED MACHINES HERE!
47. kind: Machine - Managed by “capi-controller-manager” (Core Operator) - Give reference to infra provider - Give reference to bootstrap provider (Optional)
48. kind: Machine : Spec apiVersion: cluster.x-k8s.io/v1beta1 kind: Machine spec: infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachine name: demo1-default-91da4cd9-m7gn2 namespace: org-multi-project uid: d7ac11dd-d41c-40a4-9a4b-ab2fe5dd71ad bootstrap: configRef: apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmConfig name: demo1-region1-8342e0a3-lwlqx namespace: org-multi-project uid: 5a31ddc4-92e3-4bc9-9af3-d7827e6366fc dataSecretName: demo1-region1-8342e0a3-lwlqx As as Cluster API user I want to have a machine On this infra provider With this bootstrap configuration
49. kind: InfraMachine - e.g. OpenStackMachine - Managed by “capo-controller-manager” (Infra Operator) - CR to declare machine spec - Image - Size / Flavor - Network / Subnet - Volumes - …
50. kind: InfraMachine : Spec apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachine spec: identityRef: kind: Secret name: cloud-config flavor: n1.medium image: ubuntu-2004-kube-v1.22.8 rootVolume: diskSize: 60 Infra specific CR Authentication Machine Spec
51. OK. We have a machine now. Let’s talk about how to bootstrap it. VPC / Network
52. Kind: KubeadmConfig - Managed by “capi-kubeadm-bootstrap-controller-manager” (Bootstrap Operator) - CR to declare - Bootstrap configuration like kubeadm config - Files to mount - Users to create - Commands to run
53. kind: KubeadmConfig : Spec apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmConfig spec: files: - content: | ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AA... path: /etc/ssh/trusted-user-ca-keys.pem permissions: "0600" joinConfiguration: discovery: bootstrapToken: apiServerEndpoint: xxx.yyy.ttt.zzz:6443 token: u7zw64.mytoken nodeRegistration: kubeletExtraArgs: eviction-hard: memory.available<200Mi feature-gates: ExpandPersistentVolumes=true name: '{{ local_hostname }}' postKubeadmCommands: - systemctl restart sshd format: cloud-config As as Cluster API user I want to bootstrap my machine By injecting these files By using this join configuration By using this kubelet configuration By running these commands By using this format
54. How the bootstrapping works - 1 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmConfig status: dataSecretName: demo1-region1-8342e0a3-lwlqx ready: true Bootstrap operator creates a secret based on the spec in the KubeAdmConfig CR.
55. How the bootstrapping works - 2 ## template: jinja #cloud-config write_files: - path: /etc/ssh/trusted-user-ca-keys.pem permissions: '0600' content: | ssh-ed25519 dfdsfs vault-ca@vault.operations.giantswarm.io - path: /run/kubeadm/kubeadm-join-config.yaml owner: root:root permissions: '0640' content: | --- apiVersion: kubeadm.k8s.io/v1beta3 runcmd: - kubeadm join --config /run/kubeadm/kubeadm-join-config.yaml - "systemctl restart sshd" users: - name: giantswarm sudo: ALL=(ALL) NOPASSWD:ALL The secret content is in one of the supported formats. cloud-config files are special scripts designed to be run by the cloud-init service.
56. How the bootstrapping works - 3 Infra operator fetches bootstrap configuration from Machine CR (by following owner references) and uses that as user_data for cloud-init while creating a machine. KubeadmConfig k8s secret user_data kubeadm config real k8s configuration bootstrap operator infra operator cloud-init kubeadm init
57. We converted the machine to a k8s node, which is great! We plan to create more. Is there a way to manage them as a set instead of one by one? VPC / Network
58. Cluster API follows k8s approach! Deployment Replica Set Pod Machine Deployment Machine Set Machine
59. kind: MachineDeployment - Managed by “capi-controller-manager” (Core Operator) - Higher level CR to manage Machines like Deployment in Kubernetes - Refers update strategies and update configuration
60. kind: MachineDeployment : Spec apiVersion: cluster.x-k8s.io/v1beta1 kind: MachineDeployment spec: minReadySeconds: 0 progressDeadlineSeconds: 600 replicas: 5 selector: matchLabels: cluster.x-k8s.io/cluster-name: demo1 cluster.x-k8s.io/deployment-name: demo1-region1 strategy: rollingUpdate: maxSurge: 1 maxUnavailable: 0 type: RollingUpdate template: MACHINE_TEMPLATE part of core api machine spec update strategy like k8s deployment
61. Wait! To be able to create all these nodes, we need a control plane to join. Where is the control plane? In the beginning, in the Cluster CR, we mentioned KubeadmControlPlane. Let’s talk about it. VPC / Network
62. kind: KubeadmControlPlane - Managed by “capi-kubeadm-control-plane-controller-manager” (ControlPlane Operator) - Referred by Cluster - Refers control-plane configuration - api-server - controller-manager - scheduler - etcd - Contains fields of KubeadmConfig too since every control plane node is also a node :)
63. kind: KubeadmControlPlane : Spec - 1 apiVersion: controlplane.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane spec: kubeadmConfigSpec: clusterConfiguration: apiServer: extraArgs: enable-admission-plugins: NamespaceLifecycle,LimitRanger... controllerManager: extraArgs: authorization-always-allow-paths: /healthz,/readyz,/livez,/metrics bind-address: 0.0.0.0 etcd: local: extraArgs: listen-metrics-urls: http://0.0.0.0:2381 imageRepository: giantswarm imageTag: 3.5.4-0-k8s scheduler: Control-plane configuration
64. kind: KubeadmControlPlane : Spec - 2 apiVersion: controlplane.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane spec: kubeadmConfigSpec: files: format: cloud-config initConfiguration: joinConfiguration: preKubeadmCommands: machineTemplate: infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachineTemplate name: demo1-control-plane-91da4cd9 namespace: org-multi-project replicas: 3 rolloutStrategy: rollingUpdate: maxSurge: 1 type: RollingUpdate Like KubeadmConfig since all control-plane nodes are also nodes! Refers InfraMachineTemplate CR Like MachineDeployment but for control-plane machines
65. How control plane provisioning works - 1 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane metadata: name: demo1-rrsnf spec: kubeadmConfigSpec: clusterConfiguration: apiServer: certSANs: - 127.0.0.1 - localhost - api.demo1.test.erkan.io When cluster infrastructure is ready, ControlPlane operator provisions certificates and kubeconfig for the cluster. It puts those into k8s secrets. kind: Secret metadata: name: demo1-ca kind: Secret metadata: name: demo1-kubeconfig kind: Secret metadata: name: demo1-etcd kind: Secret metadata: name: demo1-sa kind: Secret metadata: name: demo1-proxy Everyone uses this to access WC.
66. How control plane provisioning works - 2 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane metadata: name: demo1-rrsnf spec: clusterConfiguration: controlPlanePart: standardNodeConfigurationPart: machineTemplate: infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachineTemplate name: demo1-control-plane-91da4cd9 ControlPlane operator creates a special KubeadmConfig for controlplane nodes by using control-plane specific and generic configuration in KubeadmControlPlane CR. This KubeadmConfig includes certificates too. kind: KubeadmConfig metadata: name: demo1-rrsnf
67. How control plane provisioning works - 3 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane spec: clusterConfiguration: controlPlanePart: standardNodeConfigurationPart: machineTemplate: infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachineTemplate name: demo1-control-plane-91da4cd9 ControlPlane operator creates a InfraMachine CR by using InfraMachineTemplate reference in KubeadmControlPlane CR. kind: OpenStackMachine metadata: name: demo1-control-plane-.... kind: KubeadmConfig metadata: name: demo1-rrsnf
68. How control plane provisioning works - 4 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane spec: clusterConfiguration: controlPlanePart: standardNodeConfigurationPart: machineTemplate: infrastructureRef: apiVersion: infrastructure.cluster.x-k8s.io/v1alpha5 kind: OpenStackMachineTemplate name: demo1-control-plane-91da4cd9 ControlPlane operator finally creates a Machine CR that refers the KubeadmConfig and InfraMachine CRs created earlier. kind: OpenStackMachine metadata: name: demo1-control-plane-.... kind: KubeadmConfig metadata: name: demo1-rrsnf kind: Machine metadata: name: demo1-9jngp spec: bootstrap: configRef: kind: KubeadmConfig name: demo1-rrsnf infrastructureRef: kind: OpenStackMachine name: demo1-control-plane-...
69. How control plane provisioning works - 5 As we talked earlier, Infra operator creates a machine by using cloud-config provided by Bootstrap operator. At the end, the created node is a control-plane node. kind: OpenStackMachine metadata: name: demo1-control-plane-.... kind: KubeadmConfig metadata: name: demo1-rrsnf kind: Machine metadata: name: demo1-9jngp spec: bootstrap: configRef: kind: KubeadmConfig name: demo1-rrsnf infrastructureRef: kind: OpenStackMachine name: demo1-control-plane-...
70. How control plane provisioning works - 6 apiVersion: bootstrap.cluster.x-k8s.io/v1beta1 kind: KubeadmControlPlane spec: replicas: 3 rolloutStrategy: rollingUpdate: maxSurge: 1 type: RollingUpdate ControlPlane operator provisions new control-plane nodes according to “replicas” field and rollout nodes during upgrades according to KubeadmControlPlane spec.
71. How control plane provisioning works - 7 - ControlPlane operator is not only creating machines like MachineSet. - It also access & manipulate workload cluster internals to manage control plane nodes in a stable way.
72. How control plane provisioning works - 8 https://github.com/kubernetes-sigs/cluster-api/blob/main/controlplane/kubeadm/internal/workload_cluster.go
73. VPC / Network Control Plane We have a fully working cluster now. 😎😎😎
74. RECAP-1 1. Cluster ControlPlane InfraCluster 2. ControlPlane InfraMachineTemplate 4. InfraCluster 3. MachineDeployment InfraMachineTemplate 6. KubeadmConfigTemplate 5. InfraMachineTemplate KubeadmConfigTemplate Encapsulation ControlPlane Workers
75. MC Core Operator Bootstrap Operator Infrastructure Operator ControlPlane Operator kubectl clusterctl RECAP - 2 Cluster Machine (Deployment / Set) KubeadmConfig KubeadmControlPlane InfraCluster InfraMachine
76. RECAP - 3
77. Let’s talk about interchangeability again.
78. An infra provider can implement only InfraCluster without using others CRs. It is up to infra provider. Cluster ControlPlane InfraCluster FullyManagedInfraCluster ControlPlaneConfig MachineConfig optional
79. A controlplane provider can provision the control plane in a cloud service without using bootstrap/machine apis. ManagedControlPlane My cloud credentials Control Plane Configuration WC Managed Control Plane
80. A bootstrap provider can bootstrap a machine by connecting it to through ssh and running commands without using cloud-init. It is up to bootstrap provider. bootstrap provider ssh
81. Cluster API components are interchangeable! Core Bootstrap Provider Infrastructure Provider ControlPlane Provider Always the same! Full interchangeable (In theory) We don’t have so many working examples yet.
82. BONUS PART Generated by DALL-E
83. kind: MachineHealthCheck apiVersion: cluster.x-k8s.io/v1beta1 kind: MachineHealthCheck metadata: name: demo1 spec: clusterName: demo1 maxUnhealthy: 40% nodeStartupTimeout: 20m0s selector: matchLabels: cluster.x-k8s.io/cluster-name: demo1 unhealthyConditions: - status: Unknown timeout: 10m0s type: Ready - status: "False" timeout: 10m0s type: Ready - Part of core api. - Core operator watches machine. If there is a machine which is not in Ready state, it deletes that machine and create a new one.
84. kind: ClusterResourceSet apiVersion: addons.cluster.x-k8s.io/v1beta1 kind: ClusterResourceSet metadata: name: demo1-coredns spec: clusterSelector: matchLabels: cluster.x-k8s.io/cluster-name: demo1 resources: - kind: ConfigMap name: demo1-coredns strategy: ApplyOnce As as Cluster API user In every cluster with these labels I want to create this k8s object automatically.
85. kind: ClusterClass - 1 - Experimental feature - Feature gate name: ClusterTopology - Creating a topology once and using many times
86. kind: ClusterClass - 2 - Experimental feature - Feature gate name: ClusterTopology - Creating a topology once and using many times
87. kind: MachinePool - 1 - Experimental feature - Feature gate name: MachinePool - Like MachineDeployment but doesn’t use MachineSet - Delegates the responsibility of these concerns to an infrastructure provider specific resource such as AWS Auto Scale Groups, GCP Managed Instance Groups, and Azure Virtual Machine Scale Sets.
88. kind: MachinePool - 2 MachineDeployment BootstrapConfig: KubeadmConfigTemplate infrastructureRef: AzureMachineTemplate MachinePool BootstrapConfig: KubeadmConfig infrastructureRef: AzureMachinePool
89. Let me talk about my company for 5 minutes But not like a salesman. It will be like tips and tricks.
90. Sauce of
91. App Platform - 1 MC Any App Catalog (Git Repo / OCR registry) create App CR App’s workloads manage (by using helm) pull https://docs.giantswarm.io/app-platform PUBLIC
92. App Platform - 2 https://docs.giantswarm.io/app-platform - There are lots of apps in the app catalogs - giantswarm/giantswarm-catalog - giantswarm/default-catalog - We use the app platform to create WCs too. - giantswarm/cluster-api-app - giantswarm/cluster-catalog - Upgrade = changing app version
93. Example Apps - Observability - Prometheus : You can access any WC by just changing a URL param - Grafana: There are many built-in dashboard - Loki, EFK stack - Note: GiantSwarm monitors all clusters and gives 7/24 support. - Security - Kyverno: There are some built-in policies for secure clusters - Falco - Trivy - Connectivity - linkerd - Kong, ingress
94. Gitops + Flux - 1 MC manage Configuration Git Repo For MC configuration watch manage https://docs.giantswarm.io/advanced/gitops/
95. Gitops + Flux - 2 MC WC App Catalog manage App CR App’s workloads manage pull https://docs.giantswarm.io/advanced/gitops/ Git Repo watch manage App’s workloads
96. Gitops + Flux - 3: Fleets & Collections MC manage e.g. https://github.com/giantswarm/openstack-app-collection Collection Git Repo MC … Fleet
97. Management Tools - Powerful internal admin tools - Lists management clusters - Get kubeconfig for MC/WC - Get access to MC/WC - Daily ops activities (deploy, rollout, drain etc.) - Open MC apps like prometheus, grafana etc. - We have powerful user tools like kubectl-gs - Easy templating - WC management, especially GS types (e.g. apps) - Web UI (giantswarm/happa)
98. User Experience Open source tools in upstream repositories are good but not enough for a smooth user experience. We - implement additional/helper operators - for easy upgrades with declarative approach like GitOps - for backup - for cleanup - create useful helm charts (See `cluster-$provider` repos in giantswarm org)
99. The problem domain is huge and complex. Ops is inevitable. Support is must.
100. for listening!