Skip to content

bug(k0s): argocd-server manifest is incomplete and fails readiness probe without Redis and controllers #177

Closed as not planned

Description

@castrojo

Defect Finding

files/k0s/manifests/argocd/install.yaml currently ships only:

  • Namespace argocd
  • ServiceAccount argocd-server
  • ConfigMap argocd-cm
  • Deployment argocd-server
  • Service argocd-server

Symptoms

During live first-boot VM testing, argocd-server fails its readiness probe (http://:8080/healthz) and never becomes ready (0/1 Running, 60+ restarts):

Warning  Unhealthy  kubelet  Readiness probe failed: Get "http://10.244.0.X:8080/healthz": dial tcp 10.244.0.X:8080: connect: connection refused

Root Cause

argocd-server requires Redis (argocd-redis), repository server (argocd-repo-server), application controller (argocd-application-controller), and corresponding cluster RBAC roles to start its API services and bind port 8080. Without those supporting components in the manifest, the API server cannot finish initialization.

Recommendation

Vendor the complete lightweight/core Argo CD manifest stack into files/k0s/manifests/argocd/ (including redis, repo-server, application-controller, and RBAC) so the stack reaches healthy readiness out of the box.

Activity

  1. Danathar commented on Sep 21, 2026

    @Danathar
    Contributor

    Tracking note: #213 is closed. #210 replaces the k0s Argo CD install with Argo CD Core, which removes argocd-server altogether, so this issue resolves when #210 merges.

  2. Danathar commented on Sep 30, 2026

    @Danathar
    Contributor

    Correction to my tracking note above: #210 didn't merge. It was closed on 2026-09-29 as superseded by #262, and #262 left k0s and Argo CD in place. So this issue was not resolved the way I said it would be.

    On main (9a399ca), files/k0s/manifests/argocd/install.yaml is still the 76-line stub with only a Namespace, a ServiceAccount, argocd-cm, the argocd-server Deployment and its Service. There's still no Redis, repo-server or application-controller, so the readiness problem described here should still apply wherever the k0s sysext is enabled. I haven't booted it to confirm that.

    Which way to fix it depends on the k0s decision @jeefy mentioned on #210 ("the k0s-removal part is still a separate decision"). The options are: ship the full Argo CD core stack (as #213 did), switch to Argo CD Core without argocd-server, or drop Argo CD along with k0s. I'll leave that choice to the maintainers.

  3. castrojo commented on Oct 3, 2026

    @castrojo
    ContributorAuthor

    Resolved on main by commit 6f5f4d6 (#353), which shipped the complete Argo CD manifest stack (CRDs, repo-server, application-controller, redis, and RBAC) in files/homelab/manifests/50-argocd/.

  4. jeefy commented on Oct 3, 2026

    @jeefy
    Collaborator

    Obsolete: #358 removed the k0s sysext's bundled argocd/install.yaml. Argo CD now ships in the homelab sysext, rendered from the pinned upstream chart with all components, and is applied by bluefin-homelab-apply on kubeadm or k0s (#353). The QEMU homelab checks bring it up Ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething is broken.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions