🥇Uqinisekiso kwiKubernetes usebenzisa iGitHub OAuth kunye neDex

Ndinikezela kwingqwalasela yakho isifundo sokwenza ufikelelo kwiqela leKubernetes usebenzisa iDex, dex-k8s-authenticator kunye neGitHub.

I-meme yasekhaya evela kwi-Kubernetes yolwimi lwesiRashiya incokole kuyo yocingo

Intshayelelo

Sisebenzisa i-Kubernetes ukudala iimeko eziguquguqukayo zophuhliso kunye neqela le-QA. Ke sifuna ukubanika ukufikelela kwiqela ledeshbhodi kunye ne kubectl. Ngokungafaniyo ne-OpenShift, i-vanilla Kubernetes ayinayo isiqinisekiso somthonyama, ke sisebenzisa izixhobo zomntu wesithathu koku.

Kolu lungelelwaniso sisebenzisa:

dex-k8s-isiqinisekisi — isicelo sewebhu sokwenza kubectl uqwalaselo
Dex —OpenID Connect umboneleli
I-GitHub-kuba sisebenzisa i-GitHub kwinkampani yethu

Sizamile ukusebenzisa iGoogle OIDC, kodwa ngelishwa thina isilele ukubaqala ngamaqela, ke udibaniso kunye neGitHub lusilungele kakuhle. Ngaphandle kwemephu yeqela, akunakwenzeka ukwenza imigaqo-nkqubo ye-RBAC esekelwe kumaqela.

Ke, isebenza njani inkqubo yethu yogunyaziso yeKubernetes kumboniso obonakalayo:

Inkqubo yogunyaziso

Ingcaciso encinci kunye nenqaku ngenqaku:

Umsebenzisi ungena kwi-dex-k8s-isiqinisekisi (login.k8s.example.com)
i-dex-k8s-authenticator idlulisela isicelo kwi-Dex (dex.k8s.example.com)
I-Dex iphinda iqondise kwiphepha lokungena le-GitHub
I-GitHub ivelisa ulwazi olugunyazisiweyo oluyimfuneko kwaye ibuyisele kwi-Dex
I-Dex idlulisela ulwazi olufunyenweyo kwi-dex-k8s-authenticator
Umsebenzisi ufumana ithokheni ye-OIDC esuka kwi-GitHub
dex-k8s-isiqinisekisi songeza uphawu kwi kubeconfig
kubectl igqithisa uphawu kwi KubeAPIServer
I-KubeAPIServer ibuyisela ufikelelo kwi-kubectl ngokusekwe kuphawu olugqithisiweyo
Umsebenzisi ufumana ukufikelela kwi kubectl

Imisebenzi yokulungiselela

Ewe, sele sineqela leKubernetes efakiweyo (k8s.example.com), kwaye iza ne-HELM efakwe ngaphambili. Sikwanayo nombutho kwiGitHub (super-org).
Ukuba awunayo i-HELM, yifake ilula kakhulu.

Okokuqala kufuneka sisete iGitHub.

Yiya kwiphepha lezicwangciso zombutho, (https://github.com/organizations/super-org/settings/applications) kwaye wenze isicelo esitsha (i-OAuth App eGunyaziweyo):

Ukwenza isicelo esitsha kwiGitHub

Gcwalisa iindawo ngee-URL eziyimfuneko, umzekelo:

I-URL yekhasi lasekhaya: https://dex.k8s.example.com
Ugunyaziso lokufowunela i-URL: https://dex.k8s.example.com/callback

Qaphela ngeekhonkco, kubalulekile ukuba ungalahlekelwa yi-slashs.

Ukuphendula kwifomu egqityiweyo, i-GitHub iya kuvelisa Client ID и Client secret, zigcine kwindawo ekhuselekileyo, ziya kuba luncedo kuthi (umzekelo, sisebenzisa igumbi elinqatyisiweyo lokugcina imali nezinto zexabiso yokugcina iimfihlo):

Client ID: 1ab2c3d4e5f6g7h8
Client secret: 98z76y54x32w1

Lungiselela iirekhodi zeDNS zesubdomains login.k8s.example.com и dex.k8s.example.com, kunye nezatifikethi ze-SSL zokungena.

Masenze izatifikethi ze-SSL:

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

I-ClusterIssuer enesihloko le-clusterissuer kufanele ukuba sele ikhona, kodwa ukuba akunjalo, yidale usebenzisa 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: [email protected]
    privateKeySecretRef:
      name: le-clusterissuer
    http01: {}
EOF

KubeAPIServer uqwalaselo

Ukuze kubeAPIServer isebenze, kufuneka uqwalasele i-OIDC kwaye uhlaziye iqela:

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

Sisebenzisa khaba ngokuhambisa amaqela, kodwa oku kusebenza ngokufanayo abanye abaphathi beqela.

Ubumbeko lwe-Dex kunye ne-dex-k8s-isiqinisekisi

Ukuze iDex isebenze, kufuneka ube nesatifikethi kunye nesitshixo esivela kwi-Kubernetes master, masiyifumane apho:

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

Masilinganise indawo yokugcina i-dex-k8s-yobunyani:

git clone [email protected]:mintel/dex-k8s-authenticator.git
cd dex-k8s-authenticator/

Ukusebenzisa iifayile zexabiso, sinokumisela ngokulula izinto eziguquguqukayo zethu Iitshathi ze-HELM.

Makhe sichaze ubumbeko lweDex:

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

Kwaye ye-dex-k8s-isiqinisekisi:

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

Faka i-Dex kunye ne-dex-k8s-isiqinisekisi:

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

Masijonge ukusebenza kweenkonzo (i-Dex kufuneka ibuyisele ikhowudi engu-400, kunye ne-dex-k8s-authenticator kufuneka ibuyisele ikhowudi engu-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

Uqwalaselo lwe-RBAC

Senza i-ClusterRole yeqela, kwimeko yethu ngofikelelo lokufunda kuphela:

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

Masenze uqwalaselo lwe-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

Ngoku sikulungele ukuvavanywa.

Iimvavanyo

Yiya kwiphepha lokungena (https://login.k8s.example.com) kwaye ungene usebenzisa iakhawunti yakho yeGitHub:

Iphepha lokungena

Iphepha lokungena liqondiswe kwi-GitHub

Landela imiyalelo eyenziweyo ukuze ufumane ufikelelo

Emva kokukopa-ukuncamathisela kwiphepha lewebhu, sinokusebenzisa kubectl ukulawula izixhobo zethu zeqela:

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 "[email protected]" cannot delete pods in the namespace "default"

Kwaye iyasebenza, bonke abasebenzisi beGitHub kumbutho wethu banokubona izixhobo kwaye bangene kwiipods, kodwa abanamalungelo okuzitshintsha.

umthombo: www.habr.com

Qinisekisa kwi-Kubernetes usebenzisa i-GitHub OAuth kunye ne-Dex