-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug]: When deleting or changing Api Key name NGINX Breaks/refuses update. #7384
Comments
Hi @benshalev849 thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
@benshalev849 could you please check what HTTP request OCP UI sends to delete the API key? What is the output of |
@benshalev849 we will verify the behaviour using |
@jjngx Okay, ty! |
|
@benshalev849 can you please provide us with above info |
Hey, i am sorry for the late response, been a busy few weeks... We are an on prem deployment in a closed envrionment, copying the command to github is not really possible, when running it though i have not seen anything that may suggest it is related or broken. Have you been able to replicate it locally with k8s? Especially the change of name of the api key which just removes the api key config. |
@benshalev849 we tried to repro this but unfortunately couldn't. Would you be able to give us an failing example and partial conf please, one from the api-key example in this repo should be okay as well. |
@benshalev849 I tried changing the keys in |
Version
3.7.0
What Kubernetes platforms are you running on?
Openshift
Steps to reproduce
Creating the following secret:
Then attaching it to a policy:
When deleting an api key using
oc apply
the object does not update, when deleting via OCP UI it deletes.In addition when changing the name of a client the configuration will break and remove the api key authentication from the config file.
Only way that i have managed to delete/change name of API Keys is to completely delete the secret and re-create it.
The text was updated successfully, but these errors were encountered: