change NKL to NLK

Author: chrisakker

deployments/deployment/configmap.yaml

@@ -4,5 +4,5 @@ data:
   nginx-hosts:
     "http://10.1.1.4:9000/api,http://10.1.1.5:9000/api"
 metadata:
-  name: nkl-config
-  namespace: nkl
+  name: nlk-config
+  namespace: nlk

deployments/deployment/deployment.yaml

@@ -1,19 +1,19 @@
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: nkl-deployment
-  namespace: nkl
+  name: nlk-deployment
+  namespace: nlk
   labels:
-    app: nkl
+    app: nlk
 spec:
   replicas: 1
   selector:
     matchLabels:
-      app: nkl
+      app: nlk
   template:
     metadata:
       labels:
-        app: nkl
+        app: nlk
     spec:
       containers:
         - name: nginx-k8s-loadbalancer

deployments/deployment/namespace.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 kind: Namespace
 metadata:
-  name: nkl
+  name: nlk
   labels:
-    name: nkl
+    name: nlk

deployments/rbac/clusterrole.yaml

@@ -2,7 +2,7 @@ apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
   name: ingress-resource-get-watch-list
-  namespace: nkl
+  namespace: nlk
 rules:
   - apiGroups:
         - ""

deployments/rbac/clusterrolebinding.yaml

@@ -2,11 +2,11 @@ apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: "nginx-k8s-loadbalancer:ingress-resource-get-watch-list"
-  namespace: nkl
+  namespace: nlk
 subjects:
   - kind: ServiceAccount
     name: nginx-k8s-loadbalancer
-    namespace: nkl
+    namespace: nlk
 roleRef:
   kind: ClusterRole
   name: ingress-resource-get-watch-list

deployments/rbac/secret.yaml

@@ -2,7 +2,7 @@ apiVersion: v1
 kind: Secret
 metadata:
   name: nginx-k8s-loadbalancer-secret
-  namespace: nkl
+  namespace: nlk
   annotations:
     kubernetes.io/service-account.name: nginx-k8s-loadbalancer
 type: kubernetes.io/service-account-token

deployments/rbac/serviceaccount.yaml

@@ -2,4 +2,4 @@ apiVersion: v1
 kind: ServiceAccount
 metadata:
   name: nginx-k8s-loadbalancer
-  namespace: nkl
+  namespace: nlk

docs/DESIGN.md

@@ -13,10 +13,10 @@ Lastly, the Synchronizer calls the [NGINX+ Configuration API](https://docs.nginx
 stateDiagram-v2
     Controller --> Watcher
     Controller --> Settings 
-    Watcher --> Handler : "nkl-handler queue"
+    Watcher --> Handler : "nlk-handler queue"
     Handler --> Translator
     Translator --> Handler
-    Handler --> Synchronizer : "nkl-synchronizer queue"
+    Handler --> Synchronizer : "nlk-synchronizer queue"
     Synchronizer --> BorderClient : "HttpBorderClient | TcpBorderClient"
     BorderClient --> NGINXPlusLB1
     BorderClient --> NGINXPlusLB2
@@ -26,33 +26,33 @@ stateDiagram-v2
 
 ### Settings
 
-The Settings module is responsible for loading the configuration settings from the "nkl-config" ConfigMap resource in the "nkl" namespace.
-The Settings are loaded when the controller starts and are reloaded when the "nkl-config" ConfigMap resource is updated.
+The Settings module is responsible for loading the configuration settings from the "nlk-config" ConfigMap resource in the "nlk" namespace.
+The Settings are loaded when the controller starts and are reloaded when the "nlk-config" ConfigMap resource is updated.
 
 ### Watcher
 
 The Watcher is responsible for monitoring changes to Service resources in the "nginx-ingress" namespace.
-It registers methods that handle each event type. Events are handled by creating a `core.Event` instance and adding it to the "nkl-handler" queue. 
+It registers methods that handle each event type. Events are handled by creating a `core.Event` instance and adding it to the "nlk-handler" queue. 
 When adding the event to the queue, the Watcher also retrieves the list of Node IPs and adds the list to the event. 
 The master node ip is excluded from the list. (NOTE: This should be configurable.)
 
 ### Handler
 
-The Handler is responsible for taking the `core.Event` instances from the "nkl-handler" queue and calling the Translator to convert the event into a `core.ServerUpdateEvent` instance, 
-adding each `core.ServerUpdateEvent` to the "nkl-synchronizer" queue.
+The Handler is responsible for taking the `core.Event` instances from the "nlk-handler" queue and calling the Translator to convert the event into a `core.ServerUpdateEvent` instance, 
+adding each `core.ServerUpdateEvent` to the "nlk-synchronizer" queue.
 
 ### Translator
 
 The Translator is responsible for converting the `core.Event` event into an `nginxClient.UpstreamServer` event.
-This involves filtering out the `core.Event` instances that are not of interest to the controller by accepting only Port names starting with the NklPrefix value (currently _nkl-_).
+This involves filtering out the `core.Event` instances that are not of interest to the controller by accepting only Port names starting with the NklPrefix value (currently _nlk-_).
 The event is then fanned-out based on the defined Ports, one event per defined Port. Each port is then augmented with the Ingress name (the name configured in the Port definition with the NklPrefix value removed), 
 and the list of the Node's IP addresses.
 
 The Translator passes the list of events to the Synchronizer by calling the `AddEvents` method. 
 
 **NOTE: It is important that the Port names match the name of the defined NGINX Plus Upstreams.**
 
-In the following example the NGINX Plus Upstreams are named "nkl-nginx-lb-http" and "nkl-nginx-lb-https". These match the name in the NGINX Plus configuration.
+In the following example the NGINX Plus Upstreams are named "nlk-nginx-lb-http" and "nlk-nginx-lb-https". These match the name in the NGINX Plus configuration.
 
 ```yaml
 apiVersion: v1
@@ -66,19 +66,19 @@ spec:
   - port: 80
     targetPort: 80
     protocol: TCP
-    name: nkl-nginx-lb-http
+    name: nlk-nginx-lb-http
   - port: 443
     targetPort: 443
     protocol: TCP
-    name: nkl-nginx-lb-https
+    name: nlk-nginx-lb-https
   selector:
     app: nginx-ingress
 ```
 
 ### Synchronizer
 
 The Synchronizer is responsible for fanning-out the given list of `core.ServerUpdateEvent` events, one for each configured NGINX Plus host.
-The NGINX Plus hosts are configured using a ConfigMap resource named "nkl-config" in the "nkl" namespace. An example of the ConfigMap is shown below.
+The NGINX Plus hosts are configured using a ConfigMap resource named "nlk-config" in the "nlk" namespace. An example of the ConfigMap is shown below.
 
 ```yaml
 apiVersion: v1
@@ -87,13 +87,13 @@ data:
   nginx-hosts:
     "http://10.1.1.4:9000/api,http://10.1.1.5:9000/api"
 metadata:
-  name: nkl-config
-  namespace: nkl
+  name: nlk-config
+  namespace: nlk
 ```
 
 This example includes two NGINX Plus hosts to support High Availability.
 
-Additionally, the Synchronizer is responsible for taking the `core.ServerUpdateEvent` instances from the "nkl-synchronizer" queue and updating the target NGINX Plus host. 
+Additionally, the Synchronizer is responsible for taking the `core.ServerUpdateEvent` instances from the "nlk-synchronizer" queue and updating the target NGINX Plus host. 
 The Synchronizer uses the [NGINX Plus Go client](https://github.com/nginxinc/nginx-plus-go-client) to communicate with each NGINX Plus host.
 
 
@@ -106,7 +106,7 @@ having defaults set to a base of 2 seconds, and a maximum of 60 seconds.
 ### Jitter
 
 The Synchronizer uses a jitter mechanism to avoid thrashing the NGINX Plus hosts. Each `core.ServerUpdateEvent` instance 
-is added to the "nkl-synchronizer" queue with a random jitter value between 250 and 750 milliseconds.
+is added to the "nlk-synchronizer" queue with a random jitter value between 250 and 750 milliseconds.
 
 ## Authors
 - Steve Wagner - Solutions Architect - Community and Alliances @ F5, Inc.

docs/cafe-demo/cafe-virtualserver.yaml

@@ -1,5 +1,5 @@
 #Example virtual server with routes for Cafe Demo
-#For NKL Solution, redirects required for LB Server health checks
+#For NLK Solution, redirects required for LB Server health checks
 #Chris Akker, Apr 2023
 #
 apiVersion: k8s.nginx.org/v1

docs/http/clusters.conf

@@ -2,7 +2,7 @@
 # Chris Akker, Apr 2023
 # HTTP Proxy and load balancing
 # MultiCluster Load Balancing with http split clients 0-100%
-# Upstream servers managed by NKL Controller
+# Upstream servers managed by NLK Controller
 # Nginx Key Value store for Split ratios
 #
 #### clusters.conf
@@ -61,7 +61,7 @@ upstream cluster1-https {
    zone cluster1-https 256k;
    least_time last_byte;
    keepalive 16;
-   #servers managed by NKL Controller
+   #servers managed by NLK Controller
    state /var/lib/nginx/state/cluster1-https.state; 
 }
 
@@ -70,7 +70,7 @@ upstream cluster1-https {
 upstream cluster2-https {
    zone cluster2-https 256k;
    least_time last_byte;
-   #servers managed by NKL Controller
+   #servers managed by NLK Controller
    state /var/lib/nginx/state/cluster2-https.state; 
 }