|
2 | 2 |
|
3 | 3 | This topic provides information on how to deploy Citrix node controller on Kubernetes and establish the route between Citrix ADC and Kubernetes Nodes. |
4 | 4 |
|
| 5 | +**NOTE:** As part of configuration, some resources will be created in the "kube-system" namespace. Hence, Please make sure that "kube-system" namespace is configurable. |
| 6 | + |
5 | 7 | Perform the following: |
6 | 8 |
|
7 | 9 | 1. Download the `citrix-k8s-node-controller.yaml` deployment file using the following command: |
@@ -52,11 +54,22 @@ To verify, log on to the Citrix ADC and use the following commands to verify the |
52 | 54 |
|
53 | 55 | The highlights in the screenshot show the VXLAN VNID, VXLAN PORT, SNIP, route, and ARP configured by Citrix node controller on the Citrix ADC. |
54 | 56 |
|
| 57 | +## Verify cluster deployments |
| 58 | +
|
| 59 | +Apart from "citrix-node-controller" deployment, some other resources are also created. |
| 60 | +
|
| 61 | +- In "Kube-system" namespace: |
| 62 | + - For each worker node, a "kube-chorus-router" pod. |
| 63 | + - A configmap "kube-chorus-router". |
| 64 | + - A serviceaccount "kube-chorus-router" |
| 65 | +- A clusterrole "kube-chorus-router" |
| 66 | +- A clusterrolebinding "kube-chorus-router" |
| 67 | +
|
55 | 68 | # Delete the Citrix K8s node controller |
56 | 69 |
|
57 | 70 | 1. Delete the [config map](config_map.yaml) using the following command: |
58 | 71 |
|
59 | | - When we delete the configmap, Citrix node controller cleans up the configuration created on Citrix ADC, the router configmap and the 2 router pods created by citrix node controller. |
| 72 | + When we delete the configmap, Citrix node controller cleans up the configuration created on Citrix ADC, the "kube-chorus-router" configmap and the "kube-chorus-router" pods created by citrix node controller. |
60 | 73 |
|
61 | 74 | kubectl delete -f https://raw.githubusercontent.com/citrix/citrix-k8s-node-controller/git_cnc_v2/deploy/config_map.yaml |
62 | 75 |
|
|
0 commit comments