Steven Hawkins

> Maybe @shawkins has some idea about what might be happening. From the client side we added a ~5-10 minute timeout to websockets (included as a timeout parameter and enforced...

> @shawkins Have to mention that we also see this behavior at https://github.com/fabric8io/kubernetes-client/issues/5599, could it be what fails the upload? Does the upload take longer than 5 to 10 minutes?...

> @shawkins no the upload is a of a small file and ends after less then second.. It sounds like what you are describing is that shortly after the websocket...

> Now that createOrReplace will be deprecated, it will be frustrating and obviously not smooth to migrate to serverSideApply, as CREATE/POST operation is not yet managed. I don't follow what...

> It really means there is no handling of unexisting resources. What kubernetes server version are you hitting?

> It's the Fabric8 KubernetesServer, embedded during JUnit tests. The mock server does not support server side apply in crud mode. It requies the use of expectations, or an actual...

> Ok so we could rename my request to support serverSideApply in the mock server ;) Unfortunately that is unlikely to happen. There's quite a lot of logic that support...

> In order to ease transitioning, we might want to include at least the support for the initial create operation of server side apply At least for usage with things...

> Please don't neglect the immense value that mockServer provides. See this comment https://github.com/fabric8io/kubernetes-client/issues/5337#issuecomment-1642683157 - unfortunately the crud mock support will always be incomplete. It leads users down a path...

@manusa @rohanKanojia Marc is proposing above to have the crud mock logic support the initial create with server side apply. The other things we can consider are: - simply changing...