ArgoCD Workertools

Octopus Deploy workertools container image that provides the ArgoCD command-line interface (CLI) to a dynamic worker, letting it run Argo CD operations from a…

  • Development
  • Infrastructure
  • Tools & Utilities
Octopus Deploy workertools container image that provides the ArgoCD command-line interface (CLI) to a dynamic worker, letting it run Argo CD operations from a deployment step.

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

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

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

  • Set up its namespace and installer Make sure kubectl can reach your cluster, then replace <updater_namespace> and run both commands to create a dedicated Kubernetes namespace and apply the installer. Without that named area, the manifest has nowhere to go and the install can fail or collide with other apps. source
  • Add a Grafana dashboard if desired If you run Grafana, import the provided dashboard example to see image-updater metrics. It is optional, but without it you have fewer graphs to check that updates are running. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I stop Argo CD from trying to refresh the external Helm stable repository when I only use internal Helm repositories?

Make sure requirements.yaml uses only internally available Helm repositories. If Helm still tries to refresh the stable repo, override the stable repo URL in the argocd-cm ConfigMap as a workaround.

What prerequisites and namespace steps are needed to install Argo CD image-updater?

Make sure kubectl can reach the cluster, then replace the placeholder updater_namespace. Run the commands to create a dedicated Kubernetes namespace and apply the installer, otherwise the manifest has nowhere to go and installation can fail or collide with other apps.

What common Argo CD problem categories should I check when something is broken?

Look for sync failures, authentication errors, cluster connection problems, performance bottlenecks, and webhook misconfigurations.

Answers sourced from argo-cd.readthedocs.io, argocd-image-updater.readthedocs.io, mindfulchase.com

Community

Collected 48 days ago - public community threads