You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by to...@apache.org on 2021/06/24 02:45:20 UTC

[apisix-ingress-controller] branch master updated: docs: clarify installation by Kustomize (#558)

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 2122d76  docs: clarify installation by Kustomize (#558)
2122d76 is described below

commit 2122d76fd28cc7bce54e8f52e2d4c9d04a1e852a
Author: Fang <37...@users.noreply.github.com>
AuthorDate: Thu Jun 24 10:45:10 2021 +0800

    docs: clarify installation by Kustomize (#558)
---
 install.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/install.md b/install.md
index b3ed337..52b35c7 100644
--- a/install.md
+++ b/install.md
@@ -40,6 +40,10 @@ kubectl kustomize "github.com/apache/apisix-ingress-controller/samples/deploy?re
 
 Parameters are hardcoded so if the default values are not good for you, just tweak them manually.
 
+To tweak parameters, first you need to modify config files in _samples/deploy_ directory. There are many ways to acheive this. For example, you may insert a `sed` command after `kubectl kustomize`, that is, `kubectl kustomize "github.com/apache/apisix-ingress-controller/samples/deploy?ref=master" | sed "s@to-be-modified@after-modified@g" | kubectl apply -f -`. Another way is to use a local copy of _samples/deploy_ directory or a copy from your repo.
+
+Then you need to know which parameter need to be tweaked. If APISIX access token or the address of APISIX Admin API is changed, you need to modify `apisix.admin_key` or `apisix.base_url` respectively in field `.data.config.yaml` in file _samples/deploy/configmap/apisix-ingress-cm.yaml_. Another example is to install apisix-ingress-controller with different version, in which case you need to configure `.spec.template.spec.containers.[image]` to a desired version in file _samples/deploy/de [...]
+
 ## Verify Installation
 
 There are a lot of use examples (See [samples](docs/en/latest/practices/index.md) for more details), try to follow the operations there to verify the installation.