{"id":86902,"date":"2020-07-01T07:42:28","date_gmt":"2020-07-01T05:42:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/udalyaem-ustarevshuyu-feature-branch-v-kubernetes-klastere"},"modified":"2020-07-01T07:42:28","modified_gmt":"2020-07-01T05:42:28","slug":"udalyaem-ustarevshuyu-feature-branch-v-kubernetes-klastere","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/udalyaem-ustarevshuyu-feature-branch-v-kubernetes-klastere","title":{"rendered":"Elavult feature branch elt\u00e1vol\u00edt\u00e1sa a Kubernetes klaszterben","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Elavult<\/p>\n

Hell\u00f3! Jellemz\u0151 \u00e1g<\/b> (aka deploy preview, review app) \u2014 ez az, amikor nemcsak a master \u00e1gat, hanem minden pull requestet egyedi URL-en telep\u00edtenek. Ellen\u0151rizheti, m\u0171k\u00f6dik-e a k\u00f3d a production k\u00f6rnyezetben, \u00e9s megmutathatja a funkci\u00f3t m\u00e1s programoz\u00f3knak vagy term\u00e9kfejleszt\u0151knek. Am\u00edg a pull request-en dolgozik, minden \u00faj commit az aktu\u00e1lis telep\u00edt\u00e9st az r\u00e9gi k\u00f3dhoz t\u00f6rli, \u00e9s \u00faj telep\u00edt\u00e9st ind\u00edt az \u00faj k\u00f3dhoz. K\u00e9rd\u00e9sek mer\u00fclhetnek fel, amikor a pull requestet a master \u00e1gba olvasztja. A feature branch m\u00e1r nem sz\u00fcks\u00e9ges, de a Kubernetes er\u0151forr\u00e1sok m\u00e9g mindig a klaszterben tal\u00e1lhat\u00f3k.<\/p>\n

<\/a><\/noindex><\/p>\n

Tov\u00e1bbi inform\u00e1ci\u00f3 a feature branch-r\u0151l<\/h2>\n

<\/p>\n

Az egyik m\u00f3dszer arra, hogyan k\u00e9sz\u00edts\u00fcnk feature branch-eket a Kubernetes-ben, ha namespace-ket haszn\u00e1lunk. R\u00f6viden, a production konfigur\u00e1ci\u00f3 \u00edgy n\u00e9z ki:<\/p>\n

<\/p>\n

kind: Namespace\napiVersion: v1\nmetadata:\n  name: habr-back-end\n...\n\nkind: Deployment\napiVersion: apps\/v1\nmetadata:\n  namespace: habr-back-end\nspec:\n  replicas: 3\n...<\/code><\/pre>\n
<\/p>\n
A feature branch sz\u00e1m\u00e1ra namespace-t hozunk l\u00e9tre az azonos\u00edt\u00f3j\u00e1val (p\u00e9ld\u00e1ul a pull request sz\u00e1ma) \u00e9s valamilyen el\u0151taggal\/ut\u00f3taggal (p\u00e9ld\u00e1ul, -pr-<\/b>):<\/p>\n
<\/p>\n
kind: Namespace\napiVersion: v1\nmetadata:\n  name: habr-back-end-pr-17\n...\n\nkind: Deployment\napiVersion: apps\/v1\nmetadata:\n  namespace: habr-back-end-pr-17\nspec:\n  replicas: 1\n...<\/code><\/pre>\n
<\/p>\n
\u00d6sszess\u00e9g\u00e9ben \u00edrtam Kubernetes Operator<\/b> (alkalmaz\u00e1s, amely hozz\u00e1f\u00e9r a klaszter er\u0151forr\u00e1saihoz), link a projekthez a Github-on<\/a><\/noindex>. Ez t\u00f6rli azokat a namespace-ket, amelyek r\u00e9gi feature branch-ekhez kapcsol\u00f3dnak. A Kubernetes-ben, ha egy namespace-t t\u00f6r\u00f6lnek, az abban tal\u00e1lhat\u00f3 egy\u00e9b er\u0151forr\u00e1sok is automatikusan t\u00f6rl\u0151dnek.<\/p>\n
<\/p>\n
$ kubectl get pods --all-namespaces | grep -e \"-pr-\"\nNAMESPACE            ... \u00c9LET\nhabr-back-end-pr-264 ... 4d8h\nhabr-back-end-pr-265 ... 5d7h<\/code><\/pre>\n
<\/p>\n
Arr\u00f3l, hogyan lehet integr\u00e1lni a feature branch-eket a klaszterbe, itt olvashat. itt<\/a><\/noindex> \u00e9s itt<\/a><\/noindex>.<\/p>\n
<\/p>\n
Motiv\u00e1ci\u00f3<\/h2>\n
<\/p>\n
N\u00e9zz\u00fck meg a pull request tipikus \u00e9letciklus\u00e1t folyamatos integr\u00e1ci\u00f3val (continuous integration<\/code>):<\/p>\n
<\/p>\n
    \n
  1. \u00daj commitot toltunk az \u00e1gba.<\/li>\n
  2. A build sor\u00e1n linters \u00e9s\/vagy tesztek futnak.<\/li>\n
  3. Automatikusan gener\u00e1l\u00f3dnak a Kubernetes pull request konfigur\u00e1ci\u00f3k (p\u00e9ld\u00e1ul a megfelel\u0151 sablonba beillesztik a sz\u00e1m\u00e1t).<\/li>\n
  4. A kubectl apply seg\u00edts\u00e9g\u00e9vel a konfigur\u00e1ci\u00f3k a klaszterbe ker\u00fclnek (telep\u00edtve).<\/li>\n
  5. A pull request \u00f6sszevon\u00e1sa a master \u00e1ggal.<\/li>\n<\/ol>\n
    <\/p>\n
    Am\u00edg a pull request-en dolgozik, minden \u00faj commit az aktu\u00e1lis telep\u00edt\u00e9st az r\u00e9gi k\u00f3dhoz t\u00f6rli, \u00e9s \u00faj telep\u00edt\u00e9st ind\u00edt az \u00faj k\u00f3dhoz. De amikor a pull request \u00f6sszeolvad a master \u00e1ggal, csak a master \u00e1g \u00e9p\u00fcl. Ennek eredm\u00e9nyek\u00e9nt a pull request-re m\u00e1r elfeledkez\u00fcnk, m\u00edg a Kubernetes er\u0151forr\u00e1sai m\u00e9g mindig a klaszterben tal\u00e1lhat\u00f3k.<\/p>\n
    <\/p>\n
    Hogyan haszn\u00e1ljuk<\/h2>\n
    <\/p>\n
    Telep\u00edtsd a projektet az al\u00e1bbi parancs seg\u00edts\u00e9g\u00e9vel:<\/p>\n
    <\/p>\n
    $ kubectl apply -f https:\/\/raw.githubusercontent.com\/dmytrostriletskyi\/stale-feature-branch-operator\/master\/configs\/production.yml<\/code><\/pre>\n
    <\/p>\n
    Hozz l\u00e9tre egy f\u00e1jlt a k\u00f6vetkez\u0151 tartalommal, \u00e9s telep\u00edtsd a k\u00f6vetkez\u0151k seg\u00edts\u00e9g\u00e9vel: kubectl apply -f<\/code>:<\/p>\n
    <\/p>\n
    apiVersion: feature-branch.dmytrostriletskyi.com\/v1\nkind: StaleFeatureBranch\nmetadata:\n  name: stale-feature-branch\nspec:\n  namespaceSubstring: -pr-\n  afterDaysWithoutDeploy: 3<\/code><\/pre>\n
    <\/p>\n
    A parameter namespaceSubstring<\/b> sz\u00fcks\u00e9ges a namespace-ek sz\u0171r\u00e9s\u00e9re a pull request-ek \u00e9s m\u00e1s namespace-ek k\u00f6z\u00f6tt. P\u00e9ld\u00e1ul, ha a klaszterben a k\u00f6vetkez\u0151 namespace-ek tal\u00e1lhat\u00f3k: habr-back-end<\/code>, habr-front-end<\/code>, habr-back-end-pr-17<\/code>, habr-back-end-pr-33<\/code>, akkor a t\u00f6rl\u00e9sre jel\u00f6ltek habr-back-end-pr-17<\/code>, habr-back-end-pr-33<\/code>.<\/p>\n
    <\/p>\n
    A parameter afterDaysWithoutDeploy<\/b> sz\u00fcks\u00e9ges a r\u00e9gi namespace-ek t\u00f6rl\u00e9s\u00e9re. P\u00e9ld\u00e1ul, ha a namespace l\u00e9tre lett hozva 3 nappal 1 \u00f3r\u00e1val<\/code> ezel\u0151tt, \u00e9s a param\u00e9ter azt mondja 3 nap<\/code>, ez a namespace t\u00f6r\u00f6lve lesz. Ford\u00edtott esetben is m\u0171k\u00f6dik, ha a namespace l\u00e9trehozva 2 nappal 23 \u00f3r\u00e1val<\/code> ezel\u0151tt, \u00e9s a param\u00e9ter azt mondja 3 nap<\/code>, ez a namespace nem lesz t\u00f6r\u00f6lve.<\/p>\n
    <\/p>\n
    Van m\u00e9g egy param\u00e9ter, amely arra szolg\u00e1l, hogy milyen gyakran szkennelj\u00fck a namespace-eket \u00e9s ellen\u0151rizz\u00fck az id\u0151t an\u00e9lk\u00fcl, hogy telep\u00edt\u00e9s t\u00f6rt\u00e9nt volna \u2014 checkEveryMinutes<\/b>. Alap\u00e9rtelmez\u00e9s szerint ez 30 perc<\/code>.<\/p>\n
    <\/p>\n
    Hogyan m\u0171k\u00f6dik ez<\/h2>\n
    <\/p>\n
    Gyakorlatban sz\u00fcks\u00e9ges:<\/p>\n
    <\/p>\n
      \n
    1. Docker<\/a><\/noindex> izol\u00e1lt k\u00f6rnyezetben val\u00f3 m\u0171k\u00f6d\u00e9shez.<\/li>\n
    2. Minikube<\/a><\/noindex> lok\u00e1lisan emeli fel a Kubernetes klasztert.<\/li>\n
    3. kubectl<\/a><\/noindex> \u2014 parancssori fel\u00fclet a klaszter kezel\u00e9s\u00e9re.<\/li>\n<\/ol>\n
      <\/p>\n
      Lok\u00e1lisan emelj\u00fck fel a Kubernetes klasztert:<\/p>\n
      <\/p>\n
      $ minikube start --vm-driver=docker\nminikube v1.11.0 Darwin 10.15.5 rendszeren\nA docker drivert haszn\u00e1lja a megl\u00e9v\u0151 profil alapj\u00e1n.\nKezdj\u00fck a vez\u00e9rl\u0151 s\u00edk csom\u00f3pontot a minikube klaszterben.<\/code><\/pre>\n
      <\/p>\n
      Megadjuk kubectl<\/code> alap\u00e9rtelmez\u00e9s szerint a helyi klasztert haszn\u00e1lja:<\/p>\n
      <\/p>\n
      $ kubectl config use-context minikube\n\u00c1tv\u00e1ltva a \"minikube\" kontextusra.<\/code><\/pre>\n
      <\/p>\n
      Let\u00f6ltj\u00fck a konfigur\u00e1ci\u00f3kat a production k\u00f6rnyezethez:<\/p>\n
      <\/p>\n
      $ curl https:\/\/raw.githubusercontent.com\/dmytrostriletskyi\/stale-feature-branch-operator\/master\/configs\/production.yml > stale-feature-branch-production-configs.yml<\/code><\/pre>\n
      <\/p>\n
      Mivel a production konfigur\u00e1ci\u00f3k be vannak \u00e1ll\u00edtva a r\u00e9gi namespace-ek ellen\u0151rz\u00e9s\u00e9re, \u00e9s az \u00fajonnan l\u00e9trehozott klaszter\u00fcnkben nincs, helyettes\u00edtj\u00fck a k\u00f6rnyezeti v\u00e1ltoz\u00f3t IS_DEBUG<\/code> Gyorsan eml\u00e9kezz\u00fcnk vissza, hogyan m\u0171k\u00f6dik a modul\u00e1ris aritmetika. Az \u00f3ra m\u00e1r egy ismert koncepci\u00f3. Az \u00f3r\u00e1k haszn\u00e1lata igaz<\/code>. Ezzel az \u00e9rt\u00e9kkel a param\u00e9ter afterDaysWithoutDeploy<\/code> nem sz\u00e1m\u00edt, \u00e9s a namespace-eket nem ellen\u0151rzik az id\u0151kkel an\u00e9lk\u00fcl, hogy telep\u00edt\u00e9s t\u00f6rt\u00e9nt volna, csak a substring jelenl\u00e9t\u00e9re (-pr-<\/code>).<\/p>\n
      <\/p>\n
      Ha \u00d6n a Linux<\/code>:<\/p>\n
      <\/p>\n
      $ sed -i 's|false|true|g' stale-feature-branch-production-configs.yml<\/code><\/pre>\n
      <\/p>\n
      Ha \u00d6n a macOS<\/code>:<\/p>\n
      <\/p>\n
      $ sed -i \"\" 's|false|true|g' stale-feature-branch-production-configs.yml<\/code><\/pre>\n
      <\/p>\n
      Telep\u00edtj\u00fck a projektet:<\/p>\n
      <\/p>\n
      $ kubectl apply -f stale-feature-branch-production-configs.yml<\/code><\/pre>\n
      <\/p>\n
      Ellen\u0151rizz\u00fck, hogy a klaszterben megjelent az er\u0151forr\u00e1s StaleFeatureBranch<\/code>:<\/p>\n
      <\/p>\n
      $ kubectl api-resources | grep stalefeaturebranches\nNAME                 ... APIGROUP                             ... KIND\nstalefeaturebranches ... feature-branch.dmytrostriletskyi.com ... StaleFeatureBranch<\/code><\/pre>\n
      <\/p>\n
      Ellen\u0151rizz\u00fck, hogy a klaszterben megjelent az oper\u00e1tor:<\/p>\n
      <\/p>\n
      $ kubectl get pods --namespace stale-feature-branch-operator\nNAME                                           ... STATUS  ... AGE\nstale-feature-branch-operator-6bfbfd4df8-m7sch ... Running ... 38s<\/code><\/pre>\n
      <\/p>\n
      Ha belen\u00e9z\u00fcnk a napl\u00f3j\u00e1ba, k\u00e9szen \u00e1ll az er\u0151forr\u00e1sok feldolgoz\u00e1s\u00e1ra StaleFeatureBranch<\/code>:<\/p>\n
      <\/p>\n
      $ kubectl logs stale-feature-branch-operator-6bfbfd4df8-m7sch -n stale-feature-branch-operator\n... \"msg\":\"Operator Version: 0.0.1\"}\n...\n... \"msg\":\"Starting EventSource\", ... , \"source\":\"kind source: \/, Kind=\"}\n... \"msg\":\"Starting Controller\", ...}\n... \"msg\":\"Starting workers\", ..., \"worker count\":1}<\/code><\/pre>\n
      <\/p>\n
      Telep\u00edtj\u00fck a k\u00e9sz fixtures<\/code> (k\u00e9sz konfigur\u00e1ci\u00f3k a klaszter er\u0151forr\u00e1sainak modellez\u00e9s\u00e9hez) az er\u0151forr\u00e1shoz StaleFeatureBranch<\/code>:<\/p>\n
      <\/p>\n
      $ kubectl apply -f https:\/\/raw.githubusercontent.com\/dmytrostriletskyi\/stale-feature-branch-operator\/master\/fixtures\/stale-feature-branch.yml<\/code><\/pre>\n
      <\/p>\n
      A konfigur\u00e1ci\u00f3kban meg van adva, hogy keressen a namespace-eken egy adott r\u00e9szsz\u00f3t. -pr-<\/code> minden 1 percben<\/code>.:<\/p>\n
      <\/p>\n
      apiVersion: feature-branch.dmytrostriletskyi.com\/v1\nkind: StaleFeatureBranch\nmetadata:\n  name: stale-feature-branch\nspec:\n  namespaceSubstring: -pr-\n  afterDaysWithoutDeploy: 1 \n  checkEveryMinutes: 1<\/code><\/pre>\n
      <\/p>\n
      Az oper\u00e1tor reag\u00e1lt \u00e9s k\u00e9szen \u00e1ll a namespace-ek ellen\u0151rz\u00e9s\u00e9re:<\/p>\n
      <\/p>\n
      $ kubectl logs stale-feature-branch-operator-6bfbfd4df8-m7sch -n stale-feature-branch-operator\n... \"msg\":\"A r\u00e9gi funkci\u00f3s \u00e1g feldolgoz\u00e1s alatt \u00e1ll.\",\"namespaceSubstring\":\"-pr-\",\"afterDaysWithoutDeploy\":1,\"checkEveryMinutes\":1,\"isDebug\":\"true\"}<\/code><\/pre>\n
      <\/p>\n
      Telep\u00edt\u00fcnk fixtures<\/code>, tartalmazva k\u00e9t namespace-et (project-pr-1<\/code>, project-pr-2<\/code>) \u00e9s azok telep\u00edt\u00e9sek<\/code>, szolg\u00e1ltat\u00e1sai<\/code>, ingress<\/code>, stb.:<\/p>\n
      <\/p>\n
      $ kubectl apply -f https:\/\/raw.githubusercontent.com\/dmytrostriletskyi\/stale-feature-branch-operator\/master\/fixtures\/first-feature-branch.yml -f https:\/\/raw.githubusercontent.com\/dmytrostriletskyi\/stale-feature-branch-operator\/master\/fixtures\/second-feature-branch.yml\n...\nnamespace\/project-pr-1 created\ndeployment.apps\/project-pr-1 created\nservice\/project-pr-1 created\nhorizontalpodautoscaler.autoscaling\/project-pr-1 created\nsecret\/project-pr-1 created\nconfigmap\/project-pr-1 created\ningress.extensions\/project-pr-1 created\nnamespace\/project-pr-2 created\ndeployment.apps\/project-pr-2 created\nservice\/project-pr-2 created\nhorizontalpodautoscaler.autoscaling\/project-pr-2 created\nsecret\/project-pr-2 created\nconfigmap\/project-pr-2 created\ningress.extensions\/project-pr-2 created<\/code><\/pre>\n
      <\/p>\n
      Ellen\u0151rizz\u00fck, hogy az \u00f6sszes fent eml\u00edtett er\u0151forr\u00e1s sikeresen l\u00e9trej\u00f6tt:<\/p>\n
      <\/p>\n
      $ kubectl get namespace,pods,deployment,service,horizontalpodautoscaler,configmap,ingress -n project-pr-1 && kubectl get namespace,pods,deployment,service,horizontalpodautoscaler,configmap,ingress -n project-pr-2\n...\nNAME                              ... READY ... STATUS  ... AGE\npod\/project-pr-1-848d5fdff6-rpmzw ... 1\/1   ... Running ... 67s\n\nNAME                         ... READY ... AVAILABLE ... AGE\ndeployment.apps\/project-pr-1 ... 1\/1   ... 1         ... 67s\n...<\/code><\/pre>\n
      <\/p>\n
      Mivel aktiv\u00e1ltuk debug<\/code>, namespace-ek project-pr-1<\/code> \u00e9s project-pr-2<\/code>, ez\u00e9rt az \u00f6sszes t\u00f6bbi er\u0151forr\u00e1snak is azonnal el kell t\u0171nnie, figyelmen k\u00edv\u00fcl hagyva a param\u00e9tert afterDaysWithoutDeploy<\/code>. Ez az oper\u00e1tor napl\u00f3iban l\u00e1that\u00f3:<\/p>\n
      <\/p>\n
      $ kubectl logs stale-feature-branch-operator-6bfbfd4df8-m7sch -n stale-feature-branch-operator\n... \"msg\":\"A namespace-t t\u00f6r\u00f6lni kell, mert a debug m\u00f3d enged\u00e9lyezve van.\",\"namespaceName\":\"project-pr-1\"}\n... \"msg\":\"A namespace feldolgoz\u00e1s alatt \u00e1ll.\",\"namespaceName\":\"project-pr-1\",\"namespaceCreationTimestamp\":\"2020-06-16 18:43:58 +0300 EEST\"}\n... \"msg\":\"A namespace t\u00f6r\u00f6lve lett.\",\"namespaceName\":\"project-pr-1\"}\n... \"msg\":\"A namespace-t t\u00f6r\u00f6lni kell, mert a debug m\u00f3d enged\u00e9lyezve van.\",\"namespaceName\":\"project-pr-2\"}\n... \"msg\":\"A namespace feldolgoz\u00e1s alatt \u00e1ll.\",\"namespaceName\":\"project-pr-2\",\"namespaceCreationTimestamp\":\"2020-06-16 18:43:58 +0300 EEST\"}\n... \"msg\":\"A namespace t\u00f6r\u00f6lve lett.\",\"namespaceName\":\"project-pr-2\"}<\/code><\/pre>\n
      <\/p>\n
      Ha ellen\u0151rizz\u00fck az er\u0151forr\u00e1sok megl\u00e9t\u00e9t, akkor azok Terminating<\/code> (t\u00f6rl\u00e9si folyamat) \u00e1llapotban lesznek, vagy m\u00e1r t\u00f6r\u00f6lve vannak (a parancs kimenete \u00fcres).<\/p>\n
      <\/p>\n
      $ kubectl get namespace,pods,deployment,service,horizontalpodautoscaler,configmap,ingress -n project-pr-1 && kubectl get namespace,pods,deployment,service,horizontalpodautoscaler,configmap,ingress -n project-pr-2\n...<\/code><\/pre>\n
      <\/p>\n
      Ism\u00e9telheti a l\u00e9trehoz\u00e1si folyamatot fixtures<\/code> t\u00f6bbsz\u00f6r is, \u00e9s megvizsg\u00e1lhatja, hogy a t\u00f6rl\u00e9s egy percen bel\u00fcl megt\u00f6rt\u00e9nik.<\/p>\n
      <\/p>\n
      Alternat\u00edv\u00e1k<\/h2>\n
      <\/p>\n
      Mit lehet tenni a clusterben m\u0171k\u00f6d\u0151 oper\u00e1tor helyett? Sz\u00e1mos megk\u00f6zel\u00edt\u00e9s l\u00e9tezik, mindegyik nem t\u00f6k\u00e9letes (\u00e9s azok h\u00e1tr\u00e1nyai szubjekt\u00edvak), \u00e9s mindenki maga d\u00f6nti el, mi a legjobb a konkr\u00e9t projekthez:<\/p>\n
      <\/p>\n
        \n
      1. \n
        A feature branch t\u00f6rl\u00e9se a master branch folyamatos integr\u00e1ci\u00f3s buildje alatt.<\/p>\n
        <\/p>\n