Chever-John commented on code in PR #994: URL: https://github.com/apache/apisix-ingress-controller/pull/994#discussion_r866584818
########## docs/en/latest/practices/how-to-use-go-plugin-runner-in-apisix-ingress.md: ########## @@ -0,0 +1,375 @@ +# How to use go-plugin-runner in APISIX Ingress + +## Proposal Description + +Based on version 0.3 of the go-plugin-runner plugin and version 1.4.0 of APISIX Ingress, this article goes through building the cluster, building the image, customizing the helm chart package, and finally, deploying the resources. It is guaranteed that the final result can be derived in full based on this documentation. + +```bash +go-plugin-runner: 0.3 +APISIX Ingress: 1.4.0 + +kind: kind v0.12.0 go1.17.8 linux/amd64 +kubectl version: Client Version: v1.23.5/Server Version: v1.23.4 +golang: go1.18 linux/amd64 +``` + +## Begin + +### Build a cluster environment + +Select `kind` to build a local cluster environment. The command is as follows: + +```bash +cat <<EOF | kind create cluster --config=- +kind: Cluster +apiVersion: kind.x-k8s.io/v1alpha4 +nodes: +- role: control-plane + kubeadmConfigPatches: + - | + kind: InitConfiguration + nodeRegistration: + kubeletExtraArgs: + node-labels: "ingress-ready=true" + extraPortMappings: + - containerPort: 80 + hostPort: 80 + protocol: TCP + - containerPort: 443 + hostPort: 443 + protocol: TCP +EOF +``` + +### Build the go-plugin-runner executable + +If you have finished writing the plugin, you can start compiling the executable to run with APISIX. + +This article recommends two packaging build options. + +1. put the packaging process into the Dockerfile and finish the compilation process when you build the docker image later. Review Comment: Solved~ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
