infra
kube-oidc-proxy
Our great sponsors
infra | kube-oidc-proxy | |
---|---|---|
20 | 5 | |
1,350 | 474 | |
0.8% | 3.2% | |
7.4 | 1.8 | |
7 days ago | 9 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
infra
-
Recommendations for a better way to grant access in K8s on a granular level?
Check out https://infrahq.com. I saw the founder give a talk at the Civo conference in Feb.
-
infra alternatives - paralus and pinniped
3 projects | 7 Apr 2023
-
Converting http.Request to gin.Context struct
using generics you can even include request and response structs in your handlers. i did that here https://github.com/infrahq/infra/blob/main/internal/server/routes.go
-
Why are there so many OIDC SSO options for Kubernetes?
infra
-
RBAC MANAGEMENT
You should try Infra. It works with any flavor of Kube and can hook up Okta, Google, and AD (and anything that supports OpenID Connect). It can pull in your cluster/roles, and set up the cluster/role bindings. It's open source, although there is also a SaaS version if you don't want to self host.
-
Have you used generics?
I use them frequently. see https://github.com/infrahq/infra/blob/main/internal/server/routes.go
-
Infra: open source access management for Kubernetes
Github repo: https://github.com/infrahq/infra
- Infra: self-hosted access management
-
Anyone needs a (long-term) contributor for their open source project written in Go?
if you like Go and backend/infrastructure you might like https://github.com/infrahq/infra. it’s simple identity and access management for kubernetes (and eventually others).
-
The funny thing about generics in Go
not sure what you’re talking about. we use generics extensively and love it. https://github.com/infrahq/infra
kube-oidc-proxy
-
Windows auth with K8s on prem
It is sort of a roundabout way, but I sync Active Directory to a Keycloak realm, then use OIDC auth with kube-oidc-proxy (https://github.com/jetstack/kube-oidc-proxy) and kubelogin (https://github.com/int128/kubelogin) for OIDC-based auth to the api server.
-
Kubernetes in production.
Yes, I setup a cluster with no SPFs. That means an HA setup for the external load balancer. I use HAProxy for my ELB, and setup 2 instances with a VRRP + keepalived to provide HA to the ingress controller. I run the control plane private, accessible only from localhost. I setup kube-oidc-proxy (https://github.com/jetstack/kube-oidc-proxy) to expose the API server with single sign-on on the ingress controller, and use the kubelogin plugin (https://github.com/int128/kubelogin) to provide OIDC support to kubectl. I then setup Keycloak to handle OIDC/OAuth2/SAML and syncing to Active Directory, and setup groups in Active Directory to control acccess to clusters. Devs each get their own namespace in the dev cluster, with mostly cluster-admin access to their namespace. Staging/Prod clusters are locked down, with read-only access to devs. Thanks to the OIDC auth to the APIServer, when employees are onboarded & offboarded, we only need to add/remove them from groups in Active Directory and everything else just magically syncs.
-
Why are there so many OIDC SSO options for Kubernetes?
kube-oidc-proxy (OIDC to Kubernetes API servers where OIDC authentication is not available)
-
RBAC MANAGEMENT
I use the kube-login plugin for kubectl (https://github.com/int128/kubelogin) along with the kube-oidc-proxy (https://github.com/jetstack/kube-oidc-proxy), using Keycloak as my OIDC provider (https://www.keycloak.org) and doing LDAP synchronization to Active Directory.
-
What is the biggest challenge you/your org faces while running k8s in production?
We use Keycloak for this purpose. We deploy an OIDC-proxy to the kube-api (https://github.com/jetstack/kube-oidc-proxy), then use the kubectl plugin 'kubelogin' (aka oidc-login if you use krew - https://github.com/int128/kubelogin). This gives us the ability to have no user secrets in our KUBECONFIG, and to use Keycloak's Active Directory/LDAP user & group federation to control access to clusters. With this, downloading the KUBECONFIG is self-service, and adding users to new clusters is as easy as adding them to a group in AD.
What are some alternatives?
pinniped - Pinniped is the easy, secure way to log in to your Kubernetes clusters.
kubelogin - kubectl plugin for Kubernetes OpenID Connect authentication (kubectl oidc-login)
scan - Scan provides the ability to to scan sql rows directly to any defined structure.
graph - A library for creating generic graph data structures and modifying, analyzing, and visualizing them.
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
aws-iam-authenticator - A tool to use AWS IAM credentials to authenticate to a Kubernetes cluster
lens - Lens - The way the world runs Kubernetes
dex - OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors
authentik - The authentication glue you need.
gosf-socketio - golang socket.io client and server
paralus - All-in-one Kubernetes access manager. User-level credentials, RBAC, SSO, audit logs.