Kubernetes Dashboard is a general-purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them and manage the cluster itself.

Spectro Proxy is a fast and straightforward reverse proxy that lets you forward a port of your local server behind a NAT or firewall to a public server. The proxy server pack is available as an add on pack for authentication. Users can attach this layer to the cluster profile while profile creation. This installs the FRP client in the workload clusters and configures it with a FRP server. Spectro Cloud provides hosts FRP server and by default the pack is configrued to connect to this server. Spectro Cloud detects the presence of this pack in the cluster and automatically updates the Kubeconfig file to use the FRP server as the endpoint. This section talks about how we can configure the Kubernetes Dashboard exposed to external traffic using Spectro Proxy pack, with RBAC authentication enabled.


  • Kubernetes Dashboard Pack to be part of the Cluster Profile.
  • To expose the dashboard, use Spectro-Proxy Pack (1.1.0) if Kubernetes Dashboard is not using LoadBalancer. Make the following changes to the Spectro-Proxy pack.

/ We enabled the k8sDashboard by making the enabled flag at line 4 to true.
enabled: true
useInsecurePort: false

  • OIDC authentication enabled for the cluster.

Quick Workflow:

  1. Create a cluster profile with required Infrastructure layers and Add-on layers per use case, in addition to the Kubernetes Dashboard Pack and Spectro-Proxy packs to the cluster profile as briefed in the Prerequisites.
  1. Enable OIDC authentication to the Kubernetes pack.
  1. Launch a new cluster using the cluster profile.
  1. Configure the Role Binding for the user. The two options available for Role Binding are:
  1. Now, from the cluster overview page of Palette UI, click connect to redirect to the IDP for authentication or dashboard if already authorized.
  1. The Palette Kubernetes Dashboard with Spectro-Proxy is ready for monitoring.

Enable OIDC Authentication

To enable OIDC authentication, make the following configuration to Kubernetes Pack:

Sample scenario

OIDC Related Configuration to Kubernetes Pack

## OIDC related config
identityProviderConfigName: 'Spectro-docs' # The name of the OIDC provider configuration
issuerUrl: 'issuer-url' # The URL of the OpenID identity provider
clientId: 'user-client-id-from-Palette' # The ID for the client application that makes authentication requests to the OpenID identity provider
usernameClaim: "email" # The JSON Web Token (JWT) claim to use as the username
usernamePrefix: "-" # The prefix that is prepended to username claims to prevent clashes with existing names
groupsClaim: "groups" # The JWT claim that the provider uses to return your groups
groupsPrefix: "" # The prefix that is prepended to group claims to prevent clashes with existing names
requiredClaims: # The key value pairs that describe required claims in the identity token

Client Configuration to Add OIDC Based Authentication in kubeconfig

## Client configuration to add OIDC based authentication flags in kubeconfig
oidc-issuer-url: "{{ .spectro.pack.kubernetes-eks.managedControlPlane.oidcIdentityProvider.issuerUrl }}"
oidc-client-id: "{{ .spectro.pack.kubernetes-eks.managedControlPlane.oidcIdentityProvider.clientId }}"
oidc-client-secret: client-secret-value
oidc-extra-scope: profile,email