Steven Hawkins

Proactive or failure refreshing of the credential regardless of the source has been added to both refresh interceptors. This will hopefully be formalized a bit more with the work being...

Removing the never stale. There could still be follow-up on 1, 2 in https://github.com/fabric8io/kubernetes-client/issues/2112#issuecomment-1010183636 but the basic support for expiration is ensured with #4802. That is we'll always fully refresh...

@iocanel is this related to the changes in https://github.com/sundrio/sundrio/issues/374 and https://github.com/sundrio/sundrio/issues/350 or does there still need to be an explicit declaration that PodSpec is Buildable?

Let's rebase and address the review comments with this after #4702

@manusa some next steps: - refine the KubernetesSerialization interface and where that would be associated with the client. - ideally allow for the configuration/setting of the objectmappers to the instance...

Marking as resolved by #4662 - we'll make further adjustments to the KubernetesSerialization from there.

Removed the never stale - it doesn't seem like an okhttp4 based option is in the cards to be distributed with the core project. It's easy enough for a user...

@mattnelson @manusa the cve listed above applies just to the project, not to its usage in the fabric8 client - which uses its own managed version of the jackson dependencies....

@dmlloyd it seems like there isn't a great way to do this. The comment https://github.com/smallrye/smallrye-config/blob/889fa9ffb91cd44d3d4b77e82b39c9cb81fc7750/implementation/src/main/java/io/smallrye/config/ExpressionConfigSourceInterceptor.java#L94 seems to make it clear that the more general handling of escape will not happen,...

> The existing workaround is already concerning IMO. What if it hits \$$? or \\$ or \\\$ or \\\$$... etc. I don't think all of these cases are well-defined in...