BackendConfig OpenAPI spec

[DennisVis]

I'm using Deployment Manager to deploy all k8s resources by leveraging custom types. To create these types Deployment Manager needs access to an OpenAPI spec. For the Ingress this works fine, but I can't find the one for the BackendConfig type.

I see one is created in pkg/apis/backendconfig/v1beta1/zz_generated.openapi.go, is this exposed anywhere on the gke cluster?

[rramkumar1]

@DennisVis when you say "can't find one for the BackendConfig type", can you point me to where you looked?

I remember in the past we have had some complaints that BackendConfig does not work with Deployment Manager so hopefully we can address that soon.

/kind bug

[DennisVis]

The first place I looked was in the cluster swagger specification which can be found at https://{cluster-ip}/swaggerapi. But none of the endpoints seem to hold a reference to the namespace being used by the BackendConfig cloud.google.com.

I tried finding the API itself which can be found at https://{cluster-ip}/apis/cloud.google.com/v1beta1. A GET request results in a descriptive document, but it's not an OpenAPI spec so DM can't use it.

I assume the spec must live somewhere and be reachable as the existence of zz_generated.openapi.go suggests as much.

[rramkumar1]

@DennisVis thanks for the info. I'll ask around to see how this can be resolved as I'm not immediately sure what the next step is.

[DennisVis]

@rramkumar1 Did you manage to make any progress on this?

[MrHohn]

It seems like folks are working on publishing openapi for CRD: kubernetes/kubernetes#71192

[mbohlool]

Also https://{cluster-ip}/swaggerapi is deprecated and old swagger 1.2. It is not up to date. The correct path is https://{cluster-ip}/openapi/v2. But CRDs is not included in OpenAPI spec yet and kubernetes/kubernetes#71192 is trying to handle that. Note that it will only appear if the CRD has a validation schema which is in OpenAPI v3 model format (or schema field for new versions struct in CRD's spec.versions)

[bowei]

@rramkumar1 we should check if we satisfy the OpenAPI v3 model format and close this bug.

[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.

[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.