Unknown field "logging" in com.google.cloud.v1beta1.BackendConfig.spec

[caddac]

Attempting to disable LB logging on my backend (version cloud.google.com/v1beta1/BackendConfig) and getting this error: error validating data: ValidationError(BackendConfig.spec): unknown field "logging" in com.google.cloud.v1beta1.BackendConfig.spec

My full BackendConfig:

apiVersion: cloud.google.com/v1beta1
kind: BackendConfig
metadata:
  name: gke-ingress-config
spec:
  healthCheck:
    type: HTTP
    port: 15021
    requestPath: /healthz/ready
  logging:
    enable: false

This is being applied via FluxCD (which is reporting the error). In my cluster, the BackendConfig is actually v1. If I manually modify the resource, I am able to disable logging in the load balancer. I have been unable to find a doc for the v1beta1 version.

Any ideas what I'm doing wrong here?

[caddac]

updating my manifest to v1 solved this issue. But I'd still like to understand why v1beta1 doesn't work.

[freehan]

cc @skmatti

Do you see any reason why v1beta1 did not work?

[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

[skmatti]

Logging field is not defined in v1beta1 API. We have introduced this field only in V1 API.

[skmatti]

/close

[k8s-ci-robot]

@skmatti: Closing this issue.

In response to this:

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

[skmatti]

/remove-lifecycle stale