Releases: fabric8io/kubernetes-client
Releases · fabric8io/kubernetes-client
4.13.2 (2021-02-05)
Bugs
- Fix #2715: CVE-2021-20218 vulnerable to a path traversal leading to integrity and availability compromise
5.0.1 (2021-01-27)
Bugs
- Fix #2687: RawCustomResourceOperationsImpl ignores config
- Fix #2612: add support for checking latest kubeconfig in Interceptor
Improvements
- Fix #2723: Dependency cleanup
- Remove javax.annotation-api
- Remove jaxb-api
- Remove jacson-module-jaxb-annotations
- Fix #2744: Automatically instantiates spec and status fields on
CustomResource
when possible.
initSpec
andinitStatus
methods are also provided to allow for overriding of the default implementation.
Dependency Upgrade
- Fix #2723: Upgrade sundrio.version to 0.24.1
4.13.1 (2021-01-20)
5.0.0 (2020-12-30)
Bugs
- Fix #2695: fromCustomResourceType should be of type
CustomResource
5.0.0-beta-1 (2020-12-21)
Bugs
- Fix #2671: Reliability improvements to watchers
- Fix #2592: ConcurrentModificationException in CRUD KubernetesMockServer
- Fix #2519: Generated schemas contains a valid meta-schema URI reference (
http://json-schema.org/draft-05/schema#
) - Fix #2631: Handle null values when getting current context on OIDC interceptors
- Fix #2510 : Yaml containing aliases rejected due to FasterXML bug
- Fix #2651: SharedInformers should ignore resync on zero resyncPeriod
- Fix #2656: Binding operations can be instantiated
Improvements
- Fix #2676: Allow specifying PropagationPolicy when using deleteExisting
- Fix #2678: Adds a convenience method for referring to Cache keys by namespace and name rather than item
- Fix #2665: CustomResourceDefinitionContext.fromCrd support for v1 CustomResourceDefinition
- Fix #2642: Update kubernetes-examples to use apps/v1 Deployment rather than extensions/v1beta1
New Features
- Fix #2611: Support for Custom Resource and Custom Resource Definitions has been improved
- New annotations have been introduced for users to specify group, version, singular and plural
properties forCustomResource
instances CustomResource
instances must now be annotated with@ApiVersion
and@ApiGroup
so that the
associated information can be automatically computedHasMetadata
provides default implementations forgetApiVersion
andgetKind
based on the
presence (or not) of annotations on the target class- Static methods have been introduced on
HasMetadata
andCustomResource
to encapsulate the
logic used to resolveKind
,ApiVersion
,Group
,Version
,Plural
,Singular
andCRD Name
properties - New
v1CRDFromCustomResourceType
andv1beta1CRDFromCustomResourceType
methods have been
introduced onCustomResourceDefinitionContext
to initialize aCustomResourceDefinitionBuilder
with the information provided by a specificCustomResource
implementation, making it much
easier to create CRDs if you already have defined your custom resource type CustomResource
is now parameterized by the spec and status types that it uses which further
removes boiler plate
- New annotations have been introduced for users to specify group, version, singular and plural
- Rename
@ApiVersion
and@ApiGroup
to simply@Version
and@Group
, respectively. This was done
to unify annotations and also remove potential confusion between values provided to@ApiVersion
and what is returned byHasMetadata#getApiVersion
5.0.0-alpha-3 (2020-12-10)
Bugs
- Fix #2519: Generated schemas contains a valid meta-schema URI reference (
http://json-schema.org/draft-05/schema#
) - Fix #2628: add
isFinalizerValid
to encapsulate validation logic - Fix #2631: Handle null values when getting current context on OIDC interceptors
- Fix #2610: Remove deprecated module kubernetes-model-generator/model-generator-app
Improvements
- Fix #2628: Add
isFinalizerValid
method onHasMetadata
to encapsulate validation logic - Fix #2640: Edit method accepts Visitors
Dependency Upgrade
- Fix #2636: Upgrade sundrio.version to 0.23.0
5.0.0-alpha-2 (2020-11-24)
Improvements
- Fix #2614: Watcher.onClose has dedicated WatcherException as parameter.
5.0.0-alpha-1 (2020-11-18)
4.13.0 (2020-11-10)
Bugs
- Fix #2517: Replace does not work in CRUD mockwebserver
- Fix #2537: Checking for Readiness of DeploymentConfig
- Fix #2300: Remove job extensions/v1beta1 from backward compatibiliy interceptor
- Fix #2514: SharedIndexInformer watches only pods of its own namespace when run in the cluster
Improvements
- Fix #2507: Add a test for creating a Job with generateName
- Fix #2509: Reversed order + Add Kubernetes 1.16.0 + OpenShift 4.5.14 to Compatibility matrix
- Add cache in github actions for integration tests
Dependency Upgrade
- Fix #2513: Update Kubernetes Model to v1.19.1
New Features
- Fix #2531: Allow setting the maximum concurrent requests via system property / environment variable
- Fix #2534: Tekton model based on Tekton Pipeline 0.17.0
- Fix #2574: Add support for Condition type
Note: Breaking changes in the API
-
Tekton Pipeline v1beta1 sidecars field from a task step is now a list of
io.fabric8.tekton.pipeline.v1beta1.Sidecar
instead of a list ofio.fabric8.tekton.pipeline.v1beta1.Step
-
NetworkPolicy
moved toio.fabric8.kubernetes.api.model.networking.v1.NetworkPolicy
from
io.fabric8.kubernetes.api.model.networking.NetworkPolicy
-
Fix #2557: add missing
OpenShiftReadiness.isReadinessApplicable
4.12.0 (2020-10-02)
Bugs
- Fix #2442: Wrong resource kind in
ProjectRequestHandler
causes ClassCastException when handling Project resources. - Fix #2467: OpenShiftClient cannot replace existing resource with API version =! v1
- Fix #2458: Creating new instance of the DefaultKubernetesClient is hanging
- Fix #2474: Config.fromKubeconfig throws NullPointerException
- Fix #2399: Cannot change the type of the Service from ClusterIP to ExternalName
- Fix #2479: KuberentesDeserializer works on OSGi runtime environments
- Fix #2488: Unable to derive module descriptors for kubernetes-model jars
Improvements
- Enable user to select custom address and port for KubernetesMockServer
- Fix #2473: Removed unused ValidationMessages.properties
- Fix #2408: Add documentation for Pod log options
- Fix #2141: Decouple OpenShift Model from Kubernetes Client
- Fix #2452: Make Readiness.isReady publicly available from a wrapper method in KubernetesResourceUtil
Dependency Upgrade
- Bump Knative Serving to v0.17.2 & Knative Eventing to v0.17.3
New Features
- Fix #2340: Adding support for Knative Eventing Contrib
- Fix #2111: Support automatic refreshing for expired OIDC tokens
- Fix #2146: Add Support for specifying CustomResourceDefinitionContext while initializing KubernetesServer
- Fix #2314: Fetch logs should wait for the job's associated pod to be ready
- Fix #2043: Support for Tekton Triggers
- Fix #2460: Querying for an event based on InvolvedObject fields
Note Minor breaking changes: