(apisix-ingress-controller) branch v1.8.0 updated: fix: placement for customPlugins and plugins config (#2189)

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ashishtiwari pushed a commit to branch v1.8.0
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git


The following commit(s) were added to refs/heads/v1.8.0 by this push:
     new c8309af6 fix: placement for customPlugins and plugins config (#2189)
c8309af6 is described below

commit c8309af6624bc56167d898dff7b755d03f94717e
Author: Sanket Phansekar <sa...@users.noreply.github.com>
AuthorDate: Mon Apr 1 12:02:46 2024 +0530

    fix: placement for customPlugins and plugins config (#2189)
---
 docs/en/latest/tutorials/using-custom-plugins.md | 42 ++++++++++++++----------
 1 file changed, 24 insertions(+), 18 deletions(-)

diff --git a/docs/en/latest/tutorials/using-custom-plugins.md b/docs/en/latest/tutorials/using-custom-plugins.md
index 05f4e399..437f544e 100644
--- a/docs/en/latest/tutorials/using-custom-plugins.md
+++ b/docs/en/latest/tutorials/using-custom-plugins.md
@@ -108,31 +108,37 @@ First, we will update the `values.yaml` file to mount the custom Plugin we creat
 You can configure the Plugin under `customPlugins` as shown below:
 
 ```yaml {title="values.yaml"}
-customPlugins:
-  enabled: true
-  plugins:
-    - name: "custom-response"
-      attrs: {}
-      configMap:
-        name: "custom-response-config"
-        mounts:
-          - key: "custom-response.lua"
-            path: "/usr/local/apisix/apisix/plugins/custom-response.lua"
+apisix:
+  ...
+  ...
+  customPlugins:
+    enabled: true
+    plugins:
+      - name: "custom-response"
+        attrs: {}
+        configMap:
+          name: "custom-response-config"
+          mounts:
+            - key: "custom-response.lua"
+              path: "/usr/local/apisix/apisix/plugins/custom-response.lua"
 ```
 
 You should also enable the Plugin by adding it to the `plugins` list:
 
 ```yaml {title="values.yaml"}
-plugins:
-  - api-breaker
-  - authz-keycloak
-  - basic-auth
-  - batch-requests
-  - consumer-restriction
-  - cors
+apisix:
   ...
   ...
-  - custom-response
+  plugins:
+    - api-breaker
+    - authz-keycloak
+    - basic-auth
+    - batch-requests
+    - consumer-restriction
+    - cors
+    ...
+    ...
+    - custom-response
 ```
 
 Finally you can enable the Ingress controller and configure the gateway to be exposed to external traffic. For this, set `service.type=NodePort`, `ingress-controller.enabled=true`, and `ingress-controller.config.apisix.serviceNamespace=ingress-apisix` in your `values.yaml` file.