After the upgrade it looks like the client is generating incorrect K8s API requests 😬 (namespace is missing from URL)
2021-01-15 18:26:35,385 WARN [io.fab.kub.cli.int.VersionUsageUtils] (EventHandler-io.javaoperatorsdk.sample.memcached.MemcachedController_ClientProxy) The client is using resource type 'memcacheds' with unstable version 'v1alpha1'
2021-01-15 18:26:35,584 ERROR [io.jav.ope.pro.EventDispatcher] (EventHandler-io.javaoperatorsdk.sample.memcached.MemcachedController_ClientProxy) Error during event processing ExecutionScope{events=[CustomResourceEvent{action=ADDED, resource=[ name=memcached-sample, kind=Memcached, apiVersion=cache.example.com/v1alpha1 ,resourceVersion=114585747, markedForDeletion: false ]}], customResource uid: a51c4eab-f566-412d-a65d-7cbacf8b951c, version: 114585747} failed.: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PUT at: https://35.205.211.77/apis/cache.example.com/v1alpha1/memcacheds/memcached-sample. Message: 404 page not found
.
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:570)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:509)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:474)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:435)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleReplace(OperationSupport.java:286)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleReplace(OperationSupport.java:267)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleReplace(BaseOperation.java:876)
at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.lambda$replace$0(HasMetadataOperation.java:75)
at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.replace(HasMetadataOperation.java:80)
at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.replace(HasMetadataOperation.java:30)
at io.javaoperatorsdk.operator.processing.EventDispatcher$CustomResourceFacade.replaceWithLock(EventDispatcher.java:213)
at io.javaoperatorsdk.operator.processing.EventDispatcher.replace(EventDispatcher.java:177)
at io.javaoperatorsdk.operator.processing.EventDispatcher.updateCustomResourceWithFinalizer(EventDispatcher.java:154)
at io.javaoperatorsdk.operator.processing.EventDispatcher.handleCreateOrUpdate(EventDispatcher.java:95)
at io.javaoperatorsdk.operator.processing.EventDispatcher.handleDispatch(EventDispatcher.java:82)
at io.javaoperatorsdk.operator.processing.EventDispatcher.handleExecution(EventDispatcher.java:48)
at io.javaoperatorsdk.operator.processing.ExecutionConsumer.run(ExecutionConsumer.java:25)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
@adam-sandor CR need to be marked as Namespaced if they are supposed to deployed in namespaces as opposed to cluster-wide. I've made the change and I will document it in the SDK README as well.
After the upgrade it looks like the client is generating incorrect K8s API requests 😬 (namespace is missing from URL)