Kubernetes Integration
Kubernetes integration will allow Annie to connect to your clusters and provide deep insights into your container orchestration, workloads, and resource usage.Prerequisites
- Kubernetes 1.20+
- Helm 3.8+
- Anyshift API token (generate one at app.anyshift.io/integrations)
Installation
Option 1: Quick Installation
Option 1: Quick Installation
Step 1: Add the Anyshift Helm repository
Step 2: Install the agent
Option A: Using Kubernetes Secret (Recommended for Production)First, create a Kubernetes secret to store your API token securely:<YOUR_API_TOKEN>
with your API token from the integrations page and <YOUR_CLUSTER_NAME>
with a meaningful name for your cluster (e.g., “production-us-east”, “staging-eu”).Advanced Installation Examples
Cluster Name Templating Use Go template syntax for dynamic cluster names:Option 2: Custom Configuration
Option 2: Custom Configuration
Step 1: Create the secret (if using secret method)
If you’re using the secret method for token storage:Step 2: Create a values.yaml file
Create avalues.yaml
file with your custom configuration:Step 3: Install with custom values
Advanced Values File Examples
Dynamic Cluster Naming with Custom LabelsSecurity Configuration
Secrets Handling
By default, the agent tracks secrets metadata (name, namespace, labels, annotations) but never accesses actual secret contents. The agent only reads the metadata to understand the relationships and the topology. For environments with strict security requirements, you can disable secrets scanning: Option 1: Command lineClusterRole
permissions, preventing access to secrets.
Validate The Installation
Check that the agent is running:Upgrade
To upgrade the agent to the latest version:Uninstall
Supported Resources
The Anyshift Kubernetes agent v1 supports a wide range of resources across several API groups to provide a comprehensive view of your cluster. Here is the full list of supported resources:Core Resources
- Pods
- Services
- Nodes
- Namespaces
- ServiceAccounts
- ConfigMaps
- Secrets
- PersistentVolumeClaims (PVCs)
- PersistentVolumes (PVs)
Apps Resources
- Deployments
- ReplicaSets
- DaemonSets
- StatefulSets
Networking Resources
- Ingresses
RBAC Resources
- Roles
- ClusterRoles
- RoleBindings
- ClusterRoleBindings
Autoscaling & Availability
- HorizontalPodAutoscalers (HPA)
- PodDisruptionBudgets (PDB)
Batch Resources
- Jobs
- CronJobs
Permissions Overview
The agent requires read-only access to cluster resources. Here are the exactClusterRole
permissions: