unkin/argocd-apps
2
0
Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Deploy bind-operator (operator + CRDs) #219

Merged
benvin merged 1 commits from benvin/deploy-bind-operator into main 2026-07-03 20:04:58 +10:00
Conversation 0 Commits 1 Files Changed 16
+2082
unkinben commented 2026-07-03 19:55:00 +10:00
Owner
Copy Link
Copy Source

First of a 4-PR split of the bind rollout (was #216). Deploys just the operator control plane so it can be verified before any DNS clusters exist.

Why

Roll out incrementally: operator + CRDs first, then each BIND tier as its own PR.

Changes

  • apps/base/bind-system: operator Deployment (git.unkin.net/unkin/bind-operator:v0.1.1), RBAC, namespace; CRDs pulled from the operator repo by raw URL (config/crd/install.yaml @ v0.1.1)
  • au-syd1 bind-system overlay
  • register all four bind apps in argocd/applicationsets/platform.yaml (DNS overlays instantiate only when their dirs land in the follow-up PRs)
  • add binddns-* namespaces to argocd/projects/platform.yaml
  • add schemas/bind.unkin.net/*.json for kubeconform

Deploy impact

Operator pod + CRDs only. No DNS services yet — the operator is idle until BindClusters exist.

Follow-ups (merge after this)

binddns-auth, binddns-resolver, binddns-externaldns — one PR each.

First of a 4-PR split of the bind rollout (was #216). Deploys just the operator control plane so it can be verified before any DNS clusters exist. ## Why Roll out incrementally: operator + CRDs first, then each BIND tier as its own PR. ## Changes - `apps/base/bind-system`: operator Deployment (`git.unkin.net/unkin/bind-operator:v0.1.1`), RBAC, namespace; CRDs pulled from the operator repo by raw URL (`config/crd/install.yaml` @ v0.1.1) - au-syd1 `bind-system` overlay - register all four bind apps in `argocd/applicationsets/platform.yaml` (DNS overlays instantiate only when their dirs land in the follow-up PRs) - add `binddns-*` namespaces to `argocd/projects/platform.yaml` - add `schemas/bind.unkin.net/*.json` for kubeconform ## Deploy impact Operator pod + CRDs only. No DNS services yet — the operator is idle until BindClusters exist. ## Follow-ups (merge after this) binddns-auth, binddns-resolver, binddns-externaldns — one PR each.
unkinben added 1 commit 2026-07-03 19:55:00 +10:00
Deploy bind-operator (operator + CRDs)
ci/woodpecker/pr/pre-commit Pipeline was successful
Details
ci/woodpecker/pr/kubeconform Pipeline was successful
Details
edbb62cca4 
Deploys the bind-operator control plane on its own so it can be verified
before any DNS clusters are created. The three BIND tiers follow as
separate PRs.

- add apps/base/bind-system: operator Deployment (image v0.1.1), RBAC,
  namespace, and CRDs pulled from the operator repo by raw URL
- add au-syd1 bind-system overlay
- register all four bind apps in the platform ApplicationSet (the DNS
  overlays are instantiated only once their dirs land in later PRs)
- add binddns-* namespaces to the platform AppProject destinations
- add schemas/bind.unkin.net/*.json so kubeconform validates the CRs
benvin merged commit 4b8f9313c8 into main 2026-07-03 20:04:58 +10:00
benvin deleted branch benvin/deploy-bind-operator 2026-07-03 20:04:58 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#219
Delete Branch "benvin/deploy-bind-operator"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?