Add initial controller code and translator logic

[chuangw6]

What type of PR is this?

/kind feature

What this PR does / why we need it:

• Add initial controller implementation.

  Note: Currently, the controller just reconciles the resources, but doesn't translate them to envoy config, which will be added in follow-up PRs.

• Add translator code that translates GW resources to Envoy config.

  Note: this code is not connected to controller yet and needs some updates in follow-up PRs

Which issue(s) this PR fixes:

#19

Does this PR introduce a user-facing change?:

Initial controller implementation.

[k8s-ci-robot]

Hi @chuangw6. Thanks for your PR.

I'm waiting for a github.com 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.

[LiorLieberman]

Thanks, looks good to me overall with two nits!
will lgtm once you get a chance to fix that

[david-martin]

@chuangw6 Is this in essence a partial Gateway API implementation that will use envoy proxy as the underlying gateway,
with an implementation for the proposed APIs (AccessPolicy and Backend)?

[chuangw6]

@chuangw6 Is this in essence a partial Gateway API implementation that will use envoy proxy as the underlying gateway, with an implementation for the proposed APIs (AccessPolicy and Backend)?

Yes, this is correct! @david-martin

[LiorLieberman]

/ok-to-test

[hzxuzhonghu]

I donot understand here, why does it read from k8s, oss k8s seems no such endpoint?

[chuangw6]

I think it's standard OIDC discovery endpoint per https://kubernetes.io/docs/reference/config-api/apiserver-config.v1/#apiserver-config-k8s-io-v1-Issuer

[chuangw6]

Strictly speaking, I think it's available when the SA volume projection is enabled per https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-issuer-discovery.

And SA volume projection is required to allow the client application Pod (i.e. MCP client) to surface its token.

[LiorLieberman]

This looks good as another foundation for the controller. Thanks @chuangw6!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chuangw6, LiorLieberman

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 [LiorLieberman]

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