Repository files navigation

The APISIX Ingress Controller allows you to run the APISIX Gateway as aKubernetes Ingress to handle inbound traffic for a Kubernetes cluster. Itdynamically configures and manages the APISIX Gateway using Gateway APIresources.

• Getting Started
• Concepts
• Configuration

• go version v1.22.0+
• docker version 17.03+.
• kubectl version v1.11.3+.
• Access to a Kubernetes v1.11.3+ cluster.

Build and push your image to the location specified byIMG:

make build-image

NOTE: This image ought to be published in the personal registry youspecified. And it is required to have access to pull the image from theworking environment. Make sure you have the proper permission to the registryif the above commands don't work.

Install the CRDs & Gateway API into the cluster:

make install

Deploy the Manager to the cluster with the image specified byIMG:

make deploy#IMG=apache/apisix-ingress-controller:dev

NOTE: If you encounter RBAC errors, you may need to grant yourselfcluster-admin privileges or be logged in as admin.

Delete the APIs(CRDs) from the cluster:

make uninstall

UnDeploy the controller from the cluster:

make undeploy

Following are the steps to build the installer and distribute this project tousers.

1. Build the installer for the image built and published in the registry:

make build-installer# IMG=apache/apisix-ingress-controller:dev

NOTE: The makefile target mentioned above generates an 'install.yaml'file in the dist directory. This file contains all the resources builtwith Kustomize, which are necessary to install this project withoutits dependencies.

1. Using the installer

Users can just run kubectl apply -f with the YAML bundle to install theproject, i.e.:

kubectl apply -f dist/install.yaml