Fix: IAP cannot be disabled

[yfuruyama]

Issue Overview

Currently when disabling IAP with the following BackendConfig,

apiVersion: cloud.google.com/v1
kind: BackendConfig
metadata:
  name: iap-backendconfig
spec:
  iap:
    enabled: false

it results with a following sync error:

Error syncing to GCP: error running backend syncing routine: Errored updating IAP Settings for service default/sample-svc: Cannot switch to default OAuth once IAP credentials have been set

Issue Details

This is because when spec.iap.enabled: false is applied, the validation is skipped and beConfig.Spec.Iap.OAuthClientCredentials won't be fulfilled properly (code), so switchingToDefault function always uses the blank OAuth client credentials and returns the error here.

This might be a regression that was introduced by this commit.

About this PR

This PR added the validation in switchingToDefault so that it can continue updating the IAP setting when it's disabled.

I tested this change with manual l7-lb-controller deployment and disabling IAP succeeded with the following logs.

[2024-07-15 21:10:39.058 JST] "Iap `enabled` setting changed: " logger="IngressController.SyncBackends.EnsureIAP" ingressKey="default/sample-ingress" syncId=750146048 backendServiceName="k8s1-f9080803-default-sample-svc-443-b069e533" backendVersion="ga" backendScope="global" port=0 service="default/sample-svc" from=true to=false 

[2024-07-15 21:10:39.058 JST] "Updated IAP settings" logger="IngressController.SyncBackends.EnsureIAP" ingressKey="default/sample-ingress" syncId=750146048 backendServiceName="k8s1-f9080803-default-sample-svc-443-b069e533" backendVersion="ga" backendScope="global" port=0 service="default/sample-svc" 

[2024-07-15 21:10:39.058 JST] "Updating ga BackendService" logger="IngressController.SyncBackends" ingressKey="default/sample-ingress" syncId=750146048 backendServiceName="k8s1-f9080803-default-sample-svc-443-b069e533" backendVersion="ga" backendScope="global" port=0 name="k8s1-f9080803-default-sample-svc-443-b069e533" 

[k8s-ci-robot]

Hi @yfuruyama. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yfuruyama
Once this PR has been reviewed and has the lgtm label, please assign mrhohn for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[swetharepakula]

/ok-to-test

[swetharepakula]

/hold

After some offline discussion, we are waiting on changes on the underlying Arcus API before proceeding with this PR. We may be able to remove the validation completely.

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this 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 PRs.

This bot triages 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 PR is closed

You can:

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

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

/lifecycle rotten