-
Notifications
You must be signed in to change notification settings - Fork 135
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
Updating the monitoring namespace in the DSCI CR leaves resources running #455
Comments
Note: This is same for applicationsNamespace as well. An expected solution here is to ensure, application pods are cleaned up from the old namespace. We should not be deleting the previous namespace. |
so the scope for this ticket is: |
Correct, delete the components that were enabled. |
why add rhods-2.4 to this ticket? @dchourasia |
i think part of this issue has been done in #637 for application namespace. |
@zdtsw Can you confirm this should not be tracked as "Ready for QA" in 2.4? |
i dont think the scope of this issue is completely covered , also the "application" part did not included in downstream 2.4. so the "rhods-2.4" label should be removed. |
did a test based on the current logic which already have "cleanup missing resourced in DSC" part. in our component logic, it is purely if enabled. |
2 cents from me: do we really need to support this configable namespace? |
moved this issue to JIRA ref: https://issues.redhat.com/browse/RHOAIENG-403 |
closing this as it is migrated to the JIRA |
Describe the bug
Updating the monitoring namespace in the DSCI CR will trigger the creation of new monitoring pods in the new namespace, but the old namespace will not be delete and the pods will be left running there
To Reproduce
Steps to reproduce the behavior:
Expected behavior
old pods are stopped, resources are removed, optionally namespace is deleted (not sure, might point to a namespace the user wants to keep)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: