Hagai Barel
Hagai Barel
Seems like the situation is even more tricky than I originally described, when the operator container starts it overrides the `.spec.selector` field to `name=jaeger-operator` for the `metric` service. Since that...
@tianhe-oi I don't see any news on this. No, removing the `app.kubernetes.io/instance` from the selector label won't help, the operator overrides it to `name=jaeger-operator` which is missing from the pod...
Interesting idea. I have a process in place that adds the missing label to the pod template in the deployment on each install/upgrade
Looks like it was migrated to `ghcr` so you can now `docker pull ghcr.io/linkedin/burrow/burrow:v1.3.6` even without authentication, although I don't see there's a process in place to build or publish...
This might not be relevant, but I've noticed that when using SSA, setting `pulumi.IgnoreChanges` on a resource has no affect. I'm trying to come up with a simple reproduce steps...
I like the idea, but would prefer to avoid breaking chanages if possible. We can take a differnet approch here - leave the `--set` flag as is, and intoduce a...
Have fun, don't forget to add relevant sections in the docs explaining the mechanism
Can confirm, seeing the same behavior on kubernetes running on plain ec2 (not `eks`) hosts
Hmm... the curator chart doesn't even have a `service.yaml` file which makes this error a mystery to me. I am curios what steps you took that caused this error
This would potentially break exiting installations that rely on this values being set by default