RHCLOUD-36175 - Kind cluster setup for inventory

[Adam0Brien]

PR Template:

Describe your changes

• Added setup for running containers using Kind along with github workflow:

  • inventory-api - Running
  • invdatabase - Running
  • inventory-e2e-tests - Running and Passing
  • my-cluster-zookeeper-0 Running
  • strimzi-cluster-operator Running

• Added make targets for:

  • make inventory-up-kind
  • make inventory-down-kind

Output:

❯ kubectl get pods
NAME                                        READY   STATUS      RESTARTS   AGE
e2e-inventory-http-tests-r4wm2              0/1     Completed   0          62s
invdatabase-75f6cc55bc-l24b6                1/1     Running     0          62s
kessel-inventory-9bb5546d4-8tvv6            1/1     Running     0          62s
my-cluster-zookeeper-0                      0/1     Running     0          37s
strimzi-cluster-operator-6f9fbb4c75-knkpx   1/1     Running     0          63s
❯ kubectl logs e2e-inventory-http-tests-r4wm2
INFO msg=TLS environment variables not set
=== RUN   TestInventoryAPIHTTP_Livez
=== PAUSE TestInventoryAPIHTTP_Livez
=== RUN   TestInventoryAPIHTTP_Readyz
=== PAUSE TestInventoryAPIHTTP_Readyz
=== RUN   TestInventoryAPIHTTP_Metrics
--- PASS: TestInventoryAPIHTTP_Metrics (0.00s)
=== RUN   TestInventoryAPIHTTP_CreateRHELHost
=== PAUSE TestInventoryAPIHTTP_CreateRHELHost
=== RUN   TestInventoryAPIHTTP_K8SCluster_CreateK8SCluster
=== PAUSE TestInventoryAPIHTTP_K8SCluster_CreateK8SCluster
=== RUN   TestInventoryAPIHTTP_K8SPolicy_CreateK8SPolicy
=== PAUSE TestInventoryAPIHTTP_K8SPolicy_CreateK8SPolicy
=== RUN   Test_ACMKafkaConsumer
=== PAUSE Test_ACMKafkaConsumer
=== CONT  TestInventoryAPIHTTP_Livez
=== CONT  TestInventoryAPIHTTP_K8SCluster_CreateK8SCluster
=== CONT  Test_ACMKafkaConsumer
=== CONT  TestInventoryAPIHTTP_CreateRHELHost
=== CONT  TestInventoryAPIHTTP_Readyz
=== CONT  TestInventoryAPIHTTP_K8SPolicy_CreateK8SPolicy
--- PASS: TestInventoryAPIHTTP_Livez (0.00s)
--- PASS: TestInventoryAPIHTTP_Readyz (0.00s)
%3|1731421415.806|FAIL|rdkafka#consumer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv4#127.0.0.1:9092 failed: Connection refused (after 0ms in state CONNECT)
% Error: Local: Broker transport failure: localhost:9092/bootstrap: Connect to ipv4#127.0.0.1:9092 failed: Connection refused (after 0ms in state CONNECT)
% Error: Local: All broker connections are down: 1/1 brokers are down
--- PASS: Test_ACMKafkaConsumer (0.00s)
--- PASS: TestInventoryAPIHTTP_CreateRHELHost (0.02s)
--- PASS: TestInventoryAPIHTTP_K8SPolicy_CreateK8SPolicy (0.02s)
--- PASS: TestInventoryAPIHTTP_K8SCluster_CreateK8SCluster (0.02s)
PASS

Ticket reference (if applicable)

Fixes RHCLOUD-36175

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?