🥇Autentifikacija u Kubernetesu s GitHub OAuth i Dex

Predstavljam vam vodič za generiranje pristupa Kubernetes klasteru koristeći Dex, dex-k8s-authenticator i GitHub.

Lokalni meme iz Kubernetes chata na ruskom jeziku Telegram

Uvod

Koristimo Kubernetes za stvaranje dinamičnih okruženja za razvojni i QA tim. Stoga im želimo dati pristup klasteru i za nadzornu ploču i za kubectl. Za razliku od OpenShift-a, vanilija Kubernetes nema izvornu autentifikaciju, pa za to koristimo alate trećih strana.

U ovoj konfiguraciji koristimo:

dex-k8s-autentifikator — web aplikacija za generiranje kubectl konfiguracije
Dex — OpenID Connect pružatelj usluga
GitHub - jednostavno zato što koristimo GitHub u našoj tvrtki

Pokušali smo koristiti Google OIDC, ali nažalost nije uspio pokrenuti ih s grupama, tako da nam je integracija s GitHubom sasvim dobro legla. Bez grupnog mapiranja neće biti moguće kreirati RBAC politike na temelju grupa.

Dakle, kako naš Kubernetes postupak autorizacije funkcionira u vizualnom prikazu:

Proces autorizacije

Malo detaljnije i točku po točku:

Korisnik se prijavljuje u dex-k8s-authenticator (login.k8s.example.com)
dex-k8s-authenticator prosljeđuje zahtjev Dexu (dex.k8s.example.com)
Dex preusmjerava na GitHub stranicu za prijavu
GitHub generira potrebne podatke za autorizaciju i vraća ih Dexu
Dex prosljeđuje primljene informacije dex-k8s-autentifikatoru
Korisnik dobiva OIDC token od GitHuba
dex-k8s-authenticator dodaje token u kubeconfig
kubectl prosljeđuje token KubeAPIServeru
KubeAPIServer vraća pristupe kubectl-u na temelju proslijeđenog tokena
Korisnik dobiva pristup iz kubectl

Pripremne aktivnosti

Naravno, već imamo instaliran Kubernetes klaster (k8s.example.com), a dolazi i s unaprijed instaliranim HELM-om. Imamo i organizaciju na GitHubu (super-org).
Ako nemate HELM, instalirajte ga vrlo jednostavan.

Prvo moramo postaviti GitHub.

Idite na stranicu postavki organizacije, (https://github.com/organizations/super-org/settings/applications) i izradite novu aplikaciju (Authorized OAuth App):

Izrada nove aplikacije na GitHubu

Ispunite polja s potrebnim URL-ovima, na primjer:

URL početne stranice: https://dex.k8s.example.com
URL povratnog poziva autorizacije: https://dex.k8s.example.com/callback

Budite oprezni s linkovima, važno je da ne izgubite kose crte.

Kao odgovor na ispunjen obrazac, GitHub će generirati Client ID и Client secret, čuvajte ih na sigurnom mjestu, bit će nam korisni (na primjer, koristimo svod za čuvanje tajni):

Client ID: 1ab2c3d4e5f6g7h8
Client secret: 98z76y54x32w1

Pripremite DNS zapise za poddomene login.k8s.example.com и dex.k8s.example.com, kao i SSL certifikate za ulaz.

Kreirajmo SSL certifikate:

cat <<EOF | kubectl create -f -
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: cert-auth-dex
  namespace: kube-system
spec:
  secretName: cert-auth-dex
  dnsNames:
    - dex.k8s.example.com
  acme:
    config:
    - http01:
        ingressClass: nginx
      domains:
      - dex.k8s.example.com
  issuerRef:
    name: le-clusterissuer
    kind: ClusterIssuer
---
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: cert-auth-login
  namespace: kube-system
spec:
  secretName: cert-auth-login
  dnsNames:
    - login.k8s.example.com
  acme:
    config:
    - http01:
        ingressClass: nginx
      domains:
      - login.k8s.example.com
  issuerRef:
    name: le-clusterissuer
    kind: ClusterIssuer
EOF
kubectl describe certificates cert-auth-dex -n kube-system
kubectl describe certificates cert-auth-login -n kube-system

ClusterIssuer s naslovom le-clusterissuer već bi trebao postojati, ali ako ne, stvorite ga koristeći HELM:

helm install --namespace kube-system -n cert-manager stable/cert-manager
cat << EOF | kubectl create -f -
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
  name: le-clusterissuer
  namespace: kube-system
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email: k8s-admin@example.com
    privateKeySecretRef:
      name: le-clusterissuer
    http01: {}
EOF

Konfiguracija KubeAPIServera

Da bi kubeAPIServer radio, trebate konfigurirati OIDC i ažurirati klaster:

kops edit cluster
...
  kubeAPIServer:
    anonymousAuth: false
    authorizationMode: RBAC
    oidcClientID: dex-k8s-authenticator
    oidcGroupsClaim: groups
    oidcIssuerURL: https://dex.k8s.example.com/
    oidcUsernameClaim: email
kops update cluster --yes
kops rolling-update cluster --yes

Koristimo udarac nogom za implementaciju klastera, ali ovo radi slično za drugi upravitelji klastera.

Dex konfiguracija i dex-k8s-autentifikator

Da bi Dex radio, trebate imati certifikat i ključ od Kubernetes mastera, idemo dalje:

sudo cat /srv/kubernetes/ca.{crt,key}
-----BEGIN CERTIFICATE-----
AAAAAAAAAAABBBBBBBBBBCCCCCC
-----END CERTIFICATE-----
-----BEGIN RSA PRIVATE KEY-----
DDDDDDDDDDDEEEEEEEEEEFFFFFF
-----END RSA PRIVATE KEY-----

Klonirajmo repozitorij dex-k8s-authenticator:

git clone git@github.com:mintel/dex-k8s-authenticator.git
cd dex-k8s-authenticator/

Pomoću datoteka s vrijednostima možemo fleksibilno konfigurirati varijable za naše HELM karte.

Opišimo konfiguraciju za Dex:

cat << EOF > values-dex.yml
global:
  deployEnv: prod
tls:
  certificate: |-
    -----BEGIN CERTIFICATE-----
    AAAAAAAAAAABBBBBBBBBBCCCCCC
    -----END CERTIFICATE-----
  key: |-
    -----BEGIN RSA PRIVATE KEY-----
    DDDDDDDDDDDEEEEEEEEEEFFFFFF
    -----END RSA PRIVATE KEY-----
ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
  path: /
  hosts:
    - dex.k8s.example.com
  tls:
    - secretName: cert-auth-dex
      hosts:
        - dex.k8s.example.com
serviceAccount:
  create: true
  name: dex-auth-sa
config: |
  issuer: https://dex.k8s.example.com/
  storage: # https://github.com/dexidp/dex/issues/798
    type: sqlite3
    config:
      file: /var/dex.db
  web:
    http: 0.0.0.0:5556
  frontend:
    theme: "coreos"
    issuer: "Example Co"
    issuerUrl: "https://example.com"
    logoUrl: https://example.com/images/logo-250x25.png
  expiry:
    signingKeys: "6h"
    idTokens: "24h"
  logger:
    level: debug
    format: json
  oauth2:
    responseTypes: ["code", "token", "id_token"]
    skipApprovalScreen: true
  connectors:
  - type: github
    id: github
    name: GitHub
    config:
      clientID: $GITHUB_CLIENT_ID
      clientSecret: $GITHUB_CLIENT_SECRET
      redirectURI: https://dex.k8s.example.com/callback
      orgs:
      - name: super-org
        teams:
        - team-red
  staticClients:
  - id: dex-k8s-authenticator
    name: dex-k8s-authenticator
    secret: generatedLongRandomPhrase
    redirectURIs:
      - https://login.k8s.example.com/callback/
envSecrets:
  GITHUB_CLIENT_ID: "1ab2c3d4e5f6g7h8"
  GITHUB_CLIENT_SECRET: "98z76y54x32w1"
EOF

I za dex-k8s-autentifikator:

cat << EOF > values-auth.yml
global:
  deployEnv: prod
dexK8sAuthenticator:
  clusters:
  - name: k8s.example.com
    short_description: "k8s cluster"
    description: "Kubernetes cluster"
    issuer: https://dex.k8s.example.com/
    k8s_master_uri: https://api.k8s.example.com
    client_id: dex-k8s-authenticator
    client_secret: generatedLongRandomPhrase
    redirect_uri: https://login.k8s.example.com/callback/
    k8s_ca_pem: |
      -----BEGIN CERTIFICATE-----
      AAAAAAAAAAABBBBBBBBBBCCCCCC
      -----END CERTIFICATE-----
ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
  path: /
  hosts:
    - login.k8s.example.com
  tls:
    - secretName: cert-auth-login
      hosts:
        - login.k8s.example.com
EOF

Instalirajte Dex i dex-k8s-authenticator:

helm install -n dex --namespace kube-system --values values-dex.yml charts/dex
helm install -n dex-auth --namespace kube-system --values values-auth.yml charts/dex-k8s-authenticator

Provjerimo funkcionalnost servisa (Dex bi trebao vratiti kod 400, a dex-k8s-authenticator trebao bi vratiti kod 200):

curl -sI https://dex.k8s.example.com/callback | head -1
HTTP/2 400
curl -sI https://login.k8s.example.com/ | head -1
HTTP/2 200

RBAC konfiguracija

Kreiramo ClusterRole za grupu, u našem slučaju s pristupom samo za čitanje:

cat << EOF | kubectl create -f -
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: cluster-read-all
rules:
  -
    apiGroups:
      - ""
      - apps
      - autoscaling
      - batch
      - extensions
      - policy
      - rbac.authorization.k8s.io
      - storage.k8s.io
    resources:
      - componentstatuses
      - configmaps
      - cronjobs
      - daemonsets
      - deployments
      - events
      - endpoints
      - horizontalpodautoscalers
      - ingress
      - ingresses
      - jobs
      - limitranges
      - namespaces
      - nodes
      - pods
      - pods/log
      - pods/exec
      - persistentvolumes
      - persistentvolumeclaims
      - resourcequotas
      - replicasets
      - replicationcontrollers
      - serviceaccounts
      - services
      - statefulsets
      - storageclasses
      - clusterroles
      - roles
    verbs:
      - get
      - watch
      - list
  - nonResourceURLs: ["*"]
    verbs:
      - get
      - watch
      - list
  - apiGroups: [""]
    resources: ["pods/exec"]
    verbs: ["create"]
EOF

Kreirajmo konfiguraciju za ClusterRoleBinding:

cat <<EOF | kubectl create -f -
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: dex-cluster-auth
  namespace: kube-system
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-read-all
subjects:
  kind: Group
  name: "super-org:team-red"
EOF

Sada smo spremni za testiranje.

testovi

Idite na stranicu za prijavu (https://login.k8s.example.com) i prijavite se koristeći svoj GitHub račun:

Stranica za prijavu

Stranica za prijavu preusmjerena je na GitHub

Slijedite generirane upute za pristup

Nakon kopiranja i lijepljenja s web stranice, možemo koristiti kubectl za upravljanje našim resursima klastera:

kubectl get po
NAME                READY   STATUS    RESTARTS   AGE
mypod               1/1     Running   0          3d

kubectl delete po mypod
Error from server (Forbidden): pods "mypod" is forbidden: User "amet@example.com" cannot delete pods in the namespace "default"

I radi, svi korisnici GitHuba u našoj organizaciji mogu vidjeti resurse i prijaviti se u module, ali nemaju prava mijenjati ih.

Izvor: www.habr.com