I-ProHoster > Π‘Π»ΠΎΠ³ > Ukuphatha > Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex

Ngethula ekunakeni kwakho okokufundisa kokukhiqiza ukufinyelela kuqoqo le-Kubernetes kusetshenziswa i-Dex, i-dex-k8s-authenticator ne-GitHub.

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
I-meme yendawo evela ku-Kubernetes yolimi lwesiRashiya iyaxoxa yocingo

Isingeniso

Sisebenzisa i-Kubernetes ukuze sakhe izindawo eziguqukayo zokuthuthukiswa kanye nethimba le-QA. Ngakho sifuna ukubanikeza ukufinyelela kuqoqo lakho kokubili ideshibhodi ne-kubectl. Ngokungafani ne-OpenShift, i-vanilla Kubernetes ayinabo ubuqiniso bomdabu, ngakho sisebenzisa amathuluzi ezinkampani zangaphandle kulokhu.

Kulokhu kulungiselelwa sisebenzisa:

  • i-dex-k8s-isiqinisekisiβ€Š - isicelo sewebhu sokukhiqiza i-kubectl config
  • I-Dex β€” Umhlinzeki we-OpenID Connect
  • I-GitHub - ngoba sisebenzisa i-GitHub enkampanini yethu

Sizamile ukusebenzisa i-Google OIDC, kodwa ngeshwa thina kwehlulekile ukuwaqala ngamaqembu, ngakho ukuhlanganiswa ne-GitHub kusifanele kahle. Ngaphandle kwemephu yeqembu, ngeke kwenzeke ukudala izinqubomgomo ze-RBAC ezisuselwe kumaqembu.

Ngakho-ke, inqubo yethu yokugunyazwa kwe-Kubernetes isebenza kanjani ekumeleleni okubonakalayo:

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
Inqubo yokugunyaza

Imininingwane eyengeziwe kanye nephuzu ngephuzu:

  1. Umsebenzisi ungena ku-dex-k8s-authenticator (login.k8s.example.com)
  2. i-dex-k8s-authenticator idlulisela isicelo ku-Dex (dex.k8s.example.com)
  3. U-Dex uqondisa kabusha ekhasini lokungena le-GitHub
  4. I-GitHub ikhiqiza ulwazi oludingekayo lokugunyazwa futhi ilibuyisele ku-Dex
  5. U-Dex udlulisela ulwazi olutholiwe ku-dex-k8s-authenticator
  6. Umsebenzisi uthola ithokheni ye-OIDC evela ku-GitHub
  7. I-dex-k8s-authenticator ingeza ithokheni ku-kubeconfig
  8. kubectl idlulisela ithokheni ku-KubeAPIServer
  9. I-KubeAPIServer ibuyisela ukufinyelela ku-kubectl ngokusekelwe kuthokheni edlulisiwe
  10. Umsebenzisi uthola ukufinyelela ku-kubectl

Imisebenzi Yokulungiselela

Yebo, sesivele sineqoqo le-Kubernetes elifakiwe (k8s.example.com), futhi iza ne-HELM efakwe ngaphambili. Futhi sinenhlangano ku-GitHub (super-org).
Uma ungenayo i-HELM, yifake ilula kakhulu.

Okokuqala sidinga ukusetha i-GitHub.

Iya ekhasini lezilungiselelo zenhlangano, (https://github.com/organizations/super-org/settings/applications) bese udala uhlelo olusha (Uhlelo Lokusebenza Olugunyaziwe lwe-OAuth):
Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
Ukudala uhlelo lokusebenza olusha ku-GitHub

Gcwalisa izinkambu ngama-URL adingekayo, isibonelo:

  • I-URL yekhasi eliyisiqalo: https://dex.k8s.example.com
  • I-URL yokugunyazwa yokushayela emuva: https://dex.k8s.example.com/callback

Qaphela ngezixhumanisi, kubalulekile ukuthi ungalahlekelwa ama-slash.

Ephendula ifomu eligcwalisiwe, i-GitHub izokhiqiza Client ID ΠΈ Client secret, zigcine endaweni ephephile, zizoba usizo kithi (ngokwesibonelo, sisebenzisa I-Vault okokugcina izimfihlo):

Client ID: 1ab2c3d4e5f6g7h8
Client secret: 98z76y54x32w1

Lungiselela amarekhodi e-DNS ezizindeni ezingaphansi login.k8s.example.com ΠΈ dex.k8s.example.com, kanye nezitifiketi ze-SSL zokungena.

Masidale izitifiketi 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 isivele ikhona, kodwa uma kungenjalo, idale 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

Ukucushwa kwe-KubeAPIServer

Ukuze i-kubeAPIServer isebenze, udinga ukulungisa i-OIDC futhi ubuyekeze iqoqo:

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 khahlela ngokuphakela amaqoqo, kodwa lokhu kusebenza ngendlela efanayo abanye abaphathi beqoqo.

Ukucushwa kwe-Dex nesiqinisekisi se-dex-k8s

Ukuze u-Dex asebenze, udinga ukuba nesitifiketi nokhiye ovela ku-Kubernetes master, asikuthole lapho:

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

Ake sihlanganise inqolobane yesiqinisekisi se-dex-k8s:

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

Ngokusebenzisa amafayela amanani, singakwazi ukumisa okuguquguqukayo kwezethu Amashadi we-HELM.

Ake sichaze ukucushwa kwe-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

Futhi nge-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

Faka i-Dex ne-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

Ake sihlole ukusebenza kwezinsizakalo (i-Dex kufanele ibuyisele ikhodi 400, futhi i-dex-k8s-authenticator kufanele ibuyisele ikhodi 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

Ukucushwa kwe-RBAC

Sakha i-ClusterRole yeqembu, kithina ngokufinyelela kokufunda 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

Masidale ukucushwa kwe-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

Manje sesilungele ukuhlolwa.

Uvivinyo

Iya ekhasini lokungena (https://login.k8s.example.com) bese ungena usebenzisa i-akhawunti yakho ye-GitHub:

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
Ikhasi lokungena

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
Ikhasi lokungena ngemvume liqondiswe kabusha ku-GitHub

Qinisekisa ku-Kubernetes usebenzisa i-GitHub OAuth ne-Dex
 Landela imiyalelo ekhiqiziwe ukuze uthole ukufinyelela

Ngemuva kokukopisha-ukunamathisela ekhasini lewebhu, singasebenzisa i-kubectl ukuphatha izinsiza zethu zeqoqo:

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"

Futhi kuyasebenza, bonke abasebenzisi be-GitHub enhlanganweni yethu bangabona izinsiza futhi bangene kuma-pods, kodwa abanawo amalungelo okuzishintsha.

Source: www.habr.com

Engeza amazwana