You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! We recently upgraded K8s versions (to 1.28). And the operator is giving this error:
1.704997223775299e+09 ERROR druid_operator_handler failed to list [PodDisruptionBudget] due to [no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"] {"name": "druid", "namespace": "druid", "error": "failed to list [PodDisruptionBudget] due to [no matches for kind \"PodDisruptionBudget\" in version \"policy/v1beta1\"]"}
github.com/druid-io/druid-operator/controllers/druid.deleteUnusedResources
/workspace/controllers/druid/handler.go:636
github.com/druid-io/druid-operator/controllers/druid.deployDruidCluster
/workspace/controllers/druid/handler.go:346
github.com/druid-io/druid-operator/controllers/druid.(*DruidReconciler).Reconcile
/workspace/controllers/druid/druid_controller.go:66
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:114
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:311
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:227
From the code, it looks like yall are using v1beta1:
Hi! We recently upgraded K8s versions (to 1.28). And the operator is giving this error:
From the code, it looks like yall are using v1beta1:
druid-operator/controllers/druid/handler.go
Line 1369 in 9cec3f2
But the PDBs now are
policy/v1
Is there anyway to skip the creation of PDBs while this is getting resolved?
The text was updated successfully, but these errors were encountered: