Install the Pinniped 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.12.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.

Using kapp

1. Install the latest version of the Concierge into the pinniped-concierge namespace with default options using kapp:

   • kapp deploy --app pinniped-concierge --file https://get.pinniped.dev/v0.12.0/install-pinniped-concierge.yaml

Using kubectl

1. Install the latest version of the Concierge CustomResourceDefinitions:

   • kubectl apply -f https://get.pinniped.dev/v0.12.0/install-pinniped-concierge-crds.yaml

   This step is required so kubectl can validate the custom resources deployed in the next step.

2. Install the latest version of the Concierge into the pinniped-concierge namespace with default options:

   • kubectl apply -f https://get.pinniped.dev/v0.12.0/install-pinniped-concierge.yaml

With custom options

Pinniped uses ytt from Carvel as a templating system.

1. Install the ytt and kapp command-line tools using the instructions from the Carvel documentation.

2. Clone the Pinniped GitHub repository and visit the deploy/concierge directory:

   • git clone git@github.com:vmware-tanzu/pinniped.git
   • cd pinniped/deploy/concierge

3. Decide which release version you would like to install. All release versions are listed on GitHub.

4. Checkout your preferred version tag, e.g. v0.12.0.

   • git checkout v0.12.0

5. Customize configuration parameters:

   • See the default values for documentation about individual configuration parameters. For example, you can change the number of Concierge pods by setting replicas or apply custom annotations to the impersonation proxy service using impersonation_proxy_spec.

   • In a different directory, create a new YAML file to contain your site-specific configuration. For example, you might call this file site/dev-env.yaml.

     In the file, add the special ytt comment for a values file and the YAML triple-dash which starts a new YAML document. Then add custom overrides for any of the parameters from values.yaml.

     Override the image_tag value to match your preferred version tag, e.g. v0.12.0, to ensure that you use the version of the server which matches these templates.

     Here is an example which overrides the image tag, the default logging level, and the number of replicas:

     #@data/values
     ---
     image_tag: v0.12.0
     log_level: debug
     replicas: 1
     

   • Parameters for which you would like to use the default value should be excluded from this file.

   • If you are using a GitOps-style workflow to manage the installation of Pinniped, then you may wish to commit this new YAML file to your GitOps repository.

6. Render templated YAML manifests:

   • ytt --file . --file site/dev-env.yaml

   By putting the override file last in the list of --file options, it will override the default values.

7. Deploy the templated YAML manifests:

   • ytt --file . --file site/dev-env.yaml | kapp deploy --app pinniped-concierge --file -

Next steps

Next, configure the Concierge for JWT or webhook authentication, or configure the Concierge to use the Supervisor for authentication.