Automated cherry pick of #529: istio: oidc-authservice Cherry pick of #529 on v0.7-branch. #529: istio: oidc-authservice

[yanniszark]

This change is 

[yanniszark]

Related to #616

/assign @jlewi @krishnadurai

[jlewi]

@yanniszark Can you provide me a little bit more context? I tried looking through the linked issues and PRs but couldn't find an overarching explanation of the feature or bug being addressed here.

My high level question is what's the motivation for cherry-picking these changes onto the v0.7-branch? Especially given that next week is Kubecon and we just published our 0.7 blog post is it possible these changes could break 0.7 just as lots of people try it?

[krishnadurai]

/lgtm

[krishnadurai]

@jlewi refer to my comment.

[jlewi]

Thanks @krishnadurai does this PR present any risk to the other configs?

[krishnadurai]

@jlewi These shouldn't affect any other config as OIDC AuthService and Cert-Manger are only used by the existing_arrikto config.

[yanniszark]

@jlewi all tests are green after the rebase.
As mentioned, this should only affect the istio_dex config.
I'm leaving a hold in case you want to do another review here.

/approve
/hold

[jlewi]

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi, yanniszark

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 [jlewi,yanniszark]

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