ProHoster > Blog > Rianachd > Dearbhadh Kubernetes le GitHub OAuth agus Dex

Dearbhadh Kubernetes le GitHub OAuth agus Dex

Bidh mi a’ toirt dhut oideachadh airson a bhith a’ gineadh ruigsinneachd gu cruinneachadh Kubernetes a’ cleachdadh Dex, dex-k8s-authenticator agus GitHub.

Dearbhadh Kubernetes le GitHub OAuth agus Dex
Meme ionadail bhon chat ann an cànan na Ruis Kubernetes teileagram

Ro-ràdh

Bidh sinn a’ cleachdadh Kubernetes gus àrainneachdan fiùghantach a chruthachadh airson an sgioba leasachaidh agus QA. Mar sin tha sinn airson cothrom a thoirt dhaibh faighinn chun bhuidheann airson an deas-bhòrd agus kubectl. Eu-coltach ris an aon OpenShift, chan eil dearbhadh dùthchasach aig vanilla Kubernetes, agus mar sin bidh sinn a’ cleachdadh innealan treas-phàrtaidh airson seo.

Anns an rèiteachadh seo bidh sinn a’ cleachdadh:

  • dex-k8s-dearbhaidh  - tagradh lìn airson kubectl config a ghineadh
  • Deasg - Solaraiche OpenID Connect
  • GitHub - dìreach air sgàth gu bheil sinn a’ cleachdadh GitHub nar companaidh

Dh'fheuch sinn ri Google OIDC a chleachdadh, ach gu mì-fhortanach tha sinn fàilligeadh gus an tòiseachadh le buidhnean, agus mar sin bha an aonachadh le GitHub freagarrach dhuinn gu math. Às aonais mapadh buidhne, cha bhith e comasach poileasaidhean RBAC a chruthachadh stèidhichte air buidheann.

Mar sin, ciamar a tha ar pròiseas ceadachaidh Kubernetes ag obair ann an riochdachadh lèirsinneach:

Dearbhadh Kubernetes le GitHub OAuth agus Dex
Pròiseas ceadachaidh

Beagan a bharrachd mion-fhiosrachaidh agus puing air puing:

  1. Bidh cleachdaiche a’ logadh a-steach do dex-k8s-authenticator (login.k8s.example.com)
  2. dex-k8s-authenticator ag ath-stiùireadh an iarrtais gu Dex (dex.k8s.example.com)
  3. Bidh Dex ag ath-stiùireadh gu duilleag logadh a-steach GitHub
  4. Bidh GitHub a’ gineadh am fiosrachadh ùghdarrais a tha a dhìth agus ga thilleadh gu Dex
  5. Bidh Dex a’ toirt seachad an fhiosrachaidh a fhuaireadh gu dex-k8s-authenticator
  6. Bidh cleachdaiche a’ faighinn tòcan OIDC bho GitHub
  7. dex-k8s-authenticator a’ cur tòcan ri kubeconfig
  8. kubectl a’ dol seachad air tòcan gu KubeAPIServer
  9. Bidh KubeAPIServer stèidhichte air an tòcan a chaidh seachad a’ tilleadh ruigsinneachd gu kubectl
  10. Ruigsinneachd luchd-cleachdaidh bho kubectl

Gnìomhan ullachaidh

Gu dearbh, tha cruinneachadh Kubernetes againn mu thràth air a chuir a-steach (k8s.example.com), a bharrachd air HELM ro-stàlaichte. Tha buidheann againn cuideachd air GitHub (super-org).
Mura h-eil HELM agad, stàlaich e gu math sìmplidh.

An toiseach feumaidh sinn GitHub a stèidheachadh.

Rach gu duilleag roghainnean na buidhne, (https://github.com/organizations/super-org/settings/applications) agus cruthaich tagradh ùr (App OAuth Ùghdarraichte):
Dearbhadh Kubernetes le GitHub OAuth agus Dex
Cruthaich app ùr air GitHub

Lìon a-steach na raointean leis na URLan riatanach, mar eisimpleir:

  • URL na duilleige-dachaigh: https://dex.k8s.example.com
  • URL fios air ais ceadachaidh: https://dex.k8s.example.com/callback

Bi faiceallach le ceanglaichean, tha e cudromach gun a bhith a 'call slashes.

Mar fhreagairt don fhoirm chrìochnaichte, ginidh GitHub Client ID и Client secret, sàbhail iad ann an àite sàbhailte, bidh iad feumail dhuinn (mar eisimpleir, bidh sinn a 'cleachdadh Bùrn airson dìomhaireachdan a chumail):

Client ID: 1ab2c3d4e5f6g7h8
Client secret: 98z76y54x32w1

Ullaich clàran DNS airson subdomains login.k8s.example.com и dex.k8s.example.com, a bharrachd air teisteanasan SSL airson ingress.

Nach cruthaich sinn teisteanasan 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

Issuer Cluster le tiotal le-clusterissuer bu chòir a bhith ann mu thràth, mura h-eil, cruthaich e le bhith a’ cleachdadh 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

rèiteachadh KubeAPISserver

Airson kubeAPIServer a bhith ag obair, feumaidh tu OIDC a rèiteachadh agus am brabhsair ùrachadh:

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

Bidh sinn a ’cleachdadh cop gus cruinneachaidhean a leudachadh, ach tha e ag obair san aon dòigh airson manaidsearan buidheann eile.

Rèiteachadh Dex agus dex-k8s-authenticator

Airson Dex a bhith ag obair, feumaidh teisteanas agus iuchair a bhith agad bho mhaighstir Kubernetes, tarraingidh sinn a-mach às an sin e:

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

Clone an stòr dex-k8s-authenticator:

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

Le cuideachadh bho fhaidhlichean luachan, is urrainn dhuinn caochladairean a stèidheachadh gu sùbailte airson ar Mapaichean HELM.

Bheir sinn cunntas air an rèiteachadh airson 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

Agus airson dex-k8s-authenticator:

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

Stàlaich Dex agus 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

Feuch an dèan sinn cinnteach dè cho feumail sa tha na seirbheisean (bu chòir dha Dex còd 400 a thilleadh, agus bu chòir do dex-k8s-authenticator còd 200 a thilleadh):

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

rèiteachadh RBAC

Cruthaich ClusterRole airson a’ chuantail, anns a’ chùis againn le ruigsinneachd leughaidh a-mhàin:

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

Cruthaichidh sinn rèiteachadh airson 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

A-nis tha sinn deiseil airson deuchainn.

Deuchainnean

Rach gu duilleag logadh a-steachhttps://login.k8s.example.com) agus log a-steach le cunntas GitHub:

Dearbhadh Kubernetes le GitHub OAuth agus Dex
Duilleag ceadachaidh

Dearbhadh Kubernetes le GitHub OAuth agus Dex
Duilleag ceadachaidh air ath-stiùireadh gu GitHub

Dearbhadh Kubernetes le GitHub OAuth agus Dex
 Lean an stiùireadh a chaidh a chruthachadh gus faighinn a-steach

Às deidh dhuinn leth-bhreac a dhèanamh bhon duilleag-lìn, is urrainn dhuinn kubectl a chleachdadh gus na goireasan cnuasachaidh againn a riaghladh:

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"

Agus bidh e ag obair, chì a h-uile neach-cleachdaidh GitHub sa bhuidheann againn goireasan agus logadh a-steach gu Pods, ach chan eil cead aca an atharrachadh.

Source: www.habr.com

Cuir beachd ann