[LocalNet] Run LocalNet development set up with operator

[okdas]

Objective

We want to run developer environments utilizing this operator. Current implementation relies on docker-compose: https://github.com/pokt-network/pocket/tree/main/docs/development#running-localnet

The idea is that if we utilize this operator to not only maintain workloads on production Kubernetes clusters for dev, test and main-nets, but also for local-nets, we will have this product polished well for 3rd party use along with V1 client.

Goals

• Functionality should be (at least) on par with docker-compose set up, meaning dependencies are shipped and working well with network actors:
  • metrics collection
  • logs collection
  • grafana dashboards
• make targets that currently interact with docker compose should work agains set up inside Kubernetes

Deliverable

• LocalNet runs on Kubernetes, workloads are controlled by the operator
• Metrics and Log targets are discovered automatically, Grafana can consume the output
• Parity is reached by following the instructions in the Development Guide to achieve the exact same flow & outcome

Non-goals / Non-deliverables

• The current requirement is to only run 4 validators, though in future that number will have to be dynamic

General issue deliverables

• Update the appropriate CHANGELOG
• Update any relevant READMEs (local and/or global)
• Update any relevant global documentation & references

---

Creator: @okdas
Co-Owners: TBD

[okdas]

Did some research on how to approach this. InternalSet resource that will manage other CRDs would be ideal, taking a look if can implement this quickly or (for now) stick to utilizing Validators directly.

[Olshansk]

@okdas I believe another deliverable should be:

• Parity is reached by following the instructions in the Development Guide to achieve the exact same flow & outcome

Wdyt?

[okdas]

Opting-in to use https://tilt.dev/ because this way we are able to integrate Kubernetes operator and client – both running with hot reloaded code from local directories.

[Olshansk]

Opting-in to use tilt.dev because this way we are able to integrate Kubernetes operator and client – both running with hot reloaded code from local directories.

I read what they have in store and support this 👍👍