manusa on master
test: document SerialExecutor e… (compare)
manusa on master
fix #3625: updating the default… fix #3625: committing the modif… fix #3625: test corrections rel… (compare)
probably the most desirable thing is to generate POJOs which would extend CustomResource so I don't have to load yaml CRDs in my code (as that's deprecated and requires me to actually get hold of those descriptors).
I think we can do it by providing a manual
ApicurioRegistry
andApicurioRegistryList
which will extend CustomResource
Loading the yaml descriptor seems cleaner in that case. Writing the classes doesn't really seem as a good option and thus I think this method shouldn't be deprecated -- the majority of CR/Ds one is going to encounter are not going to be written in java.
@rohanKanojia
btw did you ever see this? Without touching my cluster the client starting spitting this at me
Caused by: io.fabric8.kubernetes.client.WatcherException: too old resource version: 48308901 (48321468)
5.2.1 client
Hi Guys!
I see io.fabric8.kubernetes.client.dsl.internal.core.v1.PodTemplateOperationsImpl has been removed in v5.7.0 and I don't see any info relating to this removal in changelog .
is io.fabric8.kubernetes.client.dsl.internal.HasMetadataOperationsImpl replacement for above class ?
my previous usage (v5.4.0):
new PodTemplateOperationsImpl(
k8sClient.getHttpClient(),
k8sClient.getConfiguration());
current usage(v5.7.0):
new HasMetadataOperationsImpl<>(
k8sClient.getHttpClient(),
k8sClient.getConfiguration(), ResourceDefinitionContext.fromResourceType(PodTemplate.class), PodTemplate.class, PodTemplateList.class);