patch-operator

patch-operator copied to clipboard

I have no use for the mutating webhook; how do I go about disabling this feature in helm?

Waidmann

Hi, I try to use yaml for a patch in field patchTemplate with no luck ```apiVersion: redhatcop.redhat.io/v1alpha1 kind: Patch metadata: name: helm-controller-patch namespace: flux-system spec: serviceAccountRef: name: helm-controller patches: helm-controller-patch:...

mfilotto

Hi, I try to use patch operator to add container arguments to a Deployment with no luck.

mfilotto

label / annotationSelector in targetObjectRef ignored

2

We want to patch serviceaccounts with name "default" in all namespaces. When a specific annotation exists, this object should not be patched. I tried using labelSelector or annotationSector, but the...

muellerfabi

enableCertManager to false no working, and no way to inject custom certificates

1

The Helm chart does not work with `enableCertManager` set to `false` in [values.yaml](https://github.com/redhat-cop/patch-operator/blob/main/config/helmchart/values.yaml.tpl): ```yaml ... 44 enableCertManager: false ``` Certificates are logically created only if `enableCertManager` is set to `true`...

leotomas837

Patching objects that do not support watch

3

Hi, I have a patch that seems to be working but on an object that do not support the watch method (ImageStreamTags). As a consequence, I am seeing a lot...

X-dark

ServiceMonitor is created with invalid serverName value

6

Hi, I have installed patch-operator version 0.1.4 through OperatorHub in a namespace named `scale-patch-operator`. I can see that the `serverName` in the `serviceMonitor` is created with an invalid namespace name:...

X-dark

Does patch operator really require cluster-wide permissions?

3

I've configured a ServiceAccount (`patch-operator`) with permissions to read and modify secrets and configmaps in a particular namespace. I have this role: ``` apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: patch-operator...

larsks

patch: add annotation A=1 patch updated to : add annotation A2=2 both annotations exist: A=1 A2=2 how can we cleanup the effects of the first one? is it like [...

shanproofpoint

Non idempotent patch causing infinite reconciliation

13

I faced an issue with a patch which appends items to an array. ``` [ { "op": "add", "path": "/spec/install/spec/deployments/0/spec/template/spec/containers/0/args/-", "value": "--dns01-recursive-nameservers-only" }, { "op": "add", "path": "/spec/install/spec/deployments/0/spec/template/spec/containers/0/args/-", "value": "--dns01-recursive-nameservers=8.8.8.8:53,1.1.1.1:53"...

andreadecorte