# Percona xtradb cluster 1.15 readiness probe failure in kubernetes with kubeadm

**URL:** <https://forums.percona.com/t/percona-xtradb-cluster-1-15-readiness-probe-failure-in-kubernetes-with-kubeadm/35271>\
**Category:** MySQL & MariaDB\
**Created:** [November 26, 2024, 8:17am UTC](https://forums.percona.com/t/percona-xtradb-cluster-1-15-readiness-probe-failure-in-kubernetes-with-kubeadm/35271 "2024-11-26T08:17:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shihab\_Uddin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/shihab_uddin/32/18461_2.png) [@Shihab\_Uddin](https://forums.percona.com/u/Shihab_Uddin)\
**Post date:** [November 26, 2024, 8:17am UTC](https://forums.percona.com/t/percona-xtradb-cluster-1-15-readiness-probe-failure-in-kubernetes-with-kubeadm/35271/1 "2024-11-26T08:17:34Z")

</div>

I deployed with the following yaml and it keeps in readiness probe failed state in k8s with kubeadm.

```auto
apiVersion: pxc.percona.com/v1
kind: PerconaXtraDBCluster
metadata:
  name: minimal-cluster1
  namespace: database
spec:
  crVersion: 1.15.1
  secretsName: cluster1-secrets
  unsafeFlags:
    tls: true
    pxcSize: true
    proxySize: true
  upgradeOptions:
    apply: disabled
    schedule: "0 4 * * *"
  tls:
    enabled: false
  pxc:
    size: 2
    image: percona/percona-xtradb-cluster:8.0.36-28.1
    volumeSpec:
      persistentVolumeClaim:
        storageClassName: nfs-client
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 6G
    # resources:
    # limits:
    # memory: 2Gi
    # requests:
    # memory: 2Gi
    # tolerations:
    # - key: "node.kubernetes.io/not-ready"
    # operator: "Exists"
    # effect: "NoExecute"
    # - key: "node.kubernetes.io/unreachable"
    # operator: "Exists"
    # effect: "NoExecute"             
  haproxy:
    enabled: false
    size: 1
    image: percona/haproxy:2.8.5
    exposeReplicas:
      enabled: true
    exposePrimary:
      enabled: true  
  logcollector:
    enabled: true
    image: percona/percona-xtradb-cluster-operator:1.15.1-logcollector-fluentbit3.1.4
  proxysql:
    enabled: true
    size: 1
    image: percona/proxysql2:2.5.5
    imagePullPolicy: Always
    volumeSpec:
      persistentVolumeClaim:
        storageClassName: nfs-client
        accessModes: 
          - ReadWriteOnce
        resources:
          requests:
            storage: 6G  
    gracePeriod: 30   
    expose:
      enabled: true          

```

Please tell me what change can fix this issue?

---

<div class="post-metadata">

**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\
**Post date:** [November 27, 2024, 5:47am UTC](https://forums.percona.com/t/percona-xtradb-cluster-1-15-readiness-probe-failure-in-kubernetes-with-kubeadm/35271/2 "2024-11-27T05:47:45Z")

</div>

Hello @Shihab_Uddin

I see you are starting 2 pxc pods only, which should be fine as you set unsafeFlags.pxcSize: true

It would be helpful to suggest on this issue further if you share more details like on the issue like ,

Where do you see the error, and What exact error are you getting?  
Which document are you following for the installation of the cluster?

Ref:

> **[Percona Operator for MySQL - Generic Kubernetes installation](https://docs.percona.com/percona-operator-for-mysql/pxc/kubernetes.html)**
>
> First of all, clone the percona-xtradb-cluster-operator repository:

---

<div class="post-metadata">

**Author:** ![Shihab\_Uddin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/shihab_uddin/32/18461_2.png) [@Shihab\_Uddin](https://forums.percona.com/u/Shihab_Uddin)\
**Post date:** [December 30, 2024, 7:04am UTC](https://forums.percona.com/t/percona-xtradb-cluster-1-15-readiness-probe-failure-in-kubernetes-with-kubeadm/35271/3 "2024-12-30T07:04:46Z")

</div>

Thank you. @lalit.choudhary Finally fixed the issue, it occurred because of using nfs subdir helm chart as nfs client for pvc. Fixed it using longhorn in kubeadm environment