Zoë Sam Candy

It seems the operator takes a `WATCH_NAMESPACE` variable so it may be designed to run in a single namespace. It seems we need to deploy one operator per namespace but...

I have the same issue, I use `global.infraConfigName` and `global.infraSecretName` to use a `ConfigMap` and a `Secret` I manage myself but installing and upgrading with Helm erase my `ConfigMap` and...

Yes, it was supported on edge stack 1.x (in the free version) but when the 2.x serie came out, this feature was not available anymore for free (and not on...

I confirm I have the same bug in `0.9` but not in `0.8`.

I'm interested in this feature but I found a workaround for my use case (a push replication): I just tell Harbor it's a Docker Registry (not docker Hub). I use...

The question already go an answer in [august 2022](https://github.com/spotahome/redis-operator/issues/422#issuecomment-1232199585) and even in [septembre 2021](https://github.com/spotahome/redis-operator/issues/315#issuecomment-920996734). Maybe Spotahome is using he operator and it's working for them so they don't dedicate time/resources...

I had the same error, turned out that the `Deployment` manifests was invalid (I had `strategy` set to `Recreate` directly instead of `strategy.type: Recreate`). It seems your deployment's `.spec.template.spec.imagePullSecrets` is...

Just for your information (I'm not a maintainer or anything but just interested in this feature), there is the pull request https://github.com/argoproj/argo-cd/pull/11821 but it's still a draft (base on the...

I don't know if I should open a new issue for this but SBOM in the CycloneDX format and uploaded by cosign in Harbor are not used for vulnerability scanning....

@cindymullins-dw I just tried to run `telepresence quit -s` and run `telepresence connect --manager-namespace telepresence` again but I had the exact same issue. As you see in the kubeconfig file...