[Bug]: The CustomResourceDefinition "poolers.postgresql.cnpg.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes about cloudnative-pg HOT 3 OPEN

@remotejob try a server side apply

k apply -f https://github.com/cloudnative-pg/cloudnative-pg/releases/download/v1.22.3/cnpg-1.22.3.yaml --server-side

from cloudnative-pg.

Thanks. OK

As I understand I can't change the default PORT

postgresql:
parameters:
port: "5431"

The Cluster "cluster-pg" is invalid: spec.postgresql.parameters.port: Invalid value: "5431": Can't set fixed configuration parameter

Anyway Result for install was:

namespace/cnpg-system serverside-applied
customresourcedefinition.apiextensions.k8s.io/backups.postgresql.cnpg.io serverside-applied
customresourcedefinition.apiextensions.k8s.io/clusters.postgresql.cnpg.io serverside-applied
customresourcedefinition.apiextensions.k8s.io/poolers.postgresql.cnpg.io serverside-applied
customresourcedefinition.apiextensions.k8s.io/scheduledbackups.postgresql.cnpg.io serverside-applied
serviceaccount/cnpg-manager serverside-applied
clusterrole.rbac.authorization.k8s.io/cnpg-manager serverside-applied
clusterrolebinding.rbac.authorization.k8s.io/cnpg-manager-rolebinding serverside-applied
configmap/cnpg-default-monitoring serverside-applied
service/cnpg-webhook-service serverside-applied
deployment.apps/cnpg-controller-manager serverside-applied
Apply failed with 3 conflicts: conflicts with "kubectl-client-side-apply" using admissionregistration.k8s.io/v1:

• .webhooks[name="mbackup.cnpg.io"].rules
• .webhooks[name="mcluster.cnpg.io"].rules
• .webhooks[name="mscheduledbackup.cnpg.io"].rules
  Please review the fields above--they currently have other managers. Here
  are the ways you can resolve this warning:

• If you intend to manage all of these fields, please re-run the apply
  command with the --force-conflicts flag.
• If you do not intend to manage all of the fields, please edit your
  manifest to remove references to the fields that should keep their
  current managers.
• You may co-own fields by updating your manifest to match the existing
  value; in this case, you'll become the manager if the other manager(s)
  stop managing the field (remove it from their configuration).
  See https://kubernetes.io/docs/reference/using-api/server-side-apply/#conflicts

So my question: How resolve conflicts or I can continue without resolve ?

from cloudnative-pg.

Can confirm this error happens, specifically through ArgoCD. Server-side apply applies it fine.

from cloudnative-pg.