Steven Hawkins

There is also io.fabric8.openshift.api.model.runtime.RawExtension in the mix, which matches what was mentioned above about a specific Raw type. Here's a refined proposal: - Change the mapping of `RawExtension`/`Map` to just...

With #4289 committed the only follow on I can think to consider is if RawExtension is added as a buildable target (either to all or selectively to classes using a...

For fabric8 6 CustomResource won't even be required in kubernetes-model - all of the entry points that dealt with it have been deprecated and can be removed.

@metacosm yes, I'd like to consider that more broadly #3645

Splitting off a new issue now that the pr has been resolved. Taking a step back, my thought with the ReducedStateItemStore, is that application assumes the responsibility for maintaining a...

Another OSGI concern is the location of the Managed clients - they are in the -client dependencies, I'm not sure if they need to be in -api.

The problem is the replace operation. It is not a substitute for apply / patch. Instead of createOrReplace you can use the new support for server side apply - https://github.com/fabric8io/kubernetes-client/blob/master/doc/CHEATSHEET.md#server-side-apply...

There isn't a top level operation on a resource list for patching, but 6.0 has added the resources method to help process composite operations: ``` client.load(resource.getInputStream()).resources().forEach(r -> r.patch(PatchContext.of(PatchType.SERVER_SIDE_APPLY))); ```

> FYI I'm using 6.0 is where the method resources method was added, and support for PatchType.SERVER_SIDE_APPLY.

> If you perform mvn spotless:apply, only affected files should change. I saw the same behavior - files that we're not modified locally, in the index, nor in a commit...