Frequently Asked Questions

• KubeSlice is a cloud native solution that enables the creation of Super Clusters that connect applications across distributed Kubernetes clusters. These Super Clusters facilitate seamless communication between services and streamline the management of policies, resource quotas, RBAC(Role-Based Access Control) across a fleet of clusters.

The benefits of KubeSlice are:

• Secure application communication across distributed clusters,
• Simplified application deployments across multi-cluster and multi-cloud.
• Increases devops and development agility.
• Solves overlapping IP addresses problems in multi-cluster setups.
• Reduces cloud costs through its chargeback and resource quotas management for multi-cluster.
• Enables range of multi-cluster use cases like multi-region disaster recovery, distributing Kafka broker deployment, application migration for hybrid cloud and application bursting for hybrid cloud.

• KubeSlice has two components: a controller and gateway pods that's installed in each of the clusters. The gateway pods create secure OpenVPN tunnels between clusters that are NIST/FIPS 140-2 compliant. The KubeSlice controller manages policies, RBAC, resource quotas, namespaces, application latencies across multi cluster deployments.

Features of KubeSlice:

• Secure multi-cluster application connectivity.
• Secure communication between services across multi-cluster.
• Multi-tenancy and micro segmentation(isolation) of application namespaces,
• Solves for overlapping IP addresses across multi-cluster.
• Multi-cluster namespace management,
• Multi-cluster RBAC management,
• Multi-cluster policy management,
• Multi-cluster resource quota management.
• Single pane of glass observability for multi-cluster and multi-cluster deployments.

• First install the controller.
• Next install a gateway node in each cluster, 
• Then set up a Slice using the UI or KubeSlice- CLI.

Once that is done you can start managing your multi-cluster deployments.

• For Cluster-to-Cluster Connectivity: Solutions like Submariner, Cilium, and Skupper are some options.
• For Application-Level Connectivity Across Clusters: When it comes to other multi-cluster features, particularly at the application level, KubeSlice stands out as there are no other solutions offering comparable capabilities in the market.

• "Avesha KubeSlice is a smart tool that allows us to easily connect workloads from datacenters to clouds. If you are running Kubernetes in Hybrid Cloud, you get faster resiliency with Avesha KubeSlice. Also the ability to isolate workloads by tenant with Slices is a game changer for Hybrid Cloud." - John Repucci Director of Solution Architecture, Ensono.
• “Cox Edge operates a complex and highly distributed edge cloud network across data centers in the US, so the ability to establish secure, low latency connectivity, and intelligently manage traffic routing is a core requirement. We evaluated all sorts of network solutions, and Avesha’s KubeSlice really stood up not only as a solution to today's challenges, but as a framework to build additional networking products and capabilities in the future.” - Ron Lev GM, Cox Edge.

KubeSlice enables a range of multi-cluster use cases:

• Multi-region disaster recovery
• Distributing Kafka broker deployment
• Application migration for hybrid cloud
• Application bursting for hybrid cloud
• Multi-cloud/hybrid cloud application connectivity
• Chargeback for teams

• https://docs.avesha.io/documentation/enterprise
• https://kubeslice.io/documentation/open-source

• Yes, but it is a multi-cluster/region/cloud CNI. It works as an overlay on top of any CNI running locally at each of the clusters is spans.

• Cillium does not support inter-domain connectivity

• Service Meshes automate mTLS and discovery inside a cluster. They can continue to offer this functionality inside KubeSlice, where external services would appear local (via the KubeSlice Gateway Pod) to the Service Mesh.

• Namespaces are the elements used to enforce isolation among tenants in KubeSlice. Each slice is viewed as a separate tenant as defined by the namespaces in it.