You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1). The plugin config id generation should not rely on the name of backend service name, which will cause all routes with the same backend generated with the same plugin config id.
2). add the plugin_config id reference even if users don't specify the plugin config on the ApisixRoute explicitly
Environment
your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
your Kubernetes cluster version (output of kubectl version):
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
Minimal test code / Steps to reproduce
Nope.
Actual result
Nope.
Error log
Nope.
Expected result
No response
The text was updated successfully, but these errors were encountered:
Issue description
apisix-ingress-controller/pkg/kube/translation/apisix_route.go
Lines 534 to 539 in de52243
The code snippet pasted above has two problems:
1). The plugin config id generation should not rely on the name of backend service name, which will cause all routes with the same backend generated with the same plugin config id.
2). add the plugin_config id reference even if users don't specify the plugin config on the
ApisixRoute
explicitlyEnvironment
Minimal test code / Steps to reproduce
Nope.
Actual result
Nope.
Error log
Nope.
Expected result
No response
The text was updated successfully, but these errors were encountered: