https://deploy-preview-3014--pinniped-dev.netlify.app/tags/matt-moyer/Recent content in Matt Moyer on PinnipedHugo -- gohugo.ioen-usFri, 30 Jul 2021 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/posts/supporting-remote-oidc-workflows/Fri, 30 Jul 2021 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/posts/supporting-remote-oidc-workflows/Photo by Jaddy Liu on Unsplash Remote Host Environments and OIDC login flows Enterprise workloads on Kubernetes clusters often run in a restricted environment behind a firewall. In such a setup, the clusters can be accessed via servers sometimes called “SSH jump hosts”. These servers pose restrictions on what the users can execute and typically allow only command line access. Users can use command line utilities such as kubectl, pinniped CLI, etc.https://deploy-preview-3014--pinniped-dev.netlify.app/posts/bringing-the-concierge-to-more-clusters/Thu, 01 Apr 2021 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/posts/bringing-the-concierge-to-more-clusters/Photo by Fred Heap on Unsplash Pinniped is a “batteries included” authentication system for Kubernetes clusters. With the release of v0.7.0, Pinniped now supports a much wider range of real-world Kubernetes clusters, including managed Kubernetes environments on all major cloud providers. This post describes how v0.7.0 fits into Pinniped’s quest to bring a smooth, unified login experience to all Kubernetes clusters. Authentication in Kubernetes Kubernetes includes a pluggable authentication system right out of the box.https://deploy-preview-3014--pinniped-dev.netlify.app/posts/multiple-pinnipeds/Thu, 04 Feb 2021 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/posts/multiple-pinnipeds/Photo by TRINH HUY HUNG on Unsplash Motivation Pinniped is a “batteries included” authentication system for Kubernetes clusters that tightly integrates with Kubernetes using native API patterns. Pinniped is built using custom resource definitions (CRDs) and API aggregation, both of which are core to the configuration and runtime operation of the app. We encountered a problem that’s familiar to many Kubernetes controller developers: we need to support multiple instances of our controller on one cluster.