Pinniped auth fails after identity provider certificate/config change

Products

• Tanzu Kubernetes Grid
• VMware Tanzu Kubernetes Grid
• VMware Tanzu Kubernetes Grid Management
• VMware Tanzu Kubernetes Grid Plus
• VMware Tanzu Kubernetes Grid Service (TKGs)

Issue/Introduction

After updating TKGm Pinniped IDP cert or config following the TKGm 2.5 docs you notice ldap auth fails or pinniped responds with 500 server errors.

Environment

Tanzu Kubernetes Grid Management(TKGm) 2.x

Cause

After changing the Pinniped config some of the old config can be left cached in the running Pinniped deployment pods causing the changes to not take effect.

Resolution

Restart the Pinniped supervisor pods to propagate any changes made to the config.