Cluster Agent Operator
Cluster Agent Operator is a Kubernetes operator for deploying and managing the AppDynamics Cluster Agent, giving platform teams a declarative way to run,…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
67/100 Good
- Maintained
- 99last commit 44 days ago
- Popular
- 50305 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
No GitHub repository data collected yet.
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Initialize the management cluster first Run the clusterctl init command for your infrastructure provider, such as --infrastructure vcd, before trying to create any workload clusters. This installs cert-manager and the provider controllers; without it, Cluster API has no components to manage cluster creation. source
- Set Metal3 variables before generating a cluster If using Metal3, set the Metal3 environment variables (temporary settings your commands read) for partition, project ID, control-plane IP, and machine images/sizes first. Wrong or missing values can make node provisioning fail or create the wrong firewall and worker nodes. source
- Check controller deployments show 1/1 After initialization, check that the Cluster API and cert-manager deployments show 1/1 (one running copy). If a controller is not running, the Cluster API objects may not be processed, and your cluster will not come up as expected. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
After applying the cluster-agent-operator YAML and creating the Kubernetes secret, what symptom has been reported for the Cluster Agent pod?
The Cluster Agent pod has been reported stuck in CrashLoopBackOff after applying the cluster-agent-operator YAML and creating the Kubernetes secret.
Which YAML files should I use when upgrading the Operator or Cluster Agent?
Use the latest YAML configuration files for the Operator and Cluster Agent from the upgraded version, because the Cluster Agent may support new or modified configuration.
Answers sourced from community.splunk.com, help.splunk.com
Community
- Cluster Agent Pod Stuck in CrashLoopBackOff - Splunk Community (other)
- Cluster Agent Pod Stuck in CrashLoopBackOff - Splunk Community (other)
Collected 48 days ago - public community threads