This is an automated email from the ASF dual-hosted git repository.
kvn 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 19ce6c6 doc: how to remove apisix admin key (#104)
19ce6c6 is described below
commit 19ce6c69d8b4a2d1b859caa469eba12bcd6f756c
Author: Alex Zhang <[email protected]>
AuthorDate: Thu Dec 17 13:36:42 2020 +0800
doc: how to remove apisix admin key (#104)
* doc: how to remove apisix admin key
* fix: markdown lint check
* fix: faq question title
---
docs/FAQ.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 49fb08a..4ea19b7 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -32,3 +32,9 @@ This is a cascading update problem, see for details
[apisix-ingress-controller D
No, currently we are implementing one-way synchronization, that is, CRDs file
-> Apache AIPSIX. If the configuration is modified separately through admin
api, it will not be synchronized to CRDs in Kubernetes.
This is because CRDs are generally declared in the file system, and Apply to
enter Kubernetes etcd, we follow the definition of CRDs and synchronize to
Apache Apisix Data Plane, but the reverse will make the situation more
complicated.
+
+4. Why there are some error logs like "list upstreams failed, err: http get
failed, url: blahblahblah, err: status: 401"?
+
+So far apisix-ingress-controller doesn't support set admin_key for Apache
APISIX, so when you deploy your APISIX cluster, admin_key should be removed
from config.
+
+Note since APISIX have two configuration files, the first is config.yaml,
which contains the user specified configs, the other is config-default.yaml,
which has all default items, config items in these two files will be merged. So
admin_key in both files should be removed. You can customize these two
configuration files and mount them to APISIX deloyment.
