Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable nodeport by default #223

Open
planetf1 opened this issue Dec 5, 2022 · 2 comments
Open

Enable nodeport by default #223

planetf1 opened this issue Dec 5, 2022 · 2 comments

Comments

@planetf1
Copy link
Member

planetf1 commented Dec 5, 2022

Many users trying out our Kubernetes charts are new to k8s.
One of the first questions asked or issues hit, is being able to access egeria (chassis, UI etc)

Our charts support 'nodeports'. This is where a port is made available on the IP address currently used by the kubernetes workers. This may not be useful in a cloud environment where there are additional restrictions, firewalls, and capabilities - using regular ingress may be easier. However for simple local environments - where ingress is hard (needing additional IPs etc) it works well.

This suggestion is to enable nodeports by default. It doesn't preclude other connectivity. The main risk is that a failure to allocate could cause pods not to run.

@dwolfson
Copy link
Member

dwolfson commented Dec 5, 2022

Yes - it might also be helpful (at least for testing purposes) if the default nodeport range was different for each kind of chart - so for instance, one could run base and lab charts in the same cluster?

@planetf1
Copy link
Member Author

planetf1 commented Dec 5, 2022

That's a good idea. let's do that.

Though note that to run multiple charts, you will need to deploy strimzi seperately, and disable the setup when installing the egeria charts (this is in the docs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Todo
Development

No branches or pull requests

2 participants