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
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Description
4
4
5
-
The APISIX Ingress Controller allows you to run the APISIX Gateway as a Kubernetes Ingress to handle inbound traffic for a Kubernetes cluster. It dynamically configures and manages the API7 Gateway using Gateway API resources.
5
+
The APISIX Ingress Controller allows you to run the APISIX Gateway as a Kubernetes Ingress to handle inbound traffic for a Kubernetes cluster. It dynamically configures and manages the APISIX Gateway using Gateway API resources.
6
6
7
7
## Document
8
8
@@ -41,7 +41,7 @@ make install
41
41
**Deploy the Manager to the cluster with the image specified by `IMG`:**
42
42
43
43
```sh
44
-
make deploy #IMG=api7/api7-ingress-controller:dev
44
+
make deploy #IMG=apache/apisix-ingress-controller:dev
45
45
```
46
46
47
47
> **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin
@@ -66,7 +66,7 @@ Following are the steps to build the installer and distribute this project to us
66
66
1. Build the installer for the image built and published in the registry:
67
67
68
68
```sh
69
-
make build-installer # IMG=api7/api7-ingress-controller:dev
69
+
make build-installer # IMG=apache/apisix-ingress-controller:dev
70
70
```
71
71
72
72
NOTE: The makefile target mentioned above generates an 'install.yaml'
0 commit comments