nginx

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

Feature request

Feature description

The generated and installed config files permission are too open, any user logined on the system can read and write them. So i suggest append a chmod command into Extract tar step to keep config files more safty.

How the feature is useful

Docs should be available for all the configurations possible with a values file for the helm chart installation, of the ingress-nginx-controller.

• Here is the documentation example of a table of configurations, https://artifacthub.io/packages/helm/bitnami/mysql
• Here is a documentation example of a bulleted list of configurations, https://www.consul.io/

Please update documentation to add Known OIDC Redirect URI's for the following applications:

Wekan (version 5.41) ---> https://wekan.example.com/_oauth_oidc
Portainer CE (version 2.6.1) ---> https://portainer.example.com
Nextcloud (Requires Add-on: Here, Version 22.1.0) --> https://nextcloud.example.com/apps/oidc_login/oidc

Issue description

I hope that apisix could be configurated the listening address.
In some special cases, for example, I plan to use a combination of APISIX and Keepalived to achieve high availability.
I will turn on the relevant Linux kernel parameters (to enable the program to listen the IP that does not exist on the local host):

echo "net.ipv4.ip_nonlocal_bind=1" >> /etc/sysc

Under edit Proxy Host, it states to use 1.1.1.1/path for sub folder forwarding

1.1.1.1 should not be used like this, as its a valid external address and website

Since maxmind no longer provides the legacy GeoIP databases could it might be possible to update the nxtool to use GeoIP2?

Describe the feature

I was testing a blue/green strategie within my Kubernetes cluster using flagger and the kubernetes provider.

In the documentation, in the blue/green usage strategie steps, we can see that the traffic should be routed to canary while the primary is promoted https://docs.flagger.app/usage/deployment-strategies#blue-green-deployments

I was assuming that using