/
No matches for kind PodSecurityPolicy
No matches for kind PodSecurityPolicy
Expected behavior
The kubernetes operator for HiveMQ deploys with its default values.yaml
or a modified version thereof.
Observed behavior
Upon deploying, helm returns the following error:
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "hivemq-hivemq-operator" namespace: "default" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first
Reason
In recent kubernetes versions, PodSecurityPolicy has been deprecated. The version to which the operator is being deployed to no longer accepts its use.
Affected Version
kubernetes >= 1.25
Solution / Workaround
Disabling PodSecurityPolicy by setting pspEnabled to
false
in the usedvalues.yaml
and redeploying resolves the issue
global:
rbac:
create: true
pspEnabled: false
Related content
Starting from Kubernetes API version 1.25, PodSecurityPolicy will no longer be served.
Starting from Kubernetes API version 1.25, PodSecurityPolicy will no longer be served.
More like this
Helm Chart installation fails with error "no matches for kind "PodSecurityPolicy" in version "policy/v1beta1""
Helm Chart installation fails with error "no matches for kind "PodSecurityPolicy" in version "policy/v1beta1""
More like this
No HiveMQ pods are spawned
No HiveMQ pods are spawned
More like this
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "swarm-hivemq-swarm" namespace: "swarm" from "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "swarm-hivemq-swarm" namespace: "swarm" from "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
More like this
Kubernetes API v1.22 migration
Kubernetes API v1.22 migration
More like this