This message was deleted.

I've heard Rancher folks seem to suggest that there is a lot about the Rancher API that's not necessarily considered stable/public and you can backsolve from the UI but it's not too guaranteed not to change. There has also been suggestions that with 2.6 they're moving to put everything so it can be accessed/done via the Kubernetes API, so that might be a more future-proofed direction to look?

It may be future proof to make your workflow run against kubernetes api instead of rancher api