Rework kind setup by removing Ingress and embedded etcd

[embik]

This PR is a pretty big refresh to the kind setup because I was discussing it with an interested party and we just couldn't get the setup to work properly. I assume it has been broken in many ways for a while.

The changes in this PR are:

• Eliminate usage of an Ingress. If we are going to have a node port exposure via nginx-ingress-controller, might as well expose kcp directly. This switches the kcp-front-proxy Service to be of type NodePort.
• Make the kcp-front-proxy Service more configurable to pre-allocate a service IP and a specific node port, so we can hack in DNS entries (on the kcp Pod side) and node port forwards (on the kind side) pointing to the front proxy.
  • Subsequently, this PR sets up a host alias in the kcp pod to make sure that traffic to the external name gets routed to the kcp-front-proxy Service.
• Get rid of using the latest tag. This is a setup that new users will end up with to try out kcp, there is no reason to expose them to development versions.
• Stop using embedded etcd. It's broken (since #81).

Please give this a spin on your system before approving it, but for my kind setup it works without issues as far as I can say.

[xrstf]

/approve /lgtm

[kcp-ci-bot]

LGTM label has been added.

Git tree hash: cc4dc6ac4b60cef54cbe29f1b5f50770048ebec5

[embik]

/approve

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik, xrstf

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](https://github.com/kcp-dev/helm-charts/blob/main/OWNERS)~~ [embik] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment