Feat(k8-manifest): introduce a manifest containing a redpanda broker

[ChrisRousey]

Added a manifest which also deploys a redpanda broker.

To access the broker inside datacater, bootsrap.servers is redpanda-0.redpanda.default.svc.cluster.local.:9093 To produce data to broker, use the following command: kubectl exec -it -n default redpanda-0 -- rpk topic produce topicName --brokers='redpanda-0.redpanda.default.svc.cluster.local.:9093'

Currently running minikube with:

• cpus: 4
• memory: 8192

Update

By editing /etc/hosts/ and adding the line 127.0.0.1 redpanda-0.redpanda.default.svc.cluster.local., you can then portforward kubectl port-forward redpanda-0 9093:9093 and access the topics through localhost. This is much faster to produce test records, than using rpk inside the cluster

[flippingbits]

Thanks, that is a very helpful for testing and playing with DataCater! :)

Can we somewhere document how to generate these manifests, so we can easily update them if needed?

[HknLof]

I think these manifests should only be used for development. We should also add README.md into the k8s-manifests directory, which describes how to generate the manifests as mentioned by @flippingbits.

Further, I opened an issue regarding some annotations, but this would need to touch all manifests. https://github.com/DataCater/datacater/issues/129

[ChrisRousey]

@HknLof @flippingbits i'll update the manifests labels in this PR and add a readme how to work with and use redpanda in cluster

Should i also add the changes to run pythonrunner stateful set in k8 instead of through the application? The changes for this are already in main but no in the currently referenced image nightly-20230105

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information