{"id":97895,"date":"2020-10-23T02:42:12","date_gmt":"2020-10-23T00:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd"},"modified":"2020-10-23T02:42:12","modified_gmt":"2020-10-23T00:42:12","slug":"kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd","title":{"rendered":"Jak pou\u017e\u00edvat HashiCorp Waypoint ke spolupr\u00e1ci s GitLab CI\/CD","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Jak<\/p>\n

<\/p>\n

HashiCorp p\u0159edstavila nov\u00fd projekt Waypoint<\/a><\/noindex> na HashiCorp Digital<\/a><\/noindex>. Vyu\u017e\u00edv\u00e1 soubor zalo\u017een\u00fd na HCL pro popis sestaven\u00ed, dod\u00e1n\u00ed a vyd\u00e1n\u00ed aplikac\u00ed pro r\u016fzn\u00e9 cloudov\u00e9 platformy, od Kubernetes po AWS a Google Cloud Run. Je mo\u017en\u00e9 si p\u0159edstavit, \u017ee Waypoint je kombinac\u00ed Terraform a Vagrant pro popis procesu sestaven\u00ed, dod\u00e1n\u00ed a vyd\u00e1n\u00ed va\u0161ich aplikac\u00ed.<\/p>\n

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

Z\u016fst\u00e1vaj\u00edc v\u011brn\u00e1 sama sob\u011b, HashiCorp vydala Waypoint jako open-source, p\u0159i\u010dem\u017e obsahuje tak\u00e9 mnoho p\u0159\u00edklad\u016f. \u00darove\u0148 orchestr\u00e1toru z\u00e1vis\u00ed na v\u00e1s, Waypoint je dod\u00e1v\u00e1n jako spustiteln\u00fd soubor, kter\u00fd m\u016f\u017eete spustit p\u0159\u00edmo na va\u0161em notebooku nebo z n\u00e1stroje CI\/CD, kter\u00fd si vyberete. C\u00edl pro nasazen\u00ed aplikac\u00ed si rovn\u011b\u017e vyb\u00edr\u00e1te vy, proto\u017ee Waypoint podporuje Kubernetes, Docker, Google Cloud Run, AWS ECS a dal\u0161\u00ed.<\/p>\n

<\/p>\n

Po p\u0159e\u010dten\u00ed \u00fa\u017easn\u00fdch dokumentaci<\/a><\/noindex> a skv\u011bl\u00fdch p\u0159\u00edklad\u016f<\/a><\/noindex> aplikac\u00ed, kter\u00e9 poskytla HashiCorp, jsme se rozhodli pod\u00edvat bl\u00ed\u017ee na orchestraci Waypoint pomoc\u00ed GitLab CI\/CD. Abychom to ud\u011blali, vezmeme jednoduchou aplikaci Node.js b\u011b\u017e\u00edc\u00ed na AWS ECS z repozit\u00e1\u0159e p\u0159\u00edklad\u016f.<\/p>\n

<\/p>\n

Po zklonov\u00e1n\u00ed repozit\u00e1\u0159e se pod\u00edv\u00e1me na strukturu aplikace, kter\u00e1 zobrazuje jednu str\u00e1nku:<\/p>\n

<\/p>\n

\"Jak<\/p>\n

<\/p>\n

Jak jste si mohli v\u0161imnout, v tomto projektu nen\u00ed Dockerfile. Nebyly p\u0159id\u00e1ny do p\u0159\u00edkladu, proto\u017ee je v z\u00e1sad\u011b nepot\u0159ebujeme, jeliko\u017e se o n\u011b postar\u00e1 Waypoint. Pod\u00edvejme se podrobn\u011bji na soubor waypoint.hcl<\/code>, abychom pochopili, co bude d\u011blat:<\/p>\n

<\/p>\n

projekt = \"example-nodejs\"\n\naplikace \"example-nodejs\" {\n  \u0161t\u00edtky = {\n    \"slu\u017eba\" = \"example-nodejs\",\n    \"prost\u0159ed\u00ed\" = \"dev\"\n  }\n\n  sestaven\u00ed {\n    pou\u017eij \"pack\" {}\n    registrace {\n    pou\u017eij \"aws-ecr\" {\n        region = \"us-east-1\"\n        repozit\u00e1\u0159 = \"waypoint-gitlab\"\n        zna\u010dka = \"latest\"\n    }\n    }\n  }\n\n  nasazen\u00ed {\n    pou\u017eij \"aws-ecs\" {\n    region = \"us-east-1\"\n    pam\u011b\u0165 = \"512\"\n    }\n  }\n}<\/code><\/pre>\n
<\/p>\n
B\u011bhem f\u00e1ze sestaven\u00ed Waypoint pou\u017eije Cloud Native Buildpacks (CNB<\/a><\/noindex>), aby ur\u010dil programovac\u00ed jazyk projektu a vytvo\u0159il obraz pro Docker bez pou\u017eit\u00ed Dockerfile. V podstat\u011b se jedn\u00e1 o stejnou technologii, kterou pou\u017e\u00edv\u00e1 GitLab v \u010d\u00e1sti Auto DevOps<\/a><\/noindex> v kroku Auto Build. Je p\u0159\u00edjemn\u00e9 vid\u011bt, \u017ee CNB od CNCF z\u00edsk\u00e1v\u00e1 st\u00e1le v\u011bt\u0161\u00ed popularitu mezi u\u017eivateli v oboru.<\/p>\n
<\/p>\n
Jakmile je obraz sestaven, Waypoint jej automaticky nahraje do na\u0161\u00ed AWS ECR registru, aby byl p\u0159ipraven k dod\u00e1n\u00ed. Po dokon\u010den\u00ed sestaven\u00ed krok dod\u00e1n\u00ed vyu\u017e\u00edv\u00e1 dopln\u011bn\u00ed AWS ECS<\/a><\/noindex> pro nasazen\u00ed na\u0161\u00ed aplikace do na\u0161eho \u00fa\u010dtu AWS.<\/p>\n
<\/p>\n
Z m\u00e9ho notebooku \u2014 v\u0161e je snadn\u00e9. Nainstaluji Waypoint, kter\u00fd je ji\u017e ov\u011b\u0159en\u00fd v m\u00e9m \u00fa\u010dtu AWS, a \u201eprost\u011b to funguje\u201c. Ale co kdy\u017e chci vyrazit za hranice sv\u00e9ho notebooku? Nebo n\u00e1hle chci tento nasazen\u00ed automatizovat jako sou\u010d\u00e1st sv\u00e9ho celkov\u00e9ho CI\/CD pipeline, ve kter\u00e9 prob\u00edhaj\u00ed m\u00e9 aktu\u00e1ln\u00ed integra\u010dn\u00ed testy, bezpe\u010dnostn\u00ed testy a dal\u0161\u00ed? To je ta \u010d\u00e1st p\u0159\u00edb\u011bhu, kde p\u0159ich\u00e1z\u00ed na sc\u00e9nu GitLab CI\/CD!<\/p>\n
<\/p>\n
N.B.<\/strong> Pokud teprve pl\u00e1nujete implementaci CI\/CD nebo chcete za\u010d\u00edt pou\u017e\u00edvat osv\u011bd\u010den\u00e9 postupy pro budov\u00e1n\u00ed pipeline, pod\u00edvejte se na nov\u00fd kurz Sl\u011brma. \u201eCI\/CD na p\u0159\u00edkladu Gitlab CI\u201c<\/a><\/noindex>. Nyn\u00ed je dostupn\u00fd za cenu p\u0159edobjedn\u00e1vky. <\/p><\/blockquote>\n
<\/p>\n
Waypoint v GitLab CI\/CD<\/h2>\n
<\/p>\n
Pro orchestraci v\u0161eho v GitLab CI\/CD se pod\u00edvejme, co pot\u0159ebujeme v na\u0161em souboru. .gitlab-ci.yml<\/code>:<\/p>\n
<\/p>\n