Skip to content

feat(dgraph): add optional PodDisruptionBudget, ServiceMonitor, PrometheusRule, and NetworkPolicy - #146

Open
mlwelles wants to merge 1 commit into
mainfrom
feat-optional-observability
Open

feat(dgraph): add optional PodDisruptionBudget, ServiceMonitor, PrometheusRule, and NetworkPolicy#146
mlwelles wants to merge 1 commit into
mainfrom
feat-optional-observability

Conversation

@mlwelles

Copy link
Copy Markdown

Add four optional, default-off resources: PodDisruptionBudget (alpha and zero), ServiceMonitor (scoped to the ClusterIP Services via the monitor label so headless Services are not double-scraped), PrometheusRule (conservative up/backup alerts), and NetworkPolicy (ingress). All are absent from a stock render; each renders only when its own flag is enabled.

Part of splitting #140 into per-area PRs. The change was built and validated on that branch; the merge of all split PRs reproduces #140's tree byte-for-byte. #140 is being closed as superseded.

…theusRule, and NetworkPolicy

All four resources default off.

- pdb.yaml: alpha/zero PodDisruptionBudgets, default-off to avoid the
  single-replica drain deadlock (minAvailable >= replicaCount blocks
  kubectl drain / cluster-autoscaler eviction indefinitely).
- servicemonitor.yaml: companion to commit 2's headless-Service ports;
  scoped to the ClusterIP Services via the monitor label.
- prometheusrule.yaml: conservative default alerts on stable metrics
  (up, kube_job_status_failed); extraRules for image-specific alerts.
- networkpolicy.yaml: ingress-only, intra-cluster allow plus
  clientPodLabels-gated alpha client access.

ServiceMonitor/PrometheusRule require the Prometheus Operator CRDs;
default-off means a stock install imposes no CRD dependency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant