-
Notifications
You must be signed in to change notification settings - Fork 25
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
Autoruler deployment is not created in control plane cluster #149
Comments
I've tried to create the below artifacts manually,
This time it got approved automatically. But we think these artifacts should be automatically created. Could you please let us know what we are missing in order to have these artifacts automatically in control plane cluster? |
They should be created automatically, because they are part of the day 2 configuration. Can you share the repository and configuration that you are using to configure your clusters? Thanks. |
Hi @yrobla We found that there is issue in rhacm manifests generated, after fixing it the node-labeller pods are running.
However we are facing issue with csr auto approval randomly with below errors, could you please help
Also please find the attached file with full logs. |
Is this problem still happening? After getting some feedback, it seems that this problem is a temporary one but should disappear after autoapprover retries. |
@yrobla Yeah, this happens randomly. |
A fix has been pushed to the autolabeler image. Please can you redeploy, ensuring that you have the latest images, and see if the problem is fixed? Thanks. |
Steps followed:
leo
We observed that csr is not getting auto approved
While debugging we found that the pods are not created
Which we think are responsible for auto approving csr.
Could you please help here?
The text was updated successfully, but these errors were encountered: