You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of right now, we have no way of accessing a kafka broker outside of the dev environment. That means we can only use kcat to list brokers and we are unable to side cart a kafka UI outside of the cluster to monitor kafka topics, messages, consumers, and consumer offsets.
We also can't access the minio UI because it points to a random port that we don't have access to. The minio UI has a lot of useful tools that can be used for debugging such as trace log monitoring, information on bucket naming rules, etc.
Having easy access to these things will help give us more insight on related failing tests in e2e and give us more information on these services when running a local dev cluster.
The text was updated successfully, but these errors were encountered:
… e2e (#3760)
This PR makes the following changes:
## Development Improvements
- Adds `localhost` kafka broker to `ts-scripts k8s` kafka service
- This allows for easy connection to kafka from within the host machine
- Adds port to minio k8s deployment and e2e to allow the connection to
minio-ui
- Useful for debugging minio related issues in e2e and k8s
Ref to issue #3759
This issue branches out into two similar issues:
Having easy access to these things will help give us more insight on related failing tests in e2e and give us more information on these services when running a local dev cluster.
The text was updated successfully, but these errors were encountered: