You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/plugins/cloudstack-kubernetes-service.rst
+50-21Lines changed: 50 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,9 @@
13
13
CloudStack Kubernetes Service
14
14
==============================
15
15
16
-
The Kubernetes Service plugin adds Kubernetes integration to CloudStack. The plugin is disabled by default and an admin can enable it using a Global Setting. It enables users to run containerized services using Kubernetes clusters.
16
+
The Kubernetes Service plugin adds Kubernetes integration to CloudStack. The plugin is disabled by default and an admin can enable it using a Global Setting. It enables users to run containerized services using Kubernetes clusters. Also the global setting "endpoint.url" needs to be set to the CloudStack management server ip example (http://management-server-ip:8080/client/api)
17
17
18
-
With CoreOS having reached EOL, from 4.16 on the Kubernetes Service Plugin will use
19
-
the existing SystemVM Template by default for deploying kubernetes clusters. For
18
+
The Kubernetes Service plugin will use the existing SystemVM Template by default for deploying Kubernetes clusters. For
20
19
installation of Kubernetes binaries on the cluster nodes, a binaries ISO is used for each
21
20
Kubernetes version to be made available via CloudStack. This allows faster, offline
22
21
installation of Kubernetes binaries and docker images along with support for adding
@@ -26,7 +25,9 @@ multiple versions of Kubernetes for upgrades and running different clusters.
26
25
From version 4.21.0, users can choose different templates and service offerings for different types of nodes (worker, control, etcd nodes) for deploying Kubernetes clusters. The templates must be previously registered selecting the 'For CKS' option.
27
26
See :ref:`flexible-kubernetes-clusters`.
28
27
29
-
For deployment and setup of Kubernetes on cluster nodes, the plugin uses the Kubernetes tool, 'kubeadm'. kubeadm is the command-line tool for easily provisioning a secure Kubernetes cluster on top of physical or cloud servers or Instances. Under the hood, control node(s) of the cluster starts a Kubernetes cluster using kubeadm init command with a custom token, and worker nodes join this Kubernetes cluster using kubeadm join command with the same token. More about kubeadm here: https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/. Weave Net CNI provider plugin is used for cluster networking. More about Weave Net provide plugin here: https://www.weave.works/docs/net/latest/kubernetes/kube-addon/.
28
+
For deployment and setup of Kubernetes on cluster nodes, the plugin uses the Kubernetes tool, 'kubeadm'. kubeadm is the command-line tool for easily provisioning a secure Kubernetes cluster on top of physical or cloud servers or Instances. Under the hood, control node(s) of the cluster starts a Kubernetes cluster using kubeadm init command with a custom token, and worker nodes join this Kubernetes cluster using kubeadm join command with the same token. More about kubeadm here: https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/.
29
+
30
+
Calico CNI provider plugin is used for cluster networking supported from ACS 4.21 onwards. More about Calico CNI plugin here: https://docs.projectcalico.org/getting-started/kubernetes/.
30
31
31
32
To access the Kubernetes dashboard securely, the plugin provides access to kubeconfig file data which uses the Kubernetes tool kubectl to run a local proxy and thereby access the dashboard. More about kubectl here: https://kubernetes.io/docs/reference/kubectl/overview/
32
33
@@ -72,26 +73,31 @@ Eg: To generate the latest kubernetes iso
72
73
73
74
.. parsed-literal::
74
75
75
-
1.27.2, kubernetes version, see https://github.com/kubernetes/kubernetes/releases
76
-
1.3.0, CNI version, see https://github.com/containernetworking/plugins/releases
77
-
1.27.0, cri-tools version, see https://github.com/kubernetes-sigs/cri-tools/releases
78
-
1.11, weave addon for kubernetes, see https://github.com/weaveworks/weave/tree/master/prog/weave-kube
76
+
1.33.1, kubernetes version, see https://github.com/kubernetes/kubernetes/releases
77
+
1.7.1, CNI version, see https://github.com/containernetworking/plugins/releases
78
+
1.33.0, cri-tools version, see https://github.com/kubernetes-sigs/cri-tools/releases
79
+
3.30.0, calico addon for kubernetes, see https://raw.githubusercontent.com/projectcalico/calico/v3.30.0/manifests/calico.yaml
79
80
2.7.0, kubernetes dashboard version, see https://github.com/kubernetes/dashboard/release
From ACS 4.21 onwards, it is possible to specify the version for etcd binaries in the create-kubernetes-binaries-iso.sh script as an optional parameter - ETCD_VERSION. When the ETCD_VERSION parameter is set, the specified etcd version binaries are downloaded and stored in the Kubernetes ISO.
@@ -100,7 +106,7 @@ Example for etcd version 3.5.1:
Kubernetes ISOs built with a specified etcd version are necessary for creating Kubernetes clusters with separate etcd nodes. See :ref:`flexible-kubernetes-clusters`.
@@ -131,15 +137,15 @@ addKubernetesSupportedVersion API can be used by an admin to add a new supported
The minimum Kubernetes version that can be added in the service is 1.11. At present, v1.17 and above might not work due to their incompatibility with weave-net plugin.
@@ -765,6 +771,29 @@ For verification of the applied CNI Configuration, the following commands can be
765
771
766
772
Events: <none>
767
773
774
+
There could be Calico routing edge case encountered in some environments. By default, Calico uses the 192.168.0.0/16 network for its pod IP pool when you install it with the standard manifests. To avoid potential routing conflicts with existing networks in your infrastructure, it's advisable to customize the Calico IP pool to use a different subnet that doesn't overlap with your current network setup.
775
+
776
+
kubectl get ippool.crd.projectcalico.org -o yaml
777
+
778
+
.. code-block:: bash
779
+
apiVersion: crd.projectcalico.org/v1
780
+
kind: IPPool
781
+
metadata:
782
+
name: default-ipv4-ippool
783
+
spec:
784
+
cidr: 192.168.0.0/16
785
+
ipipMode: Always
786
+
natOutgoing: true
787
+
disabled: false
788
+
789
+
You can edit the IP pool to change the CIDR to a different subnet that fits your network architecture better. For example, you might choose to use 10.0.0.0/16.
0 commit comments