Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy from ghcr #61

Merged
merged 1 commit into from
May 10, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ The Services and ConfigMap are restricted to a specific namespace (default: "nkl

#### Configuration

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`.
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`.
This contains a comma-separated list of NGINX Plus hosts that NKL will maintain.

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

2. Apply the Namespace

```kubectl apply -f deployments/nkl-namespace.yaml```
```kubectl apply -f deployments/namespace.yaml```

3. Apply the RBAC resources

```./deployments/rbac/apply.sh```

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

```kubectl apply -f deployments/nkl-configmap.yaml```
```kubectl apply -f deployments/configmap.yaml```

5. Apply the Deployment

```kubectl apply -f deployments/nkl-deployment.yaml```
```kubectl apply -f deployments/deployment.yaml```

6. Check the logs

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

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)
and follow the instructions to deploy a demo application.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ spec:
spec:
containers:
- name: nginx-k8s-loadbalancer
image: ciroque/nginx-k8s-loadbalancer:latest
image: ghcr.io/nginxinc/nginx-k8s-loadbalancer:latest
imagePullPolicy: Always
ports:
- name: http
Expand Down
4 changes: 2 additions & 2 deletions docs/http/http-installation-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -581,13 +581,13 @@ After a new installation of NGINX Plus, make the following configuration changes
1. Apply the updated ConfigMap:

```bash
kubectl apply -f nkl-configmap.yaml
kubectl apply -f configmap.yaml
```

1. Deploy the NKL Controller:

```bash
kubectl apply -f nkl-deployment.yaml
kubectl apply -f deployment.yaml
```

1. Check to see if the NKL Controller is running, with the updated ConfigMap:
Expand Down
4 changes: 2 additions & 2 deletions docs/tcp/tcp-installation-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -386,13 +386,13 @@ After the new installation of NGINX Plus, make the following configuration chang
1. Apply the updated ConfigMap:

```bash
kubectl apply -f nkl-configmap.yaml
kubectl apply -f configmap.yaml
```

1. Deploy the NKL Controller:

```bash
kubectl apply -f nkl-deployment.yaml
kubectl apply -f deployment.yaml
```

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