running kubectl apply --server-side -f manifests/setup get failed message

[ycyxuehan]

kubectl apply --server-side -f manifests/setup output like this: customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com serverside-applied customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com serverside-applied customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com serverside-applied customresourcedefinition.apiextensions.k8s.io/prometheusagents.monitoring.coreos.com serverside-applied customresourcedefinition.apiextensions.k8s.io/scrapeconfigs.monitoring.coreos.com serverside-applied customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com serverside-applied namespace/monitoring serverside-applied Apply failed with 2 conflicts: conflicts with "entry" using apiextensions.k8s.io/v1:

• .metadata.annotations.controller-gen.kubebuilder.io/version
• .spec.versions 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 Apply failed with 2 conflicts: conflicts with "arms-prometheus-operator" using apiextensions.k8s.io/v1:

• .metadata.annotations.controller-gen.kubebuilder.io/version
• .spec.versions 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 Apply failed with 2 conflicts: conflicts with "entry" using apiextensions.k8s.io/v1:

• .metadata.annotations.controller-gen.kubebuilder.io/version
• .spec.versions 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 Apply failed with 2 conflicts: conflicts with "entry" using apiextensions.k8s.io/v1:

• .metadata.annotations.controller-gen.kubebuilder.io/version
• .spec.versions 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