unkinben
8a9cdf35fd
## Why v0.2.2's config-hash rolling restart exposed a latent non-determinism: `client.List` returns cache-ordered results, so the resolver's forward zones reshuffled every reconcile, flipping the config hash and rolling `bind-resolvers-2` endlessly. v0.2.3 (bind-operator #11) sorts every rendered list so `named.conf` is byte-identical across reconciles and the hash is stable. ## Changes - Bump the operator image (`bind-system/deployment.yaml`) and the pulled CRD bundle URL (`bind-system/kustomization.yaml`) to `v0.2.3`. - Bump the `bind-tsig-api` image (`bind-internal/tsig-api/tsig-api.yaml`) to `v0.2.3`. CRDs are unchanged from v0.2.2 (controller-only change), so the generated kubeconform schemas need no update. ## Validation - `bind-system` renders with the v0.2.3 CRD bundle; `bind-internal` passes `kubeconform` (56/56); pre-commit clean. ## Deploy note On deploy the deterministic operator stops churning the ConfigMap; the config hash stabilizes and the stuck resolver rolling update completes, leaving all three pods Ready on one revision. Reviewed-on: #255 Co-authored-by: Ben Vincent <ben@unkin.net> Co-committed-by: Ben Vincent <ben@unkin.net>
28 lines
979 B
YAML
28 lines
979 B
YAML
---
|
|
# Companion TSIG API. The operator reconciles this into a Deployment, Service,
|
|
# ConfigMap, master-token Secret and namespaced RBAC. vault-plugin-secrets-bind-tsig
|
|
# calls it to create/rotate/delete TSIG keys, which it does by managing
|
|
# BindTSIGKey resources in this namespace (the operator reconciles the material).
|
|
#
|
|
# The master access token Secret (bind-tsig-api-token) is generated by the
|
|
# operator if absent; a VaultStaticSecret may later pre-seed/overwrite it so the
|
|
# token is sourced from Vault rather than generated in-cluster.
|
|
apiVersion: bind.unkin.net/v1alpha1
|
|
kind: BindTSIGAPI
|
|
metadata:
|
|
name: bind-tsig-api
|
|
namespace: bind-internal
|
|
spec:
|
|
image: git.unkin.net/unkin/bind-tsig-api:v0.2.3
|
|
replicas: 1
|
|
port: 8443
|
|
# targetNamespace defaults to this resource's namespace (bind-internal), where
|
|
# the authoritative cluster and its keys live.
|
|
resources:
|
|
requests:
|
|
cpu: 25m
|
|
memory: 64Mi
|
|
limits:
|
|
cpu: 250m
|
|
memory: 128Mi
|