Michael H

> Hello @erdrix , We are evaluating nifikop and we are having this issue. We are willing to contribute to solve this. > > I see there is an open...

`tolerations` go under a specific `nodeConfigGroup`. So if you're using `default_group` for each of your nodes, it'd look like this: ```yaml spec: nodeConfigGroups: default_group: nodeConfigGroups: default_group: tolerations: - key: taint.key...

If you want to pin the NiFi pods to dedicated nodes which you've tainted, you must specify both a `nodeSelector`/`nodeAffinity` and the `toleration`. Specifying only the tolerations just tells k8s...

I've fixed the build on this PR as i mimicked changes seen in fe69e9eddd7e10ed7cc8ab6aa8d9b1c1ea73d133

The other alternative is to just use the docker client for all registry interactions, but that may not be advised if the goal is to support all OCI images.

LGTM. Would love to have this too, selfishly for the logo query parameter :)

+1

There are many operators that behave this way including `Koperator` and `NiFiKop`. This behavior should at least be configurable through an `Application`/`ApplicationSet`.

We also see this same problem immediately after upgrading. Identical scenario. Rolling back to 2.8.2 makes the chart repos happy again. This prevents us from upgrading to v2.8.3 since it...

I'm also seeing this with one of our clusters. I'd upgraded from rook 1.12.8 to 1.13.3 and ceph 17.2.6 to 18.2.1. Oddly, i'd upgraded 2 other clusters with the same...