This message was deleted.
# developer
a
This message was deleted.
b
I don't really think there is a way to import an external cluster via the provider. But if it's RKE and being attached to rancher anyways why not just provision it as a downstream cluster from Rancher via the rancher2 provider? Importing seems like a lot of extra work and you'd need to manage a lot of the cluster configuration external to rancher. Whereas RKE especially is designed to integrate with the rancher UI/API very nicely.
r
The main reason, here, was to avoid circular dependencies. This cluster manages an HA Harbor install. Rancher would then use it to bootstrap itself which obviously doesn't work. With multiple rancher servers, we needed something external that would service everyone without being dependent on a specific rancher server.
However, I figured I'd at least be able to mange the Harbor cluster using Rancher's UI which would be for convenience.