Frequently Asked Questions

This topic describes the questions that are categorized based on KubeSlice features. The FAQs also include a separate category for generic questions related to KubeSlice.

General

What are the KubeSlice Open Source features?

KubeSlice Open Source Features

• Multi-cluster connectivity
  • On-prem, EKS, GKE, AKS, OCP, LKE, etc.
    • Slice specific L3 overlay network, CNI agnostic, slice subnet, IPAM, and QoS/priority
  • Full mesh connectivity
  • Micro-segmentation and isolation
  • Automation of Gateways, OpenVPN tunnels, redundant tunnels, and key rotation
  • NSM overlay network in clusters
  • Pod-to-pod connectivity over the overlay network
• Namespace association
  • Application namespaces
    • One or more namespaces can be associated with a slice.
  • Allowed namespaces
• Application onboarding
  • Application services/pods are onboarded on to a slice.
• Network policy, isolation, and monitoring
  • Network policies applied to all the associated application namespaces across all clusters associated with a slice.
  • Worker Operator monitors for drifts, alerts, and remediation
• Service discovery across a slice
  • Service export and import
  • Service-to-service connectivity over the slice overlay network
• Istio service mesh integration
  • Control plane per cluster
• Service imports as virtual services
  • E/W ingress/egress gateways
  • mTLS across clusters
• KubeSlice Controller
  • KubeSlice Control Plane and GitOps
  • Extends Kubernetes Control Plane
  • Multiple projects/tenants
  • Configuration/state managed using CRDs
  • Slice management, operations, and policies

Usage and Benefits

How is KubeSlice useful to me?

KubeSlice creates a flat, secure virtual network overlay for streamlined data distribution and communication between distributed workloads. It enables multi-tenancy and reduces deployment time, complexity, and costs for multi-cloud, hybrid cloud, and edge environments. KubeSlice seamlessly integrates with the Kubernetes ecosystem.

How do I use KubeSlice to onboard applications?

KubeSlice supports slice creation. A slice can be connected to worker clusters, and applications from those connected clusters can be onboarded onto the slice. To learn more, see onboarding applications.

How do I distribute my applications across clusters?

You can onboard applications from your cluster onto a slice by onboarding namespaces and create a service export to distribute applications across clusters. The other clusters must also be part of that slice. To learn more, see Service Export.

Dynamic IPAM

Can I change sliceIpamType on an existing slice?

No. You cannot change this setting. The sliceIpamType parameter is immutable. To use Dynamic IPAM, create a new slice. For more information, see create slices.

I receive ErrNoAvailableSubnets. What should I do? ?

This occurs when no subnets are available for allocation. Remove unused clusters from the slice or create a new slice.

Are released subnets reused?

Yes. Released subnets are persisted for 24 hours, so when a cluster rejoins, it receives the same subnet as before.

Does enabling Dynamic IPAM for a new slice will impact existing slices?

No. enabling Dynamic IPAM for a new slice does not affect a existing slice. Existing slices continue to operate using Static IPAM. Dynamic IPAM is fully backward compatible.

How long are released subnets retained?

Released subnets are preserved for 24 hours before cleanup, allowing clusters to rejoin within the grace period.