Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Chart does not work in Kubernetes 1.25. PodDisruptionBudget v1beta is _removed_ #620

Open
dhinojosa opened this issue Sep 22, 2022 · 15 comments · May be fixed by #629
Open

Chart does not work in Kubernetes 1.25. PodDisruptionBudget v1beta is _removed_ #620

dhinojosa opened this issue Sep 22, 2022 · 15 comments · May be fixed by #629

Comments

@dhinojosa
Copy link

The chart no longer works in 1.25
The chart should use Helm's Capabilities. object to determine the version of Kubernetes and make the right PodDisruptionBudget. The new reference is here: https://kubernetes.io/docs/tasks/run-application/configure-pdb/

I suspect this is what the new one should look like.

apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: confluent-oss-cp-zookeeper-pdb
spec:
  minAvailable: 2
  selector:
    matchLabels:
      app: cp-zookeeper
@markmixson
Copy link

markmixson commented Sep 22, 2022

Same issue here - version 0.6.x has the same behavior with k8s 1.25 and minikube. Downgrading to 1.24.1 fixes the problem.

@aseksenali
Copy link

Same issue on microk8s and k8s v. 1.25.2

@vancwo
Copy link

vancwo commented Oct 31, 2022

Also having an issue related to this on Azure Kubernetes Service v1.23.8. ArgoCD (v2.5.0-rc2) returns an error on sync: ComparisonError: error calculating structured merge diff: error calculating diff: error while running updater.Apply: converting (v1beta1.PodDisruptionBudget) to (v1.PodDisruptionBudget): unknown conversion

@laran
Copy link

laran commented Nov 10, 2022

Same here

@leewoobin789
Copy link

PodDisruptionBudget of beta version is unavailable from 1.25 on. please replace it with policy/v1

ymoreiratiti added a commit to ymoreiratiti/cp-helm-charts that referenced this issue Nov 16, 2022
@ymoreiratiti ymoreiratiti linked a pull request Nov 16, 2022 that will close this issue
@ymoreiratiti
Copy link

Same problem here. @leewoobin789 solution worked fine for me

  1. Cloned the repo locally
  2. Edited charts/cp-zookeeper/templates/poddisruptionbudget.yaml and replaced policy/v1beta to policy/v1
  3. Install helm using the local repo

@danielloader
Copy link

This problem is going to get worse as the cloud clusters versions keep moving forwards, it's now a problem in EKS now 1.25 is out.

@ymoreiratiti
Copy link

Do we have some news about this issue?

@danielloader
Copy link

This problem is going to get worse as the cloud clusters versions keep moving forwards, it's now a problem in EKS now 1.25 is out.

To reply to myself we moved to 1.26 today 😅

@leewoobin789
Copy link

leewoobin789 commented Apr 18, 2023

I don't think that confluent will ever care about this chart, since they have a commercial operator (CFK). To those who needs this type of chart for any purpose, I recommend you to use either CFK or Strimzi. I actually hoped that confluent defines this repository as deprecated, since there is no release since 2020.

@yoda
Copy link

yoda commented Jun 29, 2023

Deleting the history for the chart from the secrets seems to fix it.

@malibcia
Copy link

Is there any change this will be fixed in the near future?

@OneCricketeer
Copy link

OneCricketeer commented Aug 1, 2023

hoped that confluent defines this repository as deprecated

It is, and they did (#638).

This is how you should be using Helm now

@RodionXedin
Copy link

hoped that confluent defines this repository as deprecated

It is, and they did (#638).

This is how you should be using Helm now
Colleagues,

As of this day the issue still persists.

https://packages.confluent.io/helm is no longer available
(/helm has been removed)

CFK 2.7.1 on AKS 1.26.6 giving PodDistributionBudget errors since v1beta1 is not available.

As of 2023-10-13 helm charts & CFK from official examples seem to be not working, which is really worrying since those are basically stopping anyone from deploying confluent platform to K8s 1.25+ without hacks which would be prohibited in a prod environment.

Any expectation on when Confluent would address that ?

@OneCricketeer
Copy link

I'm not sure any Confluent employee watches this repo anymore

If the CFK instructions are broken, please contact support directly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.