Repository navigation
Add connection pooling guidance and kube-prometheus-stack monitoring for Kubernetes - #123
Merged
Merged
Conversation
|
@agnesadah3-jpg Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add connection pooling guidance and kube-prometheus-stack monitoring for Kubernetes
What was solved
#68 — Add PgBouncer / connection pooling guidance for the HPA-scaled backend
Add connection-pooling guidance for the HPA-scaled backend so up to 10 replicas don't exhaust Postgres/Supabase connection limits. Document using Supabase's pooler (port 6543) or deploying PgBouncer, and set a per-replica pool size in the k8s manifests and deployment docs.
Addressed:
#69 — Deploy the monitoring stack to Kubernetes
Add Kubernetes-native monitoring for the production cluster: introduce kube-prometheus-stack ServiceMonitors (or k8s service discovery) so Prometheus scrapes backend/frontend instead of static docker-compose targets, convert the existing alert rules into a PrometheusRule CRD, and document installation. Scope is limited to monitoring/ and k8s/ (plus the monitoring install doc).
Addressed:
Changes
docs/DEPLOY-KUBERNETES.md(modify)k8s/backend-deployment.yaml(modify)k8s/monitoring-servicemonitors.yaml(create)docs/MONITORING.md(modify)k8s/configmap.yaml(modify)k8s/prometheus-rule.yaml(create)k8s/secrets.yaml(modify)k8s/kustomization.yaml(modify)Approach
Issues
Closes #68
Closes #69