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-bom from 5.0.2 to 5.1.0 #15154

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 17, 2021

Bumps kubernetes-client-bom from 5.0.2 to 5.1.0.

Release notes

Sourced from kubernetes-client-bom's releases.

5.1.0 (2021-02-17)

Bugs

  • Fix #2748: Pass custom headers in kubernetes-client to watch api by modify WatchConnectionManager
  • Fix #2745: Filtering Operations can't configure PropagationPolicy
  • Fix #2672: WaitUntilReady for Service resource throws IllegalArgumentException

Improvements

  • Fix #2717: Remove edit() methods from RawCustomResourceOperationsImpl taking InputStream arguments
  • Fix #2757: add storage and served to Version annotation
  • Fix #2759: add ShortNames annotation to specify short names for CRD generation
  • Fix #2694: Remove deprecated methods from KubernetesClient DSL
  • Fix #2716: Add a property to disable BackwardCompatibilityInterceptor

Dependency Upgrade

  • Fix #2706: update Tekton Triggers model to v0.11.1
  • Fix #2684: Upgrade Kubernetes Model to v1.20.2

New Features

  • Fix #2702: Add support for discovery.k8s.io/v1beta1 EndpointSlice in KubernetesClient DSL
  • Fix #2703: Add support for certificates.k8s.io v1 and v1beta1 API in KubernetesClient DSL
  • Fix #2708: Update CSI Volume Snapshot API to v1
  • Fix #2789: Use thread context class loader instead of Class.forName
  • Fix #2779: Add DSL support for scheduling.k8s.io v1 and v1beta1 to SchedulingAPIGroupDSL
  • Fix #2776: Preview release of CRD generator based on annotations
    • Classes extending the CustomResource class can now be used as the basis for CRD generation
    • Several annotations are available to override the default behavior if it doesn't fit your needs
    • Validation schema is automatically derived from your class' spec implementation (or from the CR class, if no spec is present)
    • CRDs are automatically generated at compile-time if you include the io.fabric8:crd-generator dependency to your project (with the suggested compile scope)
    • CRDs are generated for both v1beta1 and v1 versions of the specification at this point
    • One CRD manifest is generated per CRD using the CRD name (e.g. mycrplural.group.example.com) suffixed with the specification version, e.g. mycrplural.group.example.com-v1.yml
    • The CRD files are generated in the target/META-INF/fabric8 directory of your project

Note: Breaking changes in the API

DSL Changes:
  • client.settings() DSL has been removed since PodPreset v1alpha1 API is no longer present in Kubernetes 1.20.x
  • client.customResourceDefinitions() has been removed. Use client.apiextensions().v1beta1().customResourceDefinitions() instead
  • client.events() has been removed. Use client.v1().events() instead
  • client.customResource(...) method is removed. Use client.customResources(...) with CustomResource configuration in annotations inside POJOs
Model Changes:
  • Classes in io.fabric8.kubernetes.api.model.scheduling have been moved to io.fabric8.kubernetes.api.model.scheduling.v1 and io.fabric8.kubernetes.api.model.scheduling.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.admission have been moved to io.fabric8.kubernetes.api.model.admission.v1 and io.fabric8.kubernetes.api.model.admission.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.certificates have been moved to io.fabric8.kubernetes.api.model.certificates.v1 and io.fabric8.kubernetes.api.model.certificates.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.events have been moved to io.fabric8.kubernetes.api.model.events.v1 and io.fabric8.kubernetes.api.model.events.v1beta1
Changelog

Sourced from kubernetes-client-bom's changelog.

5.1.0 (2021-02-17)

Bugs

  • Fix #2748: Pass custom headers in kubernetes-client to watch api by modify WatchConnectionManager
  • Fix #2745: Filtering Operations can't configure PropagationPolicy
  • Fix #2672: WaitUntilReady for Service resource throws IllegalArgumentException

Improvements

  • Fix #2717: Remove edit() methods from RawCustomResourceOperationsImpl taking InputStream arguments
  • Fix #2757: add storage and served to Version annotation
  • Fix #2759: add ShortNames annotation to specify short names for CRD generation
  • Fix #2694: Remove deprecated methods from KubernetesClient DSL
  • Fix #2716: Add a property to disable BackwardCompatibilityInterceptor

Dependency Upgrade

  • Fix #2706: update Tekton Triggers model to v0.11.1
  • Fix #2684: Upgrade Kubernetes Model to v1.20.2

New Features

  • Fix #2702: Add support for discovery.k8s.io/v1beta1 EndpointSlice in KubernetesClient DSL
  • Fix #2703: Add support for certificates.k8s.io v1 and v1beta1 API in KubernetesClient DSL
  • Fix #2708: Update CSI Volume Snapshot API to v1
  • Fix #2789: Use thread context class loader instead of Class.forName
  • Fix #2779: Add DSL support for scheduling.k8s.io v1 and v1beta1 to SchedulingAPIGroupDSL
  • Fix #2776: Preview release of CRD generator based on annotations
    • Classes extending the CustomResource class can now be used as the basis for CRD generation
    • Several annotations are available to override the default behavior if it doesn't fit your needs
    • Validation schema is automatically derived from your class' spec implementation (or from the CR class, if no spec is present)
    • CRDs are automatically generated at compile-time if you include the io.fabric8:crd-generator dependency to your project (with the suggested compile scope)
    • CRDs are generated for both v1beta1 and v1 versions of the specification at this point
    • One CRD manifest is generated per CRD using the CRD name (e.g. mycrplural.group.example.com) suffixed with the specification version, e.g. mycrplural.group.example.com-v1.yml
    • The CRD files are generated in the target/META-INF/fabric8 directory of your project

Note: Breaking changes in the API

DSL Changes:
  • client.settings() DSL has been removed since PodPreset v1alpha1 API is no longer present in Kubernetes 1.20.x
  • client.customResourceDefinitions() has been removed. Use client.apiextensions().v1beta1().customResourceDefinitions() instead
  • client.events() has been removed. Use client.v1().events() instead
  • client.customResource(...) method is removed. Use client.customResources(...) with CustomResource configuration in annotations inside POJOs
Model Changes:
  • Classes in io.fabric8.kubernetes.api.model.scheduling have been moved to io.fabric8.kubernetes.api.model.scheduling.v1 and io.fabric8.kubernetes.api.model.scheduling.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.admission have been moved to io.fabric8.kubernetes.api.model.admission.v1 and io.fabric8.kubernetes.api.model.admission.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.certificates have been moved to io.fabric8.kubernetes.api.model.certificates.v1 and io.fabric8.kubernetes.api.model.certificates.v1beta1
  • Classes in io.fabric8.kubernetes.api.model.events have been moved to io.fabric8.kubernetes.api.model.events.v1 and io.fabric8.kubernetes.api.model.events.v1beta1

4.11.2 (2021-02-09)

... (truncated)

Commits
  • 1a59e3b [RELEASE] Updated project version to v5.1.0
  • ef64ef2 fix: e2e readiness
  • d8eb90c refactor: Readiness no longer utility class
  • 81e1086 Use static String variable in Readiness/OpenShiftReadiness
  • 3a5d76f Fix #2672: WaitUntilReady for Service resource throws IllegalArgumentException
  • 22412af Remove redundant assertion
  • d6769dd Issue-2805: Simplify JUnit
  • 19c5ce6 Fix #2745: Filtering Operations can't configure PropagationPolicy
  • 8ec884f test: Missing assertion for KubernetesList Visitor test
  • 8bbf56f Issue-2804: Swap assertion arguments so they are in the correct order: expect...
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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)

@dependabot dependabot bot added the area/dependencies Pull requests that update a dependency file label Feb 17, 2021
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@geoand @iocanel looks like CI is happy, should we merge?

@geoand
Copy link
Contributor

geoand commented Feb 18, 2021

I'll leave this up to @iocanel and @metacosm to decide as they are the ones that would be most impacted by this

@metacosm
Copy link
Contributor

@geoand @gsmet I'd like to get that change in, yes. What would be the timeline for inclusion in a release?

@geoand
Copy link
Contributor

geoand commented Feb 18, 2021

1.12 was already cut, so likely 1.13

@gsmet gsmet merged commit db8041c into master Feb 18, 2021
@quarkus-bot quarkus-bot bot added this to the 1.13 - master milestone Feb 18, 2021
@dependabot dependabot bot deleted the dependabot/maven/io.fabric8-kubernetes-client-bom-5.1.0 branch February 18, 2021 14:31
@gsmet
Copy link
Member

gsmet commented Feb 18, 2021

Yeah except if there's a very good reason to backport it, it will be for 1.13 so in ~ 1 month.

@gsmet
Copy link
Member

gsmet commented Feb 23, 2021

Marked for backport because of #15250 (comment) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants