https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/Recent content in Pinniped how-to guides on PinnipedHugo -- gohugo.ioen-ushttps://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/debugging/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/debugging/Debugging on the Client The PINNIPED_DEBUG=true environment variable can be set to enable additional CLI logging. Debugging on the Server To adjust the log level of either the Pinniped Supervisor or the Pinniped Concierge the log level value must be updated in the appropriate configmap associated with each deployment. The log level options are as follows: info (“nice to know” information) debug (developer information) trace (timing information) all (kitchen sink) Do not use trace or all on production systems, as credentials may get logged.https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-cli/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-cli/The pinniped command-line tool is used to generate Pinniped-compatible kubeconfig files, and is also an important part of the Pinniped-based login flow. It must be installed by administrators setting up a Pinniped cluster as well as by users accessing a Pinniped-enabled cluster. Install using Homebrew on macOS or Linux Use Homebrew to install from the Pinniped tap: brew install vmware/pinniped/pinniped-cli Download binaries Find the appropriate binary for your platform from the latest release:https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-concierge/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-concierge/This guide shows you how to install the Pinniped Concierge. You should have a supported Kubernetes cluster. In the examples below, you can replace v0.45.0 with your preferred version number. You can find a list of Pinniped releases on GitHub. With default options Warning: the default Concierge configuration may create a public LoadBalancer Service on your cluster if that is the default on your cloud provider. If you’d prefer to customize the annotations or load balancer IP address, see the “With custom options” section below.https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-supervisor/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/install-supervisor/This guide shows you how to install the Pinniped Supervisor, which allows seamless login across one or many Kubernetes clusters. In the examples below, you can replace v0.45.0 with your preferred version number. You can find a list of Pinniped releases on GitHub. Prerequisites You should have a Kubernetes cluster with working HTTPS ingress or load balancer capabilities. Unlike the Concierge app, which can only run on supported Kubernetes cluster types, the Supervisor app can run on almost any Kubernetes cluster.https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/login/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/login/Prerequisites This how-to guide assumes that you have already configured the following Pinniped server-side components within your Kubernetes cluster(s): If you would like to use the Pinniped Supervisor for federated authentication across multiple Kubernetes clusters then you have already: Installed the Pinniped Supervisor with working ingress. Configured a FederationDomain to issue tokens for your downstream clusters. Configured an OIDCIdentityProvider, LDAPIdentityProvider, ActiveDirectoryIdentityProvider, or GitHubIdentityProvider for the Supervisor as the source of your user’s identities.https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/cicd/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/cicd/This guide shows you how to configure Pinniped so that your CI/CD system of choice can administrate Kubernetes clusters. Pinniped provides user authentication to Kubernetes clusters. It does not provide service-to-service (non-user) authentication. There are many other systems for service-to-service authentication in Kubernetes. If an organization prefers to manage CI/CD access with non-human user accounts in their external identity provider (IDP), Pinniped can provide authentication for those non-human user accounts. Humans can also use the same steps below to log into clusters non-interactively.https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/configure-auth-for-webapps/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-3014--pinniped-dev.netlify.app/docs/howto/configure-auth-for-webapps/The Pinniped Supervisor is an OpenID Connect (OIDC) issuer that can be used to bring your user identities from an external identity provider into your Kubernetes clusters for all your kubectl users. It can also be used to bring those same identities to web applications that are intended for use by the same users. For example, a Kubernetes dashboard web application for cluster developers could use the Supervisor as its OIDC identity provider.