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

Inconsistent additionalPrinterColumns jsonPath #1631

Closed
lburgazzoli opened this issue Nov 25, 2022 · 2 comments
Closed

Inconsistent additionalPrinterColumns jsonPath #1631

lburgazzoli opened this issue Nov 25, 2022 · 2 comments

Comments

@lburgazzoli
Copy link
Collaborator

lburgazzoli commented Nov 25, 2022

Bug Report

What did you do?

I have a class defined like:

@JsonInclude(JsonInclude.Include.NON_NULL)
@Buildable(builderPackage = "io.fabric8.kubernetes.api.builder")
public class DeploymentSpec {

    @PrinterColumn(name = "CONNECTOR_TYPE_ID")
    private String connectorTypeId;
}

And such class is used in bot the spec and the status of a resource.

What did you expect to see?

The generated CRD should always use the same path to describe the CONNECTOR_TYPE_ID column.

What did you see instead? Under which circumstances?

The resulted CRD may get amended at every build, i.e:

image

Environment

Versions:

        <kubernetes-client.version>5.12.3</kubernetes-client.version>
        <java-operator-sdk.version>3.1.1</java-operator-sdk.version>
        <quarkus.version>2.11.2.Final</quarkus.version>
        <quarkus-operator-sdk.version>4.0.1</quarkus-operator-sdk.version>
        <sundrio.version>0.50.2</sundrio.version>
@csviri
Copy link
Collaborator

csviri commented Nov 28, 2022

@lburgazzoli could you pls move this issue (re-create) in fabric8 client, this is implemented there. Thx! will close it here

@csviri csviri closed this as completed Nov 28, 2022
@lburgazzoli
Copy link
Collaborator Author

Moved here: fabric8io/kubernetes-client#4610

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants