This message was deleted.
# generala
adamant-kite-43734
02/05/2025, 9:23 AMThis message was deleted.
s
stocky-account-63046
02/05/2025, 9:26 AMfollowing on from https://rancher-users.slack.com/archives/C3ASABBD1/p1738589512375899, you might need to research removing v1 monitoring.
current v2 monitoring is handled differently
r
rich-thailand-55018
02/05/2025, 9:27 AMthanks I have already upgraded to v2 on local cluster
rich-thailand-55018
02/05/2025, 9:27 AMI cannot delete monitoring on a target cluster
Copy code
helm uninstall --namespace=cattle-monitoring-system rancher-monitoring
Error: failed to delete release: rancher-monitoringrich-thailand-55018
02/05/2025, 9:27 AMmaybe I need to update the deprecated APIs first ?
s
stocky-account-63046
02/05/2025, 9:28 AMv2 wouldn't use any deprecated apis. maybe a relic of v1?
stocky-account-63046
02/05/2025, 9:29 AMr
rich-thailand-55018
02/05/2025, 9:30 AMI had to resort to https://www.suse.com/support/kb/doc/?id=000021053
"*I forgot to check my workloads for lingering PodSecurityPolicies"*
rich-thailand-55018
02/05/2025, 9:30 AMthen I was able to remove it on local cluster
rich-thailand-55018
02/05/2025, 9:30 AMbut it's still lingering on a monitored cluster...
s
stocky-account-63046
02/05/2025, 9:42 AMah, the dreaded PSPs. that's not something i know much about unfortunately.
is there anymore detail helm can provide? could be an issue with monitoring resource finalizers?
r
rich-thailand-55018
02/05/2025, 9:55 AMnothing shows up with
helm uninstall rancher-monitoring -debugrich-thailand-55018
02/05/2025, 10:01 AMI think I removed it finally by removing the daemonsets and deployments manually phew
rich-thailand-55018
02/05/2025, 10:01 AMwhat a struggle haha even after using mapkubeapis
17 Views