This message was deleted.
# amazona
adamant-kite-43734
01/25/2023, 4:35 PMThis message was deleted.
b
bland-area-30120
01/25/2023, 4:35 PMthe issue was resolved by removing the cluster from rancher and adding it again. we still don't know why this happened
c
careful-piano-35019
01/26/2023, 9:33 AMdid you import initially the cluster in an earlier version of Rancher ?
b
bland-area-30120
01/26/2023, 9:36 AMyes, we've updated rancher quite a few times after we imported the cluster initially
bland-area-30120
01/26/2023, 9:38 AMthere are also a few other clusters we've done the same procedure with in the last 2 weeks without issues. at least one of them is older then the cluster that had the problem yesterday
c
careful-piano-35019
01/26/2023, 10:25 AMok, I was thinking out loud. Hard to say without a way to reproduce.
b
bland-area-30120
01/26/2023, 10:27 AMunderstood. Any thoughts on removing permissions I don't want rancher to have?
c
careful-piano-35019
01/26/2023, 10:29 AMyes that includes permissions to enable full cluster management and provisionning
careful-piano-35019
01/26/2023, 10:30 AMit may work with less, but mostly tests are with those profiles
b
bland-area-30120
01/26/2023, 10:30 AMok, I'll try to test this myself. Mostly thinking about removing delete permissions
6 Views