chore: rename apisix-ingress-controller

Signed-off-by: ashing <[email protected]>

Author: ronething

.github/workflows/release-drafter.yml

@@ -27,7 +27,7 @@ on:
       - '.github/**'
 jobs:
   update_release_draft:
-    if: github.repository == 'api7/api7-ingress-controller'
+    if: github.repository == 'apache/apisix-ingress-controller'
     runs-on: buildjet-2vcpu-ubuntu-2204
     steps:
       - name: Drafting release

.gitignore

@@ -34,5 +34,3 @@ apisix-ingress-controller-conformance-report.yaml
 *.mdx
 .cursor/
 .env
-
-charts/api7ee3

Makefile

@@ -5,7 +5,7 @@ VERSION ?= 2.0.0
 
 IMAGE_TAG ?= dev
 
-IMG ?= api7/api7-ingress-controller:$(IMAGE_TAG)
+IMG ?= apache/apisix-ingress-controller:$(IMAGE_TAG)
 # ENVTEST_K8S_VERSION refers to the version of kubebuilder assets to be downloaded by envtest binary.
 ENVTEST_K8S_VERSION = 1.30.0
 

README.md

@@ -2,7 +2,7 @@
 
 ## Description
 
-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.
+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.
 
 ## Document
 
@@ -41,7 +41,7 @@ make install
 **Deploy the Manager to the cluster with the image specified by `IMG`:**
 
 ```sh
-make deploy #IMG=api7/api7-ingress-controller:dev
+make deploy #IMG=apache/apisix-ingress-controller:dev
 ```
 
 > **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
 1. Build the installer for the image built and published in the registry:
 
 ```sh
-make build-installer # IMG=api7/api7-ingress-controller:dev
+make build-installer # IMG=apache/apisix-ingress-controller:dev
 ```
 
 NOTE: The makefile target mentioned above generates an 'install.yaml'

charts/values.yaml

@@ -33,7 +33,7 @@ deployment:
         - ALL
   topologySpreadConstraints: []
   image:
-    repository: api7/api7-ingress-controller
+    repository: apache/apisix-ingress-controller
     pullPolicy: IfNotPresent
     tag: "dev"
 

config/manager/kustomization.yaml

@@ -4,5 +4,5 @@ apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 images:
 - name: controller
-  newName: api7/api7-ingress-controller
+  newName: apache/apisix-ingress-controller
   newTag: dev

docs/concepts.md

@@ -1,6 +1,6 @@
 # Concepts
 
-The APISIX Ingress Controller is used to manage the APISIX Gateway as either a standalone application or a Kubernetes-based application. It dynamically configures and manages the API7 Gateway using Gateway API resources.
+The APISIX Ingress Controller is used to manage the APISIX Gateway as either a standalone application or a Kubernetes-based application. It dynamically configures and manages the APISIX Gateway using Gateway API resources.
 
 ## Architecture
 

docs/gateway-api.md

@@ -29,7 +29,7 @@ For more information about Gateway API, please refer to [Gateway API](https://ga
 
 ## HTTPRoute
 
-The HTTPRoute resource allows users to configure HTTP routing by matching HTTP traffic and forwarding it to Kubernetes backends. Currently, the only backend supported by API7 Gateway is the Service resource.
+The HTTPRoute resource allows users to configure HTTP routing by matching HTTP traffic and forwarding it to Kubernetes backends. Currently, the only backend supported by APISIX Gateway is the Service resource.
 
 ### Example