-
Notifications
You must be signed in to change notification settings - Fork 243
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
Add host.crc.testing to /etc/hosts #4410
Comments
It is similar to this docker feature https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host, I'm not sure this also can be resolved on the host? |
@bobbygryzynger if |
@praveenkumar I have some scripts that run both on the host and within containers on the cluster that interact with host services. It would be convenient to be able to use the same hostname in both circumstances and not have to set the value in the host's |
Can I work on this issue? |
+ Add another method `GetHostName()` to CrcBundleInfo struct in order to provide host domain + Use abovementioned method in `dns.addOpenShiftHosts` in order to add another dns entry for `host.crc.testing` Signed-off-by: Rohan Kumar <rohaan@redhat.com>
+ Add another method `GetFQDN()` to CrcBundleInfo struct in order to provide host domain + Use abovementioned method in `dns.addOpenShiftHosts` in order to add another dns entry for `host.crc.testing` Signed-off-by: Rohan Kumar <rohaan@redhat.com>
+ Add another method `GetFQDN()` to CrcBundleInfo struct in order to provide host domain + Use abovementioned method in `dns.addOpenShiftHosts` in order to add another dns entry for `host.crc.testing` Signed-off-by: Rohan Kumar <rohaan@redhat.com>
This issue got fixed by #4471 . Could someone please close the issue? |
"Fixes: #4410" in the PR should have triggered the closing automatically, maybe this needs to be formatted slightly differently. |
Related to #4398: because the host can be reached at
host.crc.testing
this should be added to CRC's/etc/hosts
modifications.The text was updated successfully, but these errors were encountered: