loader
KubeSlice Manager

Observe, Isolate & Manage your hybrid &
multi cloud workloads

KubeSlice Manager (UI) is a single pane of glass observability & manageability tool for cloud workloads with actionable data & insights

You can observe and manage workloads by “tenant”

You can view real-time latency data

You can see traffic flow when applications communicate

Explore our easy to use interface

KubeSlice Manager(UI) Features

KubeSlice Manager (UI) has two sections: Dashboard & Setup. It’s very easy to create a “Slice” which connects workloads across clusters and clouds for hybrid and multi cloud use cases. With KubeSlice Manager (UI) you register clusters, connect clusters & onboard namespaces onto a “Slice”. If you create multiple “Slices” per tenant, each tenant Slice has its isolated set of applications which can communicate seamlessly across clusters and clouds over the “Slice.”

First, register the clusters for which you want to connect with a ”Slice”. A “Slice” is a virtual cluster that gets created across clusters. All applications on the Slice share the same resources & policies assigned to the Slice namespace. A Slice can extend across clusters and clouds.

Step 1: Enter cluster details

You can register a cluster in any cloud, region, datacenter or edge

Step 2: Generate cluster YAMLs

Download or copy a few lines of code for each cluster

Step 3: Register clusters

Clusters are registered with KubeSlice controller

Second, connect clusters that you have registered. You can select some of the clusters to connect with a “Slice”. A “Slice” is a virtual cluster that gets created across clusters. All applications on the Slice share the same resources & policies assigned to the Slice namespace. A Slice can extend across clusters and clouds. You can create multiple “Slices”

Step 1: Create a Slice

Enter some basic infrastructure information to create a “Slice”.

Step 2: Choose clusters to go on a Slice

The clusters can be in any region, cloud, datacenter or edge.

Step 3: Connect clusters with Slice

Slice gateways & secure tunnels are created to enable east-west communication paths between clusters.

You can create multiple Slices per tenant

For true isolation of application services by teams/customers, create multiple Slices and onboard only the relevant namespaces onto each Slice. For. Eg. Create a ”Dev Slice” with apps in Dev & a “Prod Slice” with apps in Prod. Remember the Slice can extend across cluster boundaries carrying the resources & policies with it.

Third, isolate applications with Slices so that you can use your infrastructure resources efficiently. Create a “high priority Slice” and onboard applications that need the highest bandwidth allocation onto it. All other applications not on the “high priority Slice” will be isolated and will receive lower traffic priority.

Step 1: Choose Namespaces

For each cluster which has been put on the Slice, explore and choose namespaces to put on the Slice. A namespace consists of one or more microservices.

Step 2: Execute YAML

All selected namespaces are put in the Slice YAML which when executed onboards the namespaces and services onto the Slice.

Repeat steps for multiple Slices

For multi-tenancy, create multiple Slices per customer/team and choose the relevant applications for each tenant to go on its corresponding Slice.