Back to Integrations

Kubernetes Integration

Secure access to any Kubernetes distribution with RBAC integration, namespace isolation, and comprehensive audit logging for multi-cluster environments.

Features

Comprehensive Kubernetes Security

Secure access to all your Kubernetes clusters with unified authentication and authorization.

Multi-Cluster Management

Unified access control across multiple Kubernetes clusters with centralized authentication and authorization.

RBAC Integration

Seamlessly integrate with Kubernetes RBAC for fine-grained access control and role-based permissions.

kubectl Access

Native kubectl support with certificate-based authentication and automatic kubeconfig generation.

Session Recording

Record all kubectl commands and pod exec sessions for compliance and security auditing.

Capabilities

Enterprise-Grade Kubernetes Access

Kubernetes API proxy
RBAC policy enforcement
Namespace-level access
Pod exec recording
kubectl command audit
Multi-cluster discovery
Service account mapping
Impersonation controls
Admission webhook
Network policy sync
Secret management
Context switching
Setup

Get Started in Minutes

Follow these simple steps to integrate TigerAccess with your Kubernetes clusters.

1

Configure Cluster Integration

Register your Kubernetes cluster with TigerAccess and configure the API proxy endpoint.

tacctl clusters add k8s \
  --name=prod-cluster \
  --api-server=https://k8s.example.com \
  --ca-cert=/path/to/ca.crt \
  --labels=env=production,region=us-east-1
2

Deploy TigerAccess Agent

Install the TigerAccess agent in your cluster to enable session recording and advanced features.

kubectl apply -f - <<EOF
apiVersion: v1
kind: Namespace
metadata:
  name: tigeraccess
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: tigeraccess-agent
  namespace: tigeraccess
spec:
  replicas: 1
  selector:
    matchLabels:
      app: tigeraccess-agent
  template:
    metadata:
      labels:
        app: tigeraccess-agent
    spec:
      containers:
      - name: agent
        image: tigeraccess/agent:latest
        args:
        - start
        - --roles=agent
        - --auth-server=tigeraccess.example.com:3025
EOF
3

Access Cluster

Use tac to access your Kubernetes cluster with automatic certificate authentication.

tac kube login prod-cluster
# Generates kubeconfig with short-lived certificate

kubectl get pods --all-namespaces
# All commands are audited and recorded

tac kube exec prod-cluster nginx-pod -- /bin/bash
# Interactive sessions are recorded
Use Cases

Real-World Kubernetes Scenarios

Multi-Tenant Cluster Access

Provide developers with namespace-scoped access to shared Kubernetes clusters with automatic RBAC enforcement and session recording.

Production Troubleshooting

Grant just-in-time access to production clusters for debugging with comprehensive audit trails of all kubectl commands and pod exec sessions.

Multi-Cluster Operations

Manage access across development, staging, and production clusters with unified authentication and centralized policy management.

Compliance & Audit

Meet compliance requirements with detailed logs of all Kubernetes API calls, including who accessed what resources and when.

FAQ

Frequently Asked Questions

Does TigerAccess work with all Kubernetes distributions?

Yes. TigerAccess works with any Kubernetes distribution including self-managed clusters, EKS, GKE, AKS, OpenShift, Rancher, and more. It integrates at the Kubernetes API level for universal compatibility.

How does TigerAccess integrate with Kubernetes RBAC?

TigerAccess can map users to Kubernetes service accounts or groups, leveraging your existing RBAC policies. It can also enforce additional access policies on top of Kubernetes RBAC for enhanced security.

Can I restrict access to specific namespaces?

Yes. TigerAccess supports namespace-level access controls. You can grant users access to specific namespaces while restricting access to others, with full audit logging of all operations.

What kubectl commands are recorded?

All kubectl commands are logged including get, create, delete, apply, exec, logs, and more. For interactive sessions like kubectl exec, TigerAccess records the entire terminal session with keystroke-level detail.

How does multi-cluster management work?

TigerAccess provides a unified interface for accessing multiple clusters. Users authenticate once and can switch between clusters seamlessly. Access policies can be defined per-cluster or globally across all clusters.

Ready to Secure Your Infrastructure?

Join thousands of security-conscious teams using TigerAccess to protect their critical infrastructure and AI agents.

No credit card required • 14-day free trial • Enterprise support available