Bump bind-operator to v0.2.1 (secondary replication fix)

v0.2.1 fixes authoritative secondary replication, which never worked:
the master REFUSED the catalog AXFR because secondaries presented no TSIG
key, member zones had no allow-transfer, and secondaries chased the
primary's ephemeral pod IP.

- Bump the operator image and the pulled CRD bundle to v0.2.1.
- Bump the bind-tsig-api image to v0.2.1.

CRDs are unchanged from v0.2.0, so the generated schemas need no update.

apps/base/bind-internal/tsig-api/tsig-api.yaml

@@ -13,7 +13,7 @@ metadata:
   name: bind-tsig-api
   namespace: bind-internal
 spec:
-  image: git.unkin.net/unkin/bind-tsig-api:v0.2.0
+  image: git.unkin.net/unkin/bind-tsig-api:v0.2.1
   replicas: 1
   port: 8443
   # targetNamespace defaults to this resource's namespace (bind-internal), where

apps/base/bind-system/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         runAsNonRoot: true
       containers:
         - name: operator
-          image: git.unkin.net/unkin/bind-operator:v0.2.0
+          image: git.unkin.net/unkin/bind-operator:v0.2.1
           args:
             - --metrics-bind-address=:8080
             - --health-probe-bind-address=:8081

apps/base/bind-system/kustomization.yaml

@@ -6,6 +6,6 @@ resources:
   - namespace.yaml
   # CRDs are pulled from the bind-operator repo at the matching tag rather than
   # vendored here, so they never drift from the operator.
-  - https://git.unkin.net/unkin/bind-operator/raw/tag/v0.2.0/config/crd/install.yaml
+  - https://git.unkin.net/unkin/bind-operator/raw/tag/v0.2.1/config/crd/install.yaml
   - rbac.yaml
   - deployment.yaml