Icinga2/Icingaweb2/Director Multi-Tenant Setup

I’m running into a few issues and hoping someone can help clarify or provide advice on this, I am interested in setting up a single Icinga2 cluster to be used by several teams restricted to their own Hosts/Services in order to save resources.

Problems so far:

  1. I can restrict a users access to a specific HostGroup lets say ‘HostGroupA’ in Icingaweb2, but those users are allowed to create checks that are applied and run on ‘HostGroupB’.
  2. Is there a way I can run multiple Icinga2 Masters on a single container? Without this option the next question does not matter.
  3. I can use director to deploy to different Icinga2 instances, however I do not see a way in Icingaweb2 to limit a users access to a specific deployment in Director.

Thank you for your input.

  • Nate S
1 Like

I’m also interested in this type of setup, would be nice if we will be able to isolate user environments.

Typical use cases:

  • We have 1 cluster and bunch of independent small teams with 10-50 hosts each
  • We have prod/dev/staging environment on the same installation