Skip to content

Commit b5e7554

Browse files
committed
- Update image to GHCR
- Rename deployment manifests
1 parent 68e0e05 commit b5e7554

File tree

6 files changed

+10
-10
lines changed

6 files changed

+10
-10
lines changed

README.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ The Services and ConfigMap are restricted to a specific namespace (default: "nkl
7373

7474
#### Configuration
7575

76-
NKL is configured via a ConfigMap, the default settings are found in `deployment/nkl-configmap.yaml`. Presently there is a single configuration value exposed in the ConfigMap, `nginx-hosts`.
76+
NKL is configured via a ConfigMap, the default settings are found in `deployment/configmap.yaml`. Presently there is a single configuration value exposed in the ConfigMap, `nginx-hosts`.
7777
This contains a comma-separated list of NGINX Plus hosts that NKL will maintain.
7878

7979
You will need to update this ConfigMap to reflect the NGINX Plus hosts you wish to manage.
@@ -99,23 +99,23 @@ There is a much more detailed [Installation Reference](docs/README.md) available
9999

100100
2. Apply the Namespace
101101

102-
```kubectl apply -f deployments/nkl-namespace.yaml```
102+
```kubectl apply -f deployments/namespace.yaml```
103103

104104
3. Apply the RBAC resources
105105

106106
```./deployments/rbac/apply.sh```
107107

108108
4. Update / Apply the ConfigMap (For best results update the `nginx-hosts` values first)
109109

110-
```kubectl apply -f deployments/nkl-configmap.yaml```
110+
```kubectl apply -f deployments/configmap.yaml```
111111

112112
5. Apply the Deployment
113113

114-
```kubectl apply -f deployments/nkl-deployment.yaml```
114+
```kubectl apply -f deployments/deployment.yaml```
115115

116116
6. Check the logs
117117

118-
```kubectl -n nkl get pods | grep nkl-deployment | cut -f1 -d" " | xargs kubectl logs -n nkl --follow $1```
118+
```kubectl -n nkl get pods | grep deployment | cut -f1 -d" " | xargs kubectl logs -n nkl --follow $1```
119119

120120
At this point NKL should be up and running. Now would be a great time to go over to the [Installation Reference](docs/README.md)
121121
and follow the instructions to deploy a demo application.

deployments/deployment/nkl-deployment.yaml renamed to deployments/deployment/deployment.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ spec:
1717
spec:
1818
containers:
1919
- name: nginx-k8s-loadbalancer
20-
image: ciroque/nginx-k8s-loadbalancer:latest
20+
image: ghcr.io/nginxinc/nginx-k8s-loadbalancer:latest
2121
imagePullPolicy: Always
2222
ports:
2323
- name: http

docs/http/http-installation-guide.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -581,13 +581,13 @@ After a new installation of NGINX Plus, make the following configuration changes
581581
1. Apply the updated ConfigMap:
582582

583583
```bash
584-
kubectl apply -f nkl-configmap.yaml
584+
kubectl apply -f configmap.yaml
585585
```
586586

587587
1. Deploy the NKL Controller:
588588

589589
```bash
590-
kubectl apply -f nkl-deployment.yaml
590+
kubectl apply -f deployment.yaml
591591
```
592592

593593
1. Check to see if the NKL Controller is running, with the updated ConfigMap:

docs/tcp/tcp-installation-guide.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -386,13 +386,13 @@ After the new installation of NGINX Plus, make the following configuration chang
386386
1. Apply the updated ConfigMap:
387387
388388
```bash
389-
kubectl apply -f nkl-configmap.yaml
389+
kubectl apply -f configmap.yaml
390390
```
391391
392392
1. Deploy the NKL Controller:
393393
394394
```bash
395-
kubectl apply -f nkl-deployment.yaml
395+
kubectl apply -f deployment.yaml
396396
```
397397
398398
1. Check to see if the NKL Controller is running, with the updated ConfigMap:

0 commit comments

Comments
 (0)