How 0jk6/conjur-operator works
Main Components
a) Core Operator Components:
• Controller Manager (main control loop)
• Custom Resource Definition (CRD) for Conjur type
• Webhook Server (if applicable)
• RBAC Components (ServiceAccount, Roles, RoleBindings)
b) External Systems:
• CyberArk Conjur Vault
• Kubernetes API Server
• Target Kubernetes Secrets
┌─ Kubernetes Cluster ──────────────────────────────────────────┐
• ┌─ Operator Namespace ─────────────────────┐ │
• ┌─ Conjur Operator Pod ─────────────┐ │ │
• Controller Manager │ │ │
• Metrics Server │ │ │
• Leader Election │ │ │
• ┘ │ │
• ┘ │
• ┌─ Target Namespace ──────────────────────┐ │
• Conjur Custom Resource │ │
• Generated Kubernetes Secrets │ │
• ┘ │
• ┘
┌─ External Systems ─────────────────────────┐
• CyberArk Conjur Vault │
• Secrets Storage │
• Authentication │
• ┘
Key Interactions to Highlight
• Controller watching for Conjur CR changes (→)
• API calls to CyberArk Conjur Vault (↔)
• Secret creation/updates in target namespaces (→)
• RBAC permissions and scope (- - ->)
Technical Details
Annotations showing:
• Go version requirement (v1.21.0+)
• Kubernetes version compatibility (v1.11.3+)
• Container runtime requirements
• API Group: api.0jk6.github.io/v1alpha1
Implementation Notes
• The operator's reconciliation loop
• Secret management workflow
• Security boundaries
• Namespace isolation
• Resource ownership and garbage collection