-
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]: Enable "check_by_ssh" functionality #22
Comments
Hi, thanks for your feature request. I gather you want to have dedicated values to add SSH keys to the Icinga deployment in order to run I don't get your request regarding the web user and its SSH identity, afaik |
Yeah having those keys in the values.yaml would be great. It would even be greater if they could be referenced as a kubernetes secret. About the With that |
Affected Chart
icinga-stack
Please describe your feature request
As machines which either do not have binaries for the agent or other circumstances exists it would be great if the functionality for "check_by_ssh" could be supported.
After checking the helm charts and templates I already found the
.Values.web_resources
variable which is not exposed in the defaultvalues.yml
which should allow to create the necessarySSH Identity
resource for the web user in combination with manually generating the ssh file on the shared volume.But the persistent volume of the
icingaweb
pod would have to also be mounted inside theicinga2
pods where the checks are made. Am I right?As a quickfix for people who are searching for a solution: It should be possible to use
kustomize
to generate the yaml files from helm and then usepatches
to add the additional env variables for the resource as well as the volume mountThe text was updated successfully, but these errors were encountered: