Move RequestAuthentication policy creation to iap-enabler for gitops friendliness

[fabito]

Problem

In my gitops setup I was facing a race condition between Fluxcd and iap-enabler where they were both updating the ingress-jwt RequestAuthentication resource:

• Fluxcd creates/updates the ingress-jwt RequestAuthentication resource without the audience (TO_BE_PATCHED)
• iap-enabler resolves the backend id and patches the ingress-jwt audience

Solution

Move ingress-jwt RequestAuthentication creation logic to iap-enabler.

• Move policy.yaml from Kustomize resources list to envoy-config ConfigMap
• Refactor setup_backend.sh to replace TO_BE_PATCHED with the correct audience and apply policy.yaml to create/update ingress-jwt

[google-oss-prow]

Hi @fabito. Thanks for your PR.

I'm waiting for a kubeflow 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/test-infra repository.

[Arhell]

/ok-to-test

[zijianjoy]

Thank you @fabito , will this change make policy.yaml out of the control from gitops Fluxcd? Also, should we use more specific placeholder than TO_BE_PATCHED since we use sed to replace the value now? Previously we specify the yaml path for the JWT_AUDIENCE replacement.

[fabito]

Thank you @fabito , will this change make policy.yaml out of the control from gitops Fluxcd?

Yep, solely managed by iap-enabler now

Also, should we use more specific placeholder than TO_BE_PATCHED since we use sed to replace the value now?

Sure!

[gkcalat]

/lgtm
/approve

[gkcalat]

/assign @zijianjoy

[zijianjoy]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabito, gkcalat, zijianjoy

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zijianjoy]

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