Provider Configuration
Configure target providers for cluster discovery
Provider Configuration Admin
Configure target providers that integrate with external cluster management platforms. The provider configuration interface adapts dynamically based on the selected provider.
This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.
Supported Providers
| Provider | Description |
|---|---|
| ACM / OCM | Discover and synchronize managed Kubernetes clusters through Red Hat Advanced Cluster Management or Open Cluster Management |
INFO
The provider configuration interface is extensible. New integration operators can add their configuration panels here. Cloud credentials are managed separately; see the section below.
Cloud Provider Configuration
Krkn Operator supports cloud scenarios that use saved provider credentials. Administrators create and manage these credentials through Cloud Credentials Management. Users can select credentials their group is allowed to access.
The following scenarios interact with provider infrastructure and need the corresponding cloud or bare-metal credentials:
| Scenario | Why Cloud Provider Is Required |
|---|---|
| node-scenarios | Stops, terminates, or reboots nodes via the cloud provider API |
| node-scenarios-bm | Controls bare metal nodes via BMC/IPMI credentials |
| power-outages | Shuts down and restarts the entire cluster through the cloud provider |
| zone-outages | Simulates availability zone failures by manipulating cloud network resources |
INFO
Cloud credentials are stored as Kubernetes Secrets and injected into scenario pods through
SecretKeyRef. Users must have access to the saved credential through their group. For setup and provider-specific fields, see Cloud Credentials Management.