Skip to content
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

Allow passing Ticketsalts for ticket generation #211

Closed
mocdaniel opened this issue Nov 15, 2023 · 0 comments · Fixed by #222 or #250
Closed

Allow passing Ticketsalts for ticket generation #211

mocdaniel opened this issue Nov 15, 2023 · 0 comments · Fixed by #222 or #250
Milestone

Comments

@mocdaniel
Copy link
Contributor

mocdaniel commented Nov 15, 2023

In some environments, agents can't directly connect to the cluster's masters. In those situation, cluster onboarding (e.g. ticket generation) gets delegated to satellites. This is already possible, using icinga2_delegate_host.

However, for this to work, the satellite needs to have the TicketSalt of the master system(s) configured in order to calculate a valid ticket. This exposes the TicketSalt unnecessarily, as it gets persisted on the agent's file system.

Also, when provisioning for the first time, the passed TicketSalt hasn't been loaded into Icinga2's running state yet, and below command actually fails, leaving the instance in kind of a limbo.

However, it's possible to pass the TicketSalt to the CLI command being issued by Ansible in this situation:

icinga2 pki ticket --salt <salt_goes_here> --cn mocdaniel.example.com

Could we introduce another variable, e.g. delegated_ticket_salt, that allows us to only expose the TicketSalt during provisioning satellites/agents via Ansible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant