kubelogin
inspektor-gadget
kubelogin | inspektor-gadget | |
---|---|---|
14 | 8 | |
1,566 | 1,997 | |
- | 3.3% | |
8.8 | 9.9 | |
8 days ago | 3 days ago | |
Go | C | |
Apache License 2.0 | 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.
kubelogin
-
Giving Kyma a little spin ... a SpinKube
Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.
-
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.
-
Gitlab token exchange with keycloak to execute deployments with kubectl
I've successfully configured kube-apiserver to authenticate users through oidc (https://github.com/int128/kubelogin) so all the users from my keycloak realm can access to the cluster with their credentials.
-
Getting started with kubectl plugins
Link to GitHub Repository
-
Why are there so many OIDC SSO options for Kubernetes?
kubelogin (helper for k8s build in OIDC support)
-
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.
-
Manage user authentication in on-prem cluster
Dex oauth and kubelogin. We happen to use google auth in our org, but dex is pretty flexible. You only have to have a way to distribute server certificates. We then have documented script commands to pull certs and create kubectl fig files. OpenUnison always looked interesting, but dex has been good enough for our uses.
-
k8s dex authentications
With a working dex/OIDC configuration, you could use: https://github.com/int128/kubelogin
- A kubectl plugin for Kubernetes OpenID Connect (OIDC) authentication
inspektor-gadget
-
Running tcpdump on eks worker nodes
You can try using https://www.inspektor-gadget.io/ You can try either, top tcp, trace network-graph or trace tcp gadget. It's a CNCF sandbox project and it's kubernetes native so I think this should work.
-
Is there any OSS tool out there that would translate traffic flows into NetworkPolicies?
This works really well https://github.com/inspektor-gadget/inspektor-gadget/blob/main/docs/gadgets/advise/network-policy.md
-
Getting started with kubectl plugins
Link to GitHub Repository
-
Isolating Kubernetes pods for debugging
Inspector gadget is a tool designed to introspect and debug Kubernetes applications using eBPF.
-
What are some useful Kubernetes tools you can share?
I found this tool: https://github.com/kinvolk/inspektor-gadget great if you want to have a detailed debugging for running pods e.g all exec system calls or trace tcp connections etc.
- Inspektor Gadget
-
Kubernetes Security Checklist 2021
All namespaces should have NetworkPolicy. Interactions between namespaces should be limited to NetworkPolicy following least privileges principles (Inspektor Gadget)
-
How to Trace Linux System Calls in Production with Minimal Impact on Performance
The team behind traceloop has integrated it with the Inspektor Gadget project, so you can run traceloop on the K8s platform using kubectl. See the demos in Inspektor Gadget - How to use and, if you like, try it on your own.
What are some alternatives?
lens - Lens - The way the world runs Kubernetes
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
pam-keycloak-oidc - PAM module connecting to Keycloak for user authentication using OpenID Connect/OAuth2, with MFA/2FA/TOTP support
falco - Cloud Native Runtime Security
kubectl-neat - Clean up Kubernetes yaml and json output to make it readable
Flatcar - Flatcar project repository for issue tracking, project documentation, etc.
okta-k8s-oidc-terraform-example - An example repo showcasing setting up Okta OIDC using Terraform
kubesess - Kubectl plugin managing sessions
kubectl-kubesec - Security risk analysis for Kubernetes resources
security-profiles-operator - The Kubernetes Security Profiles Operator
ksniff - Kubectl plugin to ease sniffing on kubernetes pods using tcpdump and wireshark
go2seccomp - Generate seccomp profiles from go binaries