ctml91
ctml91
@v1k0d3n when I deployed cilium via OLM on OpenShift (baremetal) and I had to manually add the service accounts from cilium to the privileged SCC, but the namespace was flooded...
/reopen @giuseppe @vrothberg
Thanks for your feedback @xing-yang ! Completely understand there might be some limitations in the design of quotas and/or volumesnapshots. Unfortunately it's above be level of understanding and I am...
Same issue here, too bad as I was hoping to use nextcloud for photo synchronization with google photos. Most of my photos aren't located in an album.
Tried to work around the issue by using a condition `MustNotExist` for `nodeName` in the pod spec to only apply when it does not exist (ie. pod is not scheduled...
> Interesting. I'm guessing this is for newly defined mutators? Given the pod would have already had the fields set if it had been created beneath the mutator? Yes that's...
> Yeah, a new field in the mutation CRD sounds right. > > @ctml91 one concern I have is that only applying the mutation on "create" would cause the same...
> > If field owner is set and that triggers the deletion issue, we'd probably need to do something that extracts the value from the original field and re-adds it,...
> What do you think about something that says: "on CREATE, use the provided value, on UPDATE use the value from oldObject"? Sounds reasonable, as long as it's not an...