-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Feature]: Helm value for icinga2-master Endpoint address #20
Comments
We will have to take a look if we can go ahead and change this - I remember something about the director kickstart breaking when meddling with the |
I had the same problem in my local deploy and I resolved it by setting |
I finally found the time to look at this issue and it raises some problems:
I am not entirely sure whether this is a sane change to make or if it's more bearable for administrators to adapt the script, which gets generated by the Director upon host creation. Feel free to share your thoughts on the situation, @MTSym @CanisLupusLupus @martialblog |
I went with external FQDN as Icinga2
But all three options (I am sure there are more possibilities, but those three are the simplest ones that I can think of off hand and with some light skimming of Icinga2 docs) increase complexity and fragility of deployment. |
Affected Chart
icinga-stack
Please describe your feature request
By default the endpoint address for the icinga2-master is, afaik, the fullname of the pod.
The problem with this is the generated "Agent" configurations which want to connect to the cluster internal address even if they are installed outside the cluster. By having the
host
value configurable it is possible to avoid this and the Agent scripts should be copy&paste again.The text was updated successfully, but these errors were encountered: