Open Ab-hishek opened 2 years ago
In case someone find this issue: The fix is already merged and will be release with 3.4.0 (?) https://github.com/openebs/cstor-operators/pull/436
I test it. It was supported in v3.4.x
I can confirm that the issue was resolved by using 3.4.0 - 3.3.0 failed and the minute i upgraded the deployments and all reference to the 3.3.0 image to be 3.4.0 - everything worked.
waitting v3.4.0 helm charts, but anyway deploy 3.4.0 now?
No need to wait, https://github.com/openebs/velero-plugin/issues/183
Read that through and see last comments for cstor-operator that works :)
From: will @.> Sent: Thursday, November 17, 2022 3:56:08 AM To: openebs/cstor-operators @.> Cc: Jad Seifeddine @.>; Comment @.> Subject: Re: [openebs/cstor-operators] cStor using the removed APIs in k8s 1.25 requires changes (Issue #435)
waitting v3.4.0 helm charts
— Reply to this email directly, view it on GitHubhttps://github.com/openebs/cstor-operators/issues/435#issuecomment-1317346917, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZR4BBMKYPJSPRVTARGNEDDWIUG2RANCNFSM6AAAAAAQIMSKOU. You are receiving this because you commented.Message ID: @.***>
any plan to release helm chart 3.4.0?
Problem Description
When creating application with cStor provisioned volume(3 replicas), app gets stuck in container creating state.
Environment details: Kubeadm based 4-node(1 master & 3 workers) cluster with K8s 1.25 version:
Each node is having 3 disks attached to it.
Steps followed to create a cStor volume:
3 replicas
mentioned in the StorageClass.healthy
stateDescribe of the application pod:
Describe of CVC:
Logs from one of the pool pods:
How to solve
Upon debugging, found out that cStor operators is using
v1beta1
version ofPodDisruptBudegt
object in its codebase which was deprecated in K8s 1.21 version and is completely removed in K8s 1.25 version.We need upgrade the usage version of
PodDisruptBudegt
to v1 in the codebase to enable cStor to work in K8s 1.25 or later versions