Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request help: Question - When I change the Upstream from Kubernetes environment to Admin API #2187

Open
kworkbee opened this issue Mar 19, 2024 · 0 comments

Comments

@kworkbee
Copy link

kworkbee commented Mar 19, 2024

Issue description

When an Upstream is changed by Admin API in Kubernetes environment, there is a phenomenon in which it is restored to its original state (Declared in ApisixUpstream spec) after a specific time.

I wonder if this is the intended action, and if so, please answer whether it is reasonable to change only the ApisixUpstream spec rather than changing the Upstream information through Admin API in Kubernetes environment.

Environment

  • your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 0.14.0
  • your Kubernetes cluster version (output of kubectl version): v1.25
  • if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): AWS EKS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant