Setting Up kube-bind

kube-bind supports multiple deployment scenarios and backend providers to meet different requirements.

Setup Options

Standard Kubernetes Setup

• Quickstart: Get started quickly with the default provider
• Helm Deployment: Production deployment using Helm charts
• Local Setup with Kind: Local development environment
• kubectl Plugin: Install and use the kubectl-bind plugin

Advanced Multi-Cluster Setup

• kcp Integration: Advanced multi-tenant setup with kcp workspaces and APIExports

Architecture Overview

Starting with v0.5.0, kube-bind uses a multicluster-runtime architecture that supports:

• Multiple Providers: Choose between standard Kubernetes or kcp backends
• Enhanced API: v1alpha2 API with resource-based exports and BoundSchema support
• Flexible Deployment: Support for various cluster topologies and requirements

Choose the setup that best fits your use case:

• Use Quickstart or Local Setup with Kind for development and testing
• Use Helm Deployment for production environments with standard Kubernetes
• Use kcp Integration for advanced multi-tenant scenarios with workspace isolation

Next Steps

After completing your setup, explore these guides:

• Usage Guide: Learn common workflows and the new Catalog API
• Migration Guide: Upgrade from previous versions
• Developer Documentation: Understand the architecture and contribute

Quickstart

Get started with kube bind.

Local kube-bind with kind

Installation with Helm

Install kube-bind on an existing Kubernetes cluster via the official Helm chart.

kubectl Plugins

How to install and use the kubectl bind plugin.