-
Notifications
You must be signed in to change notification settings - Fork 0
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
Headless service support #80
Comments
You can create a headless service that points to your pods however the hostport allocator won't do anything with it, the headless service will just act as it does normally. It is only made to assign ports for pod host ports. |
understood - reason why I was asking is that I wanted to expose the allocated host port through the SRV record registered into kube dns. If that makes sense.. |
Ah I see. What you could do is create the |
It's a bit manual though, ideally I would package the HostPortClaim along with the app in the same chart and then it would automatically set up the service with the allocated host port. However, I do understand this is a bit more involved and probably not easily achievable. Thank you for prompt responses. It's a great and useful project, I'll definitely use it. |
No problem! I can look into supporting something like that. It is a bit tricky since services act differently then pods but I'll see what I can do. |
thanks @rmb938 - look forward to seeing what you come up with there. |
hey @rmb938! HNY ;) - was just checking back in today after the hols as I am looking at running some tests with the controller. Did you have time to find out whether it's possible to support services at all? Thanks. |
Yep it should be possible. I will see if I can get something out this weekend, otherwise I'll probably be a week or two. |
This is more of a question / feature request rather than an issue itself.
I was looking at using the hostport allocator in combination with a headless service. However, I don't see any references or examples of whether this is supported or not.
Thank you.
The text was updated successfully, but these errors were encountered: