sso-operator
Single Sign-On Kubernetes operator for dex, which can provision, expose and manage a SSO proxy for a Kubernetes service.
Architecture
Installation
Using Jenkins X
You can install the operator and its dependencies with Jenkins X. The only requirement is to have already allocated a DNS domain for your ingress controller.
You can execute the command bellow and then follow the wizard steps:
jx create addon sso
Using Helm
Prerequisites
The operator requires the dex identity provider and the cert-manager version v.0.6.0
to be installed into your cluster.
You can install dex
using following helm chart, which pre-configures the GitHub connector
, and uses the cert-manager
service to retrieve
the TLS certificates for dex gRPC API.
Before starting the installation, you have to create a GitHub OAuth App which should have as callback
the https://DEX_DOMAIN/callback URL.
You can install the dex
chart as follows:
helm upgrade -i --namespace <NAMESAPCE> --wait --timeout 600 dex \
--set domain="<DEX_DOMAIN>" \
--set connectors.github.config.clientID="<CLIENT_ID>" \
--set connectors.github.config.clientSecret="<CLIENT_SECRET>" \
--set connectors.github.config.orgs={ORG1,ORG2} \
.
The web endpoints provided by dex
IdP have to be publicly exposed and secured with TLS. You can do this pretty easy, if you have the Jenkins X installed into your cluster.
Just executing the command:
jx upgrade ingress
You can select TLS and provide your DEX_DOMAIN
and email. This command will configure the ingress controller to fetch automatically the TLS certificate from Let's Encrypt CA server.
Install the operator
First, you will need to add the jenkins-x chart repository to your helm repositories:
helm repo add jenkins-x http://chartmuseum.jenkins-x.io
helm repo update
You can now install the chart with:
helm install --namespace <NAMESPACE> --set dex.grpcHost=dex.<DEX_NAMESPACE> --name sso-operator jenkins-x/sso-operator
Enable Single Sign-On for a service
After installing the operator, you can enable Single Sign-On for any Kubernetes service by creating a SSO custom resource.
Let's start by creating a basic Go http service with Jenkins X:
jx create quickstart -l Go --name golang-http
Within a few minutes, the service should be running in your staging environment. You can view the Kubernetes service created for it with:
kubectl get svc -n jx-staging
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
golang-http ClusterIP 10.15.250.117 <none> 80/TCP 1m
sso-operator ClusterIP 10.15.244.220 <none> 80/TCP 6m
You can enable now the Single Sign-On for this service by creating a custom resource as follows:
cat <<EOF | kubectl create -f -
apiVersion: "jenkins.io/v1"
kind: "SSO"
metadata:
name: "sso-golang-http"
namespace: jx-staging
spec:
oidcIssuerUrl: "https://dex.jx-staging.example.com"
upstreamService: "golang-http"
forwardToken: false
domain: "example.com"
certIssuerName: "letsencrypt-prod"
urlTemplate: "{{.Service}}.{{.Namespace}}.{{.Domain}}"
cookieSpec:
name: "sso-golang-http"
expire: "168h"
refresh: "60m"
secure: true
httpOnly: true
proxyImage: "quay.io/pusher/oauth2_proxy"
proxyImageTag: "3.1.0"
proxyResources:
limits:
cpu: 100m
memory: 256Mi
requests:
cpu: 80m
memory: 128Mi
EOF
Note: You will have to update oidcIssuerUrl and domain with your specific values.
A SSO proxy will be automatically created by the operator and publicly exposed under your domain with TLS enabled. You can see the proxy URL with:
kubectl get ingress -n jx-staging
NAME HOSTS ADDRESS PORTS AGE
sso-golang-http sso-golang-http.jx-staging.example.com 104.155.7.81 80, 443 37m
You can open now the https://sso-golang-http.jx-staging.example.com
URL in a browser and check if Single Sign-On works with your GitHub user.