Skip to content

chore: remove legacy Harbor CA DaemonSet - #9

Merged
surrealwolf merged 1 commit into
mainfrom
chore/remove-harbor-ca-daemonset
Aug 1, 2026
Merged

surrealwolf merged 1 commit into
mainfrom
chore/remove-harbor-ca-daemonset

Conversation

@surrealwolf

Copy link
Copy Markdown
Collaborator

Summary

  • Remove containerd-harbor-cert-config DaemonSet and its kustomization entry — Harbor (harbor.dataknife.net) now uses Let's Encrypt, so no custom CA injection is needed.
  • Delete scripts/restart-rke2-services.sh, which only existed to apply that Harbor CA config on RKE2 nodes.
  • Document LE Harbor + post-sync cleanup: Fleet keepResources: true on gitops-mcp-prd-apps may leave the DS/secret behind.

Test plan

  • Confirm PR diff drops only the Harbor CA DS, kustomization ref, and restart script (no MCP deployment changes)
  • After merge, wait for Fleet sync of gitops-mcp-prd-apps
  • On prd-apps, if orphans remain, manually delete:
    kubectl delete daemonset containerd-harbor-cert-config -n mcp-servers --context=prd-apps --ignore-not-found
    kubectl delete secret harbor-ca-cert -n mcp-servers --context=prd-apps --ignore-not-found
  • Verify MCP pods still pull from harbor.dataknife.net without TLS errors

Post-merge note

Do not rely on Fleet to garbage-collect these resources when keepResources is true. Delete DS containerd-harbor-cert-config and secret harbor-ca-cert in mcp-servers on prd-apps if they remain after sync.

Made with Cursor

Harbor uses Let's Encrypt; custom CA DS and RKE2 restart helper are obsolete.
Fleet keepResources may leave orphans on prd-apps — delete manually after sync.

Co-authored-by: Cursor <cursoragent@cursor.com>
@surrealwolf
surrealwolf merged commit bfe0d4d into main Aug 1, 2026
3 checks passed
@surrealwolf
surrealwolf deleted the chore/remove-harbor-ca-daemonset branch August 1, 2026 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant