Thanks for the note — would love to hear what infrastructure outside of Kubernetes you’d like to connect to, so I can target the answer more specifically.
For expanding to infrastructure outside of Kubernetes, we will ultimately generating short-lived credentials from and distributing them to either humans or machine users. This can be done through different means, and we’ll select the best method for that infrastructure.
1. With where we want to take Infra, we want to enable teams to build an access system using the principles of least privilege so statically users can have a minimal permission (or no permission), and when access is needed, dynamically provision that access (automatic or manual approval depending on configuration). Infra will always be able to show who has access to what at any given time to satisfy audits.
Infra is currently self-hosted, and we will definitely be taking it through compliance audits & penetration tests (including SOC 2) as we mature the project.
2. Yes, we love desktop apps - starting from the early versions of Kite we've built, Kitematic, Docker desktop, and Infra app. We believe good software just works in the background without affecting users' flow.
3. We’ve already tried using both Google workspaces / Azure active directory via OIDC. It should work. We’re just not pitching it because we have not done extensive testing with it yet. I should note, Infra is OIDC-compliant, so it should work with any custom identity providers that support OIDC. (I will asterisk it because one OIDC-compliant provider may differ from another, even from a major vendor)
For expanding to infrastructure outside of Kubernetes, we will ultimately generating short-lived credentials from and distributing them to either humans or machine users. This can be done through different means, and we’ll select the best method for that infrastructure.
1. With where we want to take Infra, we want to enable teams to build an access system using the principles of least privilege so statically users can have a minimal permission (or no permission), and when access is needed, dynamically provision that access (automatic or manual approval depending on configuration). Infra will always be able to show who has access to what at any given time to satisfy audits.
Infra is currently self-hosted, and we will definitely be taking it through compliance audits & penetration tests (including SOC 2) as we mature the project.
2. Yes, we love desktop apps - starting from the early versions of Kite we've built, Kitematic, Docker desktop, and Infra app. We believe good software just works in the background without affecting users' flow.
3. We’ve already tried using both Google workspaces / Azure active directory via OIDC. It should work. We’re just not pitching it because we have not done extensive testing with it yet. I should note, Infra is OIDC-compliant, so it should work with any custom identity providers that support OIDC. (I will asterisk it because one OIDC-compliant provider may differ from another, even from a major vendor)