Hi folks, We are running GrowthBook on our Kubern...
# ask-questions
f
Hi folks, We are running GrowthBook on our Kubernetes cluster and need to define some liveness and readiness probes. I was thinking they could be pretty simple httpGet probes, • liveness - path is / and port is 3100 • readiness - path is /healthcheck and port is 3100 Does this seem correct?
f
ya, there are two services you want to check, the app, and the backend. (if you care about the front end app)
f
Don't much care about the frontend. But it's packaged in the container with the backend isn't it. So a single healcheck should be pretty good right?
Copy code
apiVersion: v1
kind: Service
metadata:
  annotations:
    <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: growthbook
    <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: configuration-management
  creationTimestamp: "2025-02-19T14:33:04Z"
  labels:
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: growthbook
    <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: growthbook
    <http://app.kubernetes.io/version|app.kubernetes.io/version>: 0.1.0
    <http://helm.sh/chart|helm.sh/chart>: nemlig-service-1.33.3
  name: growthbook
  namespace: configuration-management
  resourceVersion: "636806949"
  uid: 27d9cf10-c5d3-4f34-9e8b-5806ea93b83b
spec:
  clusterIP: 10.241.2.250
  clusterIPs:
  - 10.241.2.250
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: frontend
    port: 3000
    protocol: TCP
    targetPort: frontend
  - name: backend
    port: 3100
    protocol: TCP
    targetPort: backend
  selector:
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: growthbook
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: growthbook
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}
f
should be
1