io.kubernetes.client-java:14.0.0 missing V1PodBuilder

[Delovelyeleven]

Describe the bug io.kubernetes.client-java:14.0.0 missing V1PodBuilder

Client Version 14.0.0

Kubernetes Version 1.21

Java Version Java 8

[wideocean]

V1PodBuilder is located here: https://github.com/kubernetes-client/java/blob/client-java-parent-14.0.0/fluent/src/main/java/io/kubernetes/client/openapi/models/V1PodBuilder.java

[VikasChoataHP]

I am facing the same issue with V1ObjectMetaBuilder; Jar file downloaded by maven doesn't have this. I get below error The import io.kubernetes.client.openapi.models.V1ObjectMetaBuilder cannot be resolved

Do we need to import from a different package?

[ojagodzinski]

@VikasChoata88 yup, all .*Builder classes got removed

• https://javadoc.io/static/io.kubernetes/client-java-api/12.0.2/allclasses-noframe.html
• https://javadoc.io/static/io.kubernetes/client-java-api/14.0.1/allclasses-noframe.html

something like:

-                    new V1ObjectMetaBuilder()
-                            .withAnnotations([(K8sMetadataFactory.SOME_LABEL): "0.0.1"])
-                            .build()
+                    new V1ObjectMeta()
+                            .annotations([(K8sMetadataFactory.SOME_LABEL): "0.0.1"])

should be enough.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.