Skip to content

Commit b6339ff

Browse files
authored
Merge pull request #12 from aroraharsh23/Readme_changes
Readme changes
2 parents 60cf24b + 8c51c20 commit b6339ff

File tree

2 files changed

+2
-28
lines changed

2 files changed

+2
-28
lines changed

README.md

Lines changed: 1 addition & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -65,33 +65,7 @@ Citrix k8s node controller monitors the node events and establishes a route betw
6565

6666
## Get started
6767

68-
You can run Citrix k8s node controller as:
69-
70-
- A **microservice** inside the Kubernetes cluser.
71-
- A **process** outside the Kubernetes cluster.
72-
73-
>**Important:**
74-
>
75-
>Citrix recommends that you use Citrix k8s node controller as a **microservice** for production environments. And, as a **process** for easy development.
76-
77-
### Using Citrix k8s node controller as a process
78-
79-
Before you deploy the citrix-k8s-node-controller` package, ensure that you have installed Go binary for running MIC.
80-
81-
Perform the following:
82-
83-
1. Download or clone the `citrix-k8s-node-controller` package.
84-
85-
1. Navigate to the build directory and start the `citrix-k8s-node-controller` using the following command:
86-
87-
make run
88-
89-
1. Deploy the config map using the following command:
90-
91-
kubectl apply -f https://raw.githubusercontent.com/janraj/citrix-k8s-node-controller/master/deploy/config_map.yaml
92-
93-
### Using Citrix k8s node controller as a microservice
94-
68+
You can run Citrix k8s node controller as a **microservice** inside the Kubernetes cluser.
9569
Refer the [deployment](deploy/README.md) page for running Citrix k8s node controller as a microservice inside the Kubernetes cluster.
9670

9771
## Questions

deploy/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ The highlights in the screenshot show the VXLAN VNID, VXLAN PORT, SNIP, route, a
5656
5757
1. Delete the [config map](config_map.yaml) using the following command:
5858
59-
When we delete the configmap, Citrix node controller cleans up the configuration created on Citrix ADC.
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.
6060
6161
kubectl delete -f https://raw.githubusercontent.com/citrix/citrix-k8s-node-controller/git_cnc_v2/deploy/config_map.yaml
6262

0 commit comments

Comments
 (0)