Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
21–30 of 59 posts
Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#22I use rancher for this purpose alone (it can connect to okta, azure, local users...). I might consider using this with its plan to integrate more infra like databases and ssh. For ssh though I'm not sure it could easily replace FreeIPA, unless it integrates with it somehow.
Infra's designed to integrate with existing identity & access tooling (vs replace them). While we don't have a built-in integration for FreeIPA, Infra has a REST API and will integrate with any OpenID-compliant identity provider, meaning you shouldn't have to drop or replace your existing tooling to start using Infra.
Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#23Earlier quoted context omitted.
does the standard deployment use a centralized proxy? like it's your Basic Architecture in the diagram in your docs. so i feel like i'm being put on.
Sorry you feel that way! We haven't counted, but my bet is that most smaller deployments just use the single proxy. I also know that most larger deployments use multi-DC and multi-cluster design with independent CAs for availability and latency.
Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#24Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#25Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#26Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#27Re: Launch HN: Infra (YC W21) – Open-source access management for Kubernetes
#28Just went through the quickstart and that's some top-notch developer experience, great job.