Skip to content

KubeStellar has multiple documentation versions to match its multiple releases.
Please make sure you are viewing the docs version which matches the release version of the code you are using!

Check out KubeStellar working with Turbonomic:#

Medium - Make Multi-Cluster Scheduling a No-Brainer

Turbonomic and KubeStellar Demo Day#

How do I get this working with my KubeStellar instance?#

As we can see from the blog and the demo, Turbonomic talks to KubeStellar via GitOps. The scheduling decisions are passed from Turbonomic to KubeStellar in two steps: 1. Turbo -> GitHub repository. 2. GitHub repository -> KubeStellar.

For the 1st step (Turbonomic -> GitHub repository), a controller named "change reconciler" creates PRs against the GitHub repository, where the PRs contains changes to scheduling decisions.

There's also a piece of code which intercepts Turbonomic actions and creates CRs for the above change reconciler.

For the 2nd step (GitHub repository-> KubeStellar), we can use Argo CD. The detailed procedure to integrate Argo CD with KubeStellar is documented here.

As we can see from the blog and the demo, Turbonomic collects data from edge clusters. This is made possible by installing kubeturbo into each of the edge clusters.

Turbonomic and KubeStellar in the news#