mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
* feat(api): hard-fork CRD API group argoproj.io -> deploy.hanzo.ai
Hanzo CD hard-fork, phase 1.1. Single source of truth is
pkg/apis/application/register.go's Group constant (Application/AppProject/
ApplicationSet all derive their FullName from it); every other Go call-site
that hardcoded the literal group string is updated to match: the 3 generated
informer GVRs, the app-of-apps nested-Application detector in types.go, the
resource-tree Application-kind cache populator, the 3 NotFound error
constructors in server/application, and the applicationset-controller's
leader-election Lease name/ID (kept in lockstep across Go source + RBAC
resourceNames, or leader election would get RBAC-denied on startup).
CRD YAMLs (application/appproject/applicationset) and every RBAC apiGroups
rule that actually governs our 3 CRDs are repointed to deploy.hanzo.ai, across
both manifests/base/* (namespaced Roles) and manifests/cluster-rbac/* (cluster
scope). Two adjacent things that share the "argoproj.io" string but are NOT
ours are deliberately left untouched: gitops-engine's health-check dispatch
for Argo Workflows' `Workflow` kind, and argocd-server-clusterrole's second
apiGroups block granting read on Argo Workflows' `workflows` resource — both
belong to a separate, unrelated Argoproj-family project we are not forking.
Also untouched, per explicit scope: annotation/label keys (argocd.argoproj.io/*)
and finalizers (*.argoproj.io) that track already-applied live resources, and
argocd-cm.yaml's resource.customizations.ignoreResourceUpdates keys (a narrow
app-of-apps diffing nicety, not build- or RBAC-relevant).
CGO_ENABLED=0 go build ./... verified green.
* ci: wire canonical hanzo.yml + cicd.yml (Hanzo CD image build)
Phase 1.3. Follows the same one-way pattern every hanzo/lux/zoo repo uses:
hanzo.yml declares the image (root Dockerfile -> ghcr.io/hanzoai/deploy) and a
fast go-build sanity test (the multi-stage Dockerfile build is the slow, real
gate); cicd.yml is the ~10-line trigger shim importing hanzoai/ci's reusable
build workflow on the arc pool, secrets from KMS only.
No `deploy:` block yet, matching the hanzoai/cms build-only-first-cutover
pattern: this repo's own live hanzo-cd namespace runs the whole Hanzo fleet's
GitOps, so the prod image/CRD swap is a deliberate separate action (see the
[HELD] universe PR), never an automatic rollout on merge. Every PR/push still
builds and pushes an immutable ghcr.io/hanzoai/deploy:sha-<7>-amd64 image.
* feat(ui): rebrand Argo CD -> Hanzo CD (title, favicon, logo, sidebar)
Phase 1.2. User-facing "Argo CD"/"ArgoCD" text replaced with "Hanzo CD"
across the login page, help modal, settings screens, version-info panel,
sync-options warning, fullscreen-logs title, app.tsx page titles, and
index.html's <title>/noscript text (dropped the now-wrong upstream CLI
doc link rather than invent a hanzo.ai URL that doesn't exist).
Logo/favicon assets replaced with the canonical Hanzo mark (never
hand-drawn, copied from ~/work/hanzo/logo/dist): the two real usages of
Argo's logo collapse onto one Hanzo glyph (mono + white variants) at the
same 5 call sites (login icon + footer, login.scss $logoPath/
$logoNegativePath, sidebar text-logo), preserving the existing CSS
invert() filters so both the light login panel and dark sidebar still
render correctly. Old argologo.svg/argo_o.svg/argo.png deleted (no
longer referenced). favicon-{16x16,32x32}.png added at
ui/src/assets/favicon/ (index.html's links to that path were previously
dead - the directory didn't exist in this checkout). package.json name
argo-cd-ui -> hanzo-cd-ui.
Left alone, deliberately: the two Kubernetes resource-kind icon sets
under ui/src/assets/images/resources/ (unrelated to branding), and
upstream doc/project links (argoproj.io, argo-cd.readthedocs.io) since
we have no equivalent hanzo.ai docs to point to yet - except the login
footer logo's outbound link, which now points to hanzo.ai instead of
argoproj.io (a Hanzo-branded mark linking to the upstream project it
was forked from read as an obvious leftover).
* feat(module): rename Go module github.com/argoproj/argo-cd/v3 -> github.com/hanzoai/deploy
Phase 2. No version suffix on the new path (org policy: never publish our
own Go modules above v1.x.x / with a v2+ suffix) — this fork starts a fresh
v0/v1 module identity rather than carrying the v3 the upstream fork point
had reached.
Mechanical, symmetric rewrite: 704 .go files (import statements only; two
disjoint substitutions applied specific-first so the nested gitops-engine
module path never double-matches), plus go.mod (module line, the
gitops-engine require+replace pair, version reset to v0.0.0-... since a
suffix-less path can't carry a v3 semver), gitops-engine/go.mod, Makefile
(ldflags PACKAGE + 2 TEST_MODULE filters), .golangci.yaml, .goreleaser.yaml,
.mockery.yaml (+ gitops-engine's), Procfile, the codegen/proto generation
scripts (hack/generate-proto.sh, update-codegen.sh, update-openapi.sh), and
20 .proto files' go_package options. Also one OpenTelemetry tracer name
string in gitops-engine/pkg/sync/sync_context.go (a cosmestic label, not an
import, but worth keeping consistent).
CGO_ENABLED=0 go build ./... verified green for both the root module and
the nested gitops-engine module; go vet clean on both; go mod tidy run
(network available) to reconcile go.sum, dependency set unchanged.
Left alone, deliberately: doc-only mentions (docs/snyk/*.html scan reports,
gitops-engine/README.md), a comment-only reference in
.github/workflows/release.yaml, and one Renovate bot config line — none are
build- or codegen-load-bearing. Also left alone: comments citing upstream
GitHub issue URLs (github.com/argoproj/argo-cd/issues/NNNNN) and a handful
of test fixtures using "https://github.com/argoproj/argo-cd.git" as a
representative example repo URL — both are accurate historical/test-data
references, not stale self-references.
---------
Co-authored-by: Hanzo Dev <[email protected]>
135 lines
4.4 KiB
Go
135 lines
4.4 KiB
Go
package health
|
|
|
|
import (
|
|
"fmt"
|
|
"strings"
|
|
|
|
corev1 "k8s.io/api/core/v1"
|
|
"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured"
|
|
"k8s.io/apimachinery/pkg/runtime"
|
|
"k8s.io/kubectl/pkg/util/podutils"
|
|
|
|
"github.com/hanzoai/deploy/gitops-engine/pkg/utils/kube"
|
|
)
|
|
|
|
func getPodHealth(obj *unstructured.Unstructured) (*HealthStatus, error) {
|
|
gvk := obj.GroupVersionKind()
|
|
switch gvk {
|
|
case corev1.SchemeGroupVersion.WithKind(kube.PodKind):
|
|
var pod corev1.Pod
|
|
err := runtime.DefaultUnstructuredConverter.FromUnstructured(obj.Object, &pod)
|
|
if err != nil {
|
|
return nil, fmt.Errorf("failed to convert unstructured Pod to typed: %w", err)
|
|
}
|
|
return getCorev1PodHealth(&pod)
|
|
default:
|
|
return nil, fmt.Errorf("unsupported Pod GVK: %s", gvk)
|
|
}
|
|
}
|
|
|
|
func getCorev1PodHealth(pod *corev1.Pod) (*HealthStatus, error) {
|
|
// This logic cannot be applied when the pod.Spec.RestartPolicy is: corev1.RestartPolicyOnFailure,
|
|
// corev1.RestartPolicyNever, otherwise it breaks the resource hook logic.
|
|
// The issue is, if we mark a pod with ImagePullBackOff as Degraded, and the pod is used as a resource hook,
|
|
// then we will prematurely fail the PreSync/PostSync hook. Meanwhile, when that error condition is resolved
|
|
// (e.g. the image is available), the resource hook pod will unexpectedly be executed even though the sync has
|
|
// completed.
|
|
if pod.Spec.RestartPolicy == corev1.RestartPolicyAlways {
|
|
var status HealthStatusCode
|
|
var messages []string
|
|
|
|
for _, containerStatus := range pod.Status.ContainerStatuses {
|
|
waiting := containerStatus.State.Waiting
|
|
// Article listing common container errors: https://medium.com/kokster/debugging-crashloopbackoffs-with-init-containers-26f79e9fb5bf
|
|
if waiting != nil && (strings.HasPrefix(waiting.Reason, "Err") || strings.HasSuffix(waiting.Reason, "Error") || strings.HasSuffix(waiting.Reason, "BackOff")) {
|
|
status = HealthStatusDegraded
|
|
messages = append(messages, waiting.Message)
|
|
}
|
|
}
|
|
|
|
if status != "" {
|
|
return &HealthStatus{
|
|
Status: status,
|
|
Message: strings.Join(messages, ", "),
|
|
}, nil
|
|
}
|
|
}
|
|
|
|
getFailMessage := func(ctr *corev1.ContainerStatus) string {
|
|
if ctr.State.Terminated != nil {
|
|
if ctr.State.Terminated.Message != "" {
|
|
return ctr.State.Terminated.Message
|
|
}
|
|
if ctr.State.Terminated.Reason == "OOMKilled" {
|
|
return ctr.State.Terminated.Reason
|
|
}
|
|
if ctr.State.Terminated.ExitCode != 0 {
|
|
return fmt.Sprintf("container %q failed with exit code %d", ctr.Name, ctr.State.Terminated.ExitCode)
|
|
}
|
|
}
|
|
return ""
|
|
}
|
|
|
|
switch pod.Status.Phase {
|
|
case corev1.PodPending:
|
|
return &HealthStatus{
|
|
Status: HealthStatusProgressing,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
case corev1.PodSucceeded:
|
|
return &HealthStatus{
|
|
Status: HealthStatusHealthy,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
case corev1.PodFailed:
|
|
if pod.Status.Message != "" {
|
|
// Pod has a nice error message. Use that.
|
|
return &HealthStatus{Status: HealthStatusDegraded, Message: pod.Status.Message}, nil
|
|
}
|
|
for _, ctr := range append(pod.Status.InitContainerStatuses, pod.Status.ContainerStatuses...) {
|
|
if msg := getFailMessage(&ctr); msg != "" {
|
|
return &HealthStatus{Status: HealthStatusDegraded, Message: msg}, nil
|
|
}
|
|
}
|
|
|
|
return &HealthStatus{Status: HealthStatusDegraded, Message: ""}, nil
|
|
case corev1.PodRunning:
|
|
switch pod.Spec.RestartPolicy {
|
|
case corev1.RestartPolicyAlways:
|
|
// if pod is ready, it is automatically healthy
|
|
if podutils.IsPodReady(pod) {
|
|
return &HealthStatus{
|
|
Status: HealthStatusHealthy,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
}
|
|
// if it's not ready, check to see if any container terminated, if so, it's degraded
|
|
for _, ctrStatus := range pod.Status.ContainerStatuses {
|
|
if ctrStatus.LastTerminationState.Terminated != nil {
|
|
return &HealthStatus{
|
|
Status: HealthStatusDegraded,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
}
|
|
}
|
|
// otherwise we are progressing towards a ready state
|
|
return &HealthStatus{
|
|
Status: HealthStatusProgressing,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
case corev1.RestartPolicyOnFailure, corev1.RestartPolicyNever:
|
|
// pods set with a restart policy of OnFailure or Never, have a finite life.
|
|
// These pods are typically resource hooks. Thus, we consider these as Progressing
|
|
// instead of healthy.
|
|
return &HealthStatus{
|
|
Status: HealthStatusProgressing,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
}
|
|
}
|
|
return &HealthStatus{
|
|
Status: HealthStatusUnknown,
|
|
Message: pod.Status.Message,
|
|
}, nil
|
|
}
|