Niklas Ye
6a699d4341
spec.pod (api/v1alpha1/terdutserver_types.go): annotations, nodeSelector,
tolerations, affinity, topologySpreadConstraints, resources, pod and
container securityContext, serviceAccountName, extraEnv/extraEnvFrom,
extraVolumes/extraVolumeMounts, imagePullSecrets, and an optional
disruptionBudget. All direct corev1 passthrough -- no wrapper types buy
anything for any of these, matching how CloudNativePG and the Zalando
postgres-operator both expose the same knobs, and matching this repo's
own SweeperSpec precedent ("wrap only when a round-trip through a
different type buys something"). affinity is pure user-supplied
passthrough, not a toggle-plus-generated-default the way a multi-replica
cluster operator's pod anti-affinity usually is: this operator never
auto-generates one, since spec.replicas above 1 isn't a supported
topology (the sweeper/notifier singleton constraint). Considered and
declined for this round: priorityClassName, pod labels beyond
annotations, and a HorizontalPodAutoscaler -- the last of those would
directly contradict the singleton constraint above.
disruptionBudget is the one field here that isn't a plain PodTemplateSpec
knob: when set, the controller now reconciles a PodDisruptionBudget
selecting the TerdutServer's own pods (new terdutserver_pdb.go); clearing
it deletes any it previously created. New RBAC marker on
poddisruptionbudgets to match.
Driven by a public-release pass: looking past this project's own use case
at what a mature, general-purpose operator CRD exposes here (researched
against Zalando postgres-operator and CloudNativePG specifically), not
just the fields this install happened to need.
Separately, and found while answering a question about exposing
TerdutServer through Istio instead of Gateway API: spec.networking's own
doc comment quietly promised a Gateway API HTTPRoute this operator would
build eventually ("a near-term follow-up, not deferred"). That promise is
wrong for a public release -- an operator managing someone's ingress
mechanism for them is a worse default than not touching it at all, and a
surprise HTTPRoute appearing once that follow-up eventually landed would
have been exactly backwards for an Istio (or plain-Ingress, or
intentionally-unexposed) install. Made the non-goal explicit and
permanent instead (DESIGN.md §1), removed the dead `gatewayListener`
field it was the only consumer of (zero runtime call sites anywhere --
setting it already had no effect, so this is a schema cleanup, not a
behavior change), and corrected ROADMAP.md's framing. hostname/servicePort
stay: both are live (TERDUT_PUBLIC_URL, container/Service port), this
operator just never acts on hostname for exposure. Added
examples/networking (Gateway API HTTPRoute, Istio VirtualService) showing
how to expose the plain ClusterIP Service the operator already creates --
outside the operator itself, as illustrations, not as something
examples/demo applies automatically.
No new terdut-server version requirement: both changes are CRD/controller-
only, nothing about the API this operator's bootstrap flow depends on
changed.
43 lines
1.3 KiB
YAML
43 lines
1.3 KiB
YAML
apiVersion: terdut.ryuvia.com/v1alpha1
|
|
kind: TerdutServer
|
|
metadata:
|
|
labels:
|
|
app.kubernetes.io/name: terdut-operator
|
|
app.kubernetes.io/managed-by: kustomize
|
|
name: terdutserver-sample
|
|
spec:
|
|
image:
|
|
repository: git.ryuvia.com/niklas/terdut-server
|
|
tag: v0.20.0
|
|
replicas: 1
|
|
networking:
|
|
hostname: terdut.example.com
|
|
servicePort: 8080
|
|
# Bring-your-own DSN (simplest path, no external CRD dependency). For the
|
|
# Zalando postgres-operator path instead, use:
|
|
# database:
|
|
# postgresClusterRef:
|
|
# name: terdut-postgres
|
|
database:
|
|
dsn: "postgres://terdut@terdut-postgres:5432/terdut?sslmode=require"
|
|
passwordSecretRef:
|
|
name: terdut-postgres-password
|
|
key: password
|
|
sweeper:
|
|
staleAfter: 6h
|
|
archiveAfter: 168h
|
|
deadman:
|
|
matchers: "alertname=Watchdog"
|
|
timeout: 15m
|
|
severity: critical
|
|
passwordLogin: true
|
|
# Pod-level customization, all optional -- see PodSpec in
|
|
# api/v1alpha1/terdutserver_types.go for the full shape (tolerations,
|
|
# affinity, topologySpreadConstraints, securityContext,
|
|
# serviceAccountName, extraEnv/extraVolumes, imagePullSecrets,
|
|
# disruptionBudget, ...). Example:
|
|
# pod:
|
|
# resources:
|
|
# requests: {cpu: 100m, memory: 128Mi}
|
|
# limits: {memory: 256Mi}
|