Frequently Asked Questions (FAQ)
Yes. Infra is distributed under two licenses:
- The MIT license (for the CLI and agent)
- The Elastic license (for the core API server)
Most cloud services use built-in auth mechanisms that rely on passwords or static credentials.
Not all Infrastructure support OIDC. Infra uses credential vaulting to create short-lived tokens with the same properties of a certificate or JWT token.
Unlike Teleport and other access proxy tools, Infra doesn't proxy traffic or use encrypted tunnels. Infra is designed to be used as an authentication mechanism alongside existing networking tools such as OpenVPN, Tailscale or others.
We do! See status.infrahq.com.
Although the Infra connector will install with a minimum of settings in the Helm values file, you will also need to set the health check options. Refer to the Kubernetes page for more.
Depending on which cloud provider is hosting your cluster, it may take a few minutes for a Load Balancer to be configured.