Can not override nameserver that faasd-provider configures #181
Comments
|
@alexellis To expand on the use case as I ran into this issue while trying to do a proof of concept for my company skytap. Basically we are trying to see how well openfaas in its entirety would work and decided to use Faasd to be able to dive right into it a bit to see how well it was going to work. Essentially though I need to be able to interface with a lot of internal services by their DNS name, and in some cases that is the only way to interact with the service. Since this is hard coded we are not able to start building out functions with faasd that need to access our internal services. For instance we want to be able to build function that perform tasks with vmware via their API on our internal instances. Additionally it seems odd to me that this would have been some kind of configurable option to begin with. Not everyone wants to or is comfortable with utilizing Google DNS services. I wouldn't be comfortable with using faasd at home or on personal projects for this fact alone. I think that the proposed pr by @kmpm is a pretty reasonable work around to at least allow some configuration of the name server. I think though that if one of the goals of the faasd project is to be production ready then I would think this would need to be some kind of configuration for the system as well or rather than. Like docker supports setting DNS via /etc/docker/daemon.json thus allowing better configuration with config management systems like ansible/puppet/chef/etc. |
The faasd provider command creates a
resolve.conffile for all functions that points to8.8.8.8for name resolution services.I have a ordinary Windows PC (yes windows only) that is running a instance of Microsoft SQL Server Express for some stuff I have. That PC gets shutdown on a daily basis and will sometime get a new IP when getting back online.
Using my local router that provides DNS services it's not an issue to reach that machine by its name but my OpenFaaS function can not because of this hard-coded nameserver.
Expected Behaviour
I would like to have the faasd-provider service to use a nameserver that I configure myself and use that instead of
8.8.8.8For example adding a flag to the faasd provider command
cmd/provider.gothat controls the nameserver with 8.8.8.8 as a default and using the value from that flag as an input when creatingresolve.confCurrent Behaviour
A
resolve.confgets created withnameserver 8.8.8.8as a static string.Are you a GitHub Sponsor (Yes/No?)
Check at: https://github.com/sponsors/openfaas
List all Possible Solutions
resolve.conffrom the host instead of creating a new.List the one solution that you would recommend
See PR #180, flag for nameserver
Steps to Reproduce (for bugs)
Context
I am trying to use an internal DNS to reach a database on a Windows PC using
name resolution because a dynamic IP that keeps changing.
For the moment I have to change a secret and update that with the IP of the machine every
time it changes.
Your Environment
OS and architecture:
Versions:
The text was updated successfully, but these errors were encountered: