Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump kubernetes-client.version from 4.11.1 to 5.0.0 #69

Merged
merged 3 commits into from
Mar 29, 2021

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 31, 2020

Bumps kubernetes-client.version from 4.11.1 to 5.0.0.
Updates kubernetes-client from 4.11.1 to 5.0.0

Release notes

Sourced from kubernetes-client's releases.

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 for CustomResource instances
    • CustomResource instances must now be annotated with @ApiVersion and @ApiGroup so that the associated information can be automatically computed
    • HasMetadata provides default implementations for getApiVersion and getKind based on the presence (or not) of annotations on the target class
    • Static methods have been introduced on HasMetadata and CustomResource to encapsulate the logic used to resolve Kind, ApiVersion, Group, Version, Plural, Singular and CRD Name properties
    • New v1CRDFromCustomResourceType and v1beta1CRDFromCustomResourceType methods have been introduced on CustomResourceDefinitionContext to initialize a CustomResourceDefinitionBuilder with the information provided by a specific CustomResource 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
  • 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 by HasMetadata#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 on HasMetadata to encapsulate validation logic

... (truncated)

Changelog

Sourced from kubernetes-client's changelog.

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 #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 for CustomResource instances
    • CustomResource instances must now be annotated with @Version and @Group so that the associated information can be automatically computed
    • HasMetadata provides default implementations for getApiVersion and getKind based on the presence (or not) of annotations on the target class
    • Static methods have been introduced on HasMetadata and CustomResource to encapsulate the logic used to resolve Kind, ApiVersion, Group, Version, Plural, Singular and CRD Name properties
    • New v1CRDFromCustomResourceType and v1beta1CRDFromCustomResourceType methods have been introduced on CustomResourceDefinitionContext to initialize a CustomResourceDefinitionBuilder with the information provided by a specific CustomResource 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
  • 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 by HasMetadata#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 #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 on HasMetadata to encapsulate validation logic

... (truncated)

Commits
  • 427919c [RELEASE] Updated project version to v5.0.0
  • 24491c7 Merge pull request #2700 from manusa/fix/crd-context-from-custom-resource
  • 6648179 fix: fromCustomResourceType is of type CustomResource
  • 840d3a2 Merge pull request #2659 from manusa/doc/v5-migration-guide
  • 5151219 Merge pull request #2688 from manusa/doc/examples-update
  • f1d1fb4 doc: Migration to v5 guide
  • 4c020b4 doc: Updated and cleaned up Kubernetes + OpenShift examples
  • 6a717e4 Merge pull request #2689 from rohanKanojia/pr/buildconfig-instantiate-it
  • 39756a1 Add an integration test for BuildConfig instantiation
  • b6e0f7f Add an Integration test for Typed CustomResource support (#2685)
  • Additional commits viewable in compare view

Updates openshift-client from 4.11.1 to 5.0.0

Release notes

Sourced from openshift-client's releases.

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 for CustomResource instances
    • CustomResource instances must now be annotated with @ApiVersion and @ApiGroup so that the associated information can be automatically computed
    • HasMetadata provides default implementations for getApiVersion and getKind based on the presence (or not) of annotations on the target class
    • Static methods have been introduced on HasMetadata and CustomResource to encapsulate the logic used to resolve Kind, ApiVersion, Group, Version, Plural, Singular and CRD Name properties
    • New v1CRDFromCustomResourceType and v1beta1CRDFromCustomResourceType methods have been introduced on CustomResourceDefinitionContext to initialize a CustomResourceDefinitionBuilder with the information provided by a specific CustomResource 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
  • 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 by HasMetadata#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 on HasMetadata to encapsulate validation logic

... (truncated)

Changelog

Sourced from openshift-client's changelog.

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 #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 for CustomResource instances
    • CustomResource instances must now be annotated with @Version and @Group so that the associated information can be automatically computed
    • HasMetadata provides default implementations for getApiVersion and getKind based on the presence (or not) of annotations on the target class
    • Static methods have been introduced on HasMetadata and CustomResource to encapsulate the logic used to resolve Kind, ApiVersion, Group, Version, Plural, Singular and CRD Name properties
    • New v1CRDFromCustomResourceType and v1beta1CRDFromCustomResourceType methods have been introduced on CustomResourceDefinitionContext to initialize a CustomResourceDefinitionBuilder with the information provided by a specific CustomResource 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
  • 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 by HasMetadata#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 #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 on HasMetadata to encapsulate validation logic

... (truncated)

Commits
  • 427919c [RELEASE] Updated project version to v5.0.0
  • 24491c7 Merge pull request #2700 from manusa/fix/crd-context-from-custom-resource
  • 6648179 fix: fromCustomResourceType is of type CustomResource
  • 840d3a2 Merge pull request #2659 from manusa/doc/v5-migration-guide
  • 5151219 Merge pull request #2688 from manusa/doc/examples-update
  • f1d1fb4 doc: Migration to v5 guide
  • 4c020b4 doc: Updated and cleaned up Kubernetes + OpenShift examples
  • 6a717e4 Merge pull request #2689 from rohanKanojia/pr/buildconfig-instantiate-it
  • 39756a1 Add an integration test for BuildConfig instantiation
  • b6e0f7f Add an Integration test for Typed CustomResource support (#2685)
  • Additional commits viewable in compare view

Updates volumesnapshot-client from 4.11.1 to 5.0.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `kubernetes-client.version` from 4.11.1 to 5.0.0.

Updates `kubernetes-client` from 4.11.1 to 5.0.0
- [Release notes](https://github.com/fabric8io/kubernetes-client/releases)
- [Changelog](https://github.com/fabric8io/kubernetes-client/blob/master/CHANGELOG.md)
- [Commits](fabric8io/kubernetes-client@v4.11.1...v5.0.0)

Updates `openshift-client` from 4.11.1 to 5.0.0
- [Release notes](https://github.com/fabric8io/kubernetes-client/releases)
- [Changelog](https://github.com/fabric8io/kubernetes-client/blob/master/CHANGELOG.md)
- [Commits](fabric8io/kubernetes-client@v4.11.1...v5.0.0)

Updates `volumesnapshot-client` from 4.11.1 to 5.0.0

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 31, 2020
@rittneje
Copy link

@Vlatombe I am hoping for this upgrade to go through so we can take advantage of a recent bugfix in kubernetes-client. Is the only change required to update the revision in pom.xml to 5.0.0? https://github.com/jenkinsci/kubernetes-client-api-plugin/blob/master/pom.xml#L16

@Vlatombe
Copy link
Member

There are multiple API breaks in this new major version. These need to be reviewed and fixed first.

@Vlatombe Vlatombe merged commit 3c6011c into master Mar 29, 2021
@dependabot dependabot bot deleted the dependabot/maven/kubernetes-client.version-5.0.0 branch March 29, 2021 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants