Clusters
Faros provides a centralized platform for managing multiple Kubernetes clusters through a unified interface. Clusters are registered with Faros via lightweight agents that provide secure, read-only access for monitoring and analysis.
What is a Cluster in Faros?
A Cluster in Faros represents a registered Kubernetes cluster that is connected to the Faros platform. Each cluster:
- Has a unique name within your organization
- Runs a lightweight Faros agent for connectivity
- Maintains its own lifecycle and status
- Can be accessed remotely via SSH or API
- Exposes metrics and data for AI-powered analysis
Cluster Lifecycle
Clusters in Faros go through the following phases:
- Pending: Cluster resource has been created but initialization hasn’t started
- Initializing: Cluster is being set up, agent is being configured
- Ready: Cluster is fully connected and operational
- Failed: Cluster encountered an error during setup or operation
- Deleting: Cluster is being removed from Faros
- Deleted: Cluster has been successfully removed
Agent Architecture
When you initialize a cluster in Faros, an Agent resource is created. The agent:
- Runs as a deployment in your Kubernetes cluster
- Establishes a secure WebSocket tunnel to Faros
- Uses JWT authentication for secure communication
- Provides read-only access to cluster resources
- Exposes MCP (Model Context Protocol) servers for AI integration
- Sends periodic heartbeats to maintain connection status
Agent Deployment
The agent is deployed to your cluster using standard Kubernetes manifests:
apiVersion: core.faros.sh/v1alpha1
kind: Agent
metadata:
name: <cluster-name>
spec:
clusterName: <cluster-name>
token: <jwt-token>
Remote Access
Faros provides secure remote access to your clusters without exposing them to the internet:
SSH Access
kubectl faros clusters ssh <cluster-name>
This opens an interactive terminal session that:
- Uses WebSocket-based SSH tunneling
- Supports full terminal features (colors, resize, signals)
- Authenticates using your Faros credentials
- Provides secure access without VPN or direct network exposure
MCP Server Access
For AI and LLM integration, clusters expose MCP servers:
kubectl faros clusters mcp <cluster-name>
This provides connection details for AI agents to query cluster data and metrics.
Multi-Cluster Management
Faros is designed for organizations managing multiple clusters:
- Unified View: List and manage all clusters from one interface
- Consistent Tooling: Same CLI commands work across all clusters
- Centralized Authentication: Single sign-on via OAuth for all clusters
- RBAC Integration: Kubernetes-native access control using ClusterRoleBindings
Security Model
Faros clusters follow these security principles:
- Read-Only by Default: Agents provide read-only access to cluster data
- No Inbound Connections: Clusters initiate outbound connections only
- Token-Based Authentication: JWT tokens authenticate agents
- Kubernetes-Native RBAC: Standard Kubernetes roles control access
- TLS Encryption: All communication is encrypted in transit
Use Cases
Common scenarios for Faros cluster management:
- Multi-Cluster Monitoring: Track status of production, staging, and development clusters
- AI-Powered Analysis: Connect AI agents to analyze cluster health and performance
- Remote Troubleshooting: SSH into clusters without direct network access
- Team Collaboration: Share cluster access with team members via RBAC
- Compliance Auditing: Centralized access logs and audit trails
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.