Beni Cherniavsky-Paskin

@DocX `certificate-authority` fix released in gem version 4.9.3 (together with other `Config` security fixes — see #554 and #555, recommend updating ASAP!) Keeping issue open for `certificate-authority-data`.

@rhysm @benlangfeld you know more than me about OIDC, could you review? @nov Does this deserve any additions to README? Or is it "if you've set up a JWK cache...

OK, I don't know how to review this myself, but I shouldn't have blocked this either. Superficially, makes sense :+1: [I'm just getting too little time for kubeclient, so trying...

@nov friendly ping — the only thing blocking merge is I don't know how to explain this change in CHANGELOG.md, please add an entry there :pray: FYI, #606 is looking...

Thanks. That's not ruby-dependent, it's some TLS certs that expired again (used by tests only, never by kubeclient itself) => regenerated now on both `v4.y` branch (from where we currently...

(Yes, repo was moved under manageiq org when Alissa `@abonas` was leaving Red Hat so we don't depend on her for future maintainer handoffs, and in hope Adam @agrare would...

BTW I notice `with_worker` does this: `sleep(0.03) # wait for worker to watch` which (at least in theory) is not guaranteed. And one test does `sleep(0.02) # wait for watch...

Thanks! Reopening to decide if I can bump dependencies (maybe only in 5.0) to guarantee 2.7 compatibility...

I haven't managed to reproduce yet on http 3.3.0, but your analysis is right. Ruby 2.7 pre-release experimented with a more radical change making Symbol#to_s return frozen strings but that...

hmm, 4.0 dropped ruby 2.2 support, which is again ancient EOL but now I feel worse about dropping it in kubeclient before 5.0 :thinking: :shrug: