[GitHub] [apisix-ingress-controller] gxthrj commented on issue #50: Discuss: how to configure `admin_key` for multi-APISIX cluster.

[GitBox <gi...@apache.org>]

gxthrj commented on issue #50:
URL: https://github.com/apache/apisix-ingress-controller/issues/50#issuecomment-739747507


   For now, `apisix-ingress-controller` do not support the config `admin_key` from Apache APISIX.
   When using  `apisix-ingress-controller` with APISIX, it is recommended to remove the `admin_key` setting. You can use `allow_admin` to restrict the access scope of the `APISIX control plane` to ensure security.
   
   Now we can discuss how to support the `admin_key` in `apisix-ingress-controller`.
    In different APISIX clusters, there are different admin_keys. Usually we manage admin_key through secret resource. But it is not easy to sync with CRDs in `apisix-ingress-controller`, for `secret` may in the different namespace.
   
   We can use `ingress.class` to specify APISIX cluster, and also can define an annotation for `admin_key`, such as `ingress.admin_key`, But it will need to be updated manually in the future, if `admin_key` need to be changed.
   
   So anyone has a good idea, can discuss it here. Thanks.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org