-
Notifications
You must be signed in to change notification settings - Fork 6
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
worker.ingress is documented but not implemented #14
Comments
I think you are correct. The intent is to have an Ingress for worker and controller as clients need to be able to reach both and may be different as you could run the controller in one cluster and workers in another without a controller. Also, as I understand, the controller could be HTTP/HTTPS ALB, whereas the worker needs to be a TCP NLB. I just think I didn't get to it before releasing the initial version. I'm recovering from COVID and will work on this when I get a chance unless you're already working on it. |
* Closes: worker.ingress is documented but not implemented #14 Signed-off-by: Jeremy T. Bouse <Jeremy.Bouse@UnderGrid.net>
@jbouse @fredleger Thanks in advance! |
@AbhilashaLiv I have some changes locally that I haven't pushed up yet that I believe are addressing the problem, but I have been sidetracked on other projects for work and have not had much time lately to work on this. I'll try to get some time blocked to work on this and get my changes pushed up as soon as I resolve it. |
I have been testing it in EKS for a while but still not able to get the workers to work as intended as by default it registers with localhost. Any help how to get the public ip or even ingress setup for workers would be great! |
I'll assume you're using the I( have honestly not looked back at this in some time as the POC I was writing it for was placed on hold. |
seems that in the README and the docs you mention this block of settings but templates does not include an ingress template
The text was updated successfully, but these errors were encountered: