Re: oc observe quota - double update

Simply ignore status.* and compare old spec.hard.cpu against new spec.hard.cpu. Em 3 de out de 2017 03:46, "Tobias Brunner" escreveu: > Thanks for your answer! > > On 02.10.2017 23:54, Clayton Coleman wrote: > > You'd need to filter that out in your script - this is just how

Re: Private registry authentication - share a secret automatically across all projects.

Hello, I continuous my research, I'm wondering whether I should play with ServiceAccount or edit "default" ServiceAccount for all namespaces ( https://docs.openshift.com/container-platform/3.5/dev_guide/service_accounts.html ). We start with Openshift. I have doubts about the procedure to share

Re: oc observe quota - double update

Thanks for your answer! On 02.10.2017 23:54, Clayton Coleman wrote: > You'd need to filter that out in your script - this is just how the > changes get passed down. Yeah, I had this idea too, but I think that's gonna be tricky as I probably would have to compare older states and so forth. >