This message was deleted.
# cabpr
a
This message was deleted.
r
A couple of questions: 1. What version of Rancher are you using? 2. How are you registering the clusters (i.e. using "import" in Rancher)? 3. Have you disabled the embedded CAPI controllers in Rancher via the feature flag? (note: if you do this there are implications)
a
1. 2.7.3 2. Through REST api I'm calling the
/v3/cluster
endpoint as well as
/v3/clusters/<clusterid>/clusterregistrationtoken
endpoint 3. Yes I have disabled embedded CAPI with the feature-flag (as well as continuous-delivery feature flag)
r
There was an issue in webhooks in a similar situation but the error message was different: https://github.com/rancher/webhook/issues/158
a
Actually, I've found quite a few very similar issues, but they're all slightly different enough to think this is a different thing happening: https://github.com/rancher/rancher/issues/41826 https://github.com/rancher/rancher/issues/41883 ... to name a few
l
Any update to this? @abundant-camera-87627
Is there a cluster role that Rancher uses to deploy this? Is it possible for us to just revoke the permission to deploy?
a
This behaviour only seems to happen on an air gapped cluster. And no I haven't set up any specific cluster roles.
123 Views