You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
The Gateway needs to process a Gateway resource. Currently, that is
already supported by the 'state' package. However, that support is
limited. For example, the package doesn't allow processing multiple
listeners. More over, the approach used in the 'state' package is hard
to extend to support multiple listeners.
This prompts development of a better solution.
As a first deliverable, we want to support processing multiple HTTP
listeners assuming they all bind to port 80.
We also assume that the Gateway only supports a single Gateway resource
with known namespace and name.
Solution - replace the existing types of the state package with
the new ones:
- Introduce Configuration, which is an internal representation of the
Gateway configuration.
- Introduce Statuses, which holds status-related information about
processed resources.
- Introduce ChangeProcessor, which processes changes to Gateway API
resources and returns new Configuration and Statuses.
Copy file name to clipboardExpand all lines: README.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,6 @@ Before you can build and run the NGINX Kubernetes Gateway, make sure you have th
34
34
35
35
Set the `PREFIX` variable to the name of the registry you'd like to push the image to. By default, the image will be named `nginx-kubernetes-gateway:0.0.1`.
36
36
37
-
38
37
1. Push the image to your container registry:
39
38
40
39
```
@@ -55,7 +54,6 @@ You can deploy NGINX Kubernetes Gateway on an existing Kubernetes 1.16+ cluster.
55
54
56
55
Make sure to substitute the image name with the name of the image you built.
57
56
58
-
59
57
1. Install the Gateway CRDs:
60
58
61
59
```
@@ -89,6 +87,11 @@ You can deploy NGINX Kubernetes Gateway on an existing Kubernetes 1.16+ cluster.
0 commit comments