CustomObjectsApi needs enhancement

[rjeberhard]

Presently, we generate our own "Api" class for the type described by our CRD; however, I'd prefer to use the built-in CustomObjectsApi class.

Unfortunately, there is no way to pass in the our Type (and list Type) when constructing or using this class. Also, the list methods are missing parameters like fieldSelector and _continue.

I'm happy to assist with performing the enhancement but would like to know if there is a way to adjust how this class is generated so that we get the enhancements described.

@brendandburns

[tamalsaha]

@rjeberhard , you may be interested in kubernetes-client/gen#59 (comment)

[brendandburns]

This is tricky... I'm going to have to think about it a little bit...

[rjeberhard]

Hi, @brendandburns. Any update on this one? If you look at the conversation in Issue #515 you'll see the gymnastics that are presently necessary to use your own type.

In the meantime, we basically copied methods from CoreV1Api, but used the paths from CustomObjectsApi, and then updated to use our custom type.

[yue9944882]

@rjeberhard , you may be interested in kubernetes-client/gen#59 (comment)

just regenerating the client is fine i believe..

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[yue9944882]

/remove-lifecycle rotten

ref: #609, working on structured CRD client generation

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.