The 1.7.0 release updates to the 5.0.0 version of the fabric8 Kubernetes client. While this should improve the user experience quite nicely, there are a couple of things to be aware of when upgrading from a previous version as detailed below:
Doneableclasses have been removed along with all the involved complexityControllerannotation has been simplified: thecrdNamefield has been removed as that value is
computed from the associated custom resource implementation- Custom Resource implementation classes now need to be annotated with
GroupandVersion
annotations so that they can be identified properly. Optionally, they can also be annotated with
Kind(if the name of the implementation class doesn't match the desired kind) andPluralif
the plural version cannot be automatically computed (or the default computed version doesn't match
your expectations). - The
CustomResourceclass that needs to be extended is now parameterized with spec and status
types, so you can have an empty default implementation that does what you'd expect. If you don't
need a status, usingVoidfor the associated type should work. - Custom Resources that are namespace-scoped need to implement the
Namespacedinterface so that
the client can generate the proper URLs. This means, in particular, thatCustomResource
implementations that do not implementNamespacedare considered cluster-scoped. As a
consequence, theisClusterScopedmethod/field has been removed from the appropriate
classes (Controllerannotation, in particular) as this is now inferred from theCustomResource
type associated with yourController.
Many of these changes might not be immediately apparent but will result in 404 errors when
connecting to the cluster. Please check that the Custom Resource implementations are properly
annotated and that the value corresponds to your CRD manifest. If the namespace appear to be missing
in your request URL, don't forget that namespace-scoped Custom Resources need to implement
the Namescaped interface.