diff --git a/.github/workflows/_deploy-production.yml b/.github/workflows/_deploy-production.yml index 91121d29f..5b495dc00 100644 --- a/.github/workflows/_deploy-production.yml +++ b/.github/workflows/_deploy-production.yml @@ -36,7 +36,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Authenticate in Seguro diff --git a/.github/workflows/cleanup.yml b/.github/workflows/cleanup.yml index 190c10cb3..62a110f47 100644 --- a/.github/workflows/cleanup.yml +++ b/.github/workflows/cleanup.yml @@ -26,7 +26,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Cleanup diff --git a/.github/workflows/content_validation.yml b/.github/workflows/content_validation.yml index 22ac49b77..2ed831909 100644 --- a/.github/workflows/content_validation.yml +++ b/.github/workflows/content_validation.yml @@ -42,7 +42,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Check links @@ -61,7 +61,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Checkout code @@ -95,7 +95,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Checkout code diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 48f7f0a22..0600dbfb7 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -26,7 +26,7 @@ jobs: with: preset: werf group: "3" - channel: dev + channel: alpha force: false - name: Deploy to test diff --git a/_data/ru/publications.yml b/_data/ru/publications.yml index b50a9691b..7bc16b6f1 100644 --- a/_data/ru/publications.yml +++ b/_data/ru/publications.yml @@ -442,7 +442,7 @@ articles: created: 2017-08-23 img: "/images/publications/ru_230817.jpg" comment: | -
Эта статья — ознакомительное руководство по сборке Docker-образов приложений с помощью нашей Open Source-утилиты werf (dapp) (подробнее о ней читайте в анонсе). На примере двух простых приложений (с одним образом) рассмотрим, как могут быть задействованы некоторые из основных возможностей dapp и какой результат они дают.
+Эта статья — ознакомительное руководство по сборке Docker-образов приложений с помощью нашей Open Source-утилиты werf (dapp) (подробнее о ней читайте в анонсе). На примере двух простых приложений (с одним образом) рассмотрим, как могут быть задействованы некоторые из основных возможностей dapp и какой результат они дают.
- title: "Официально представляем werf (dapp) — DevOps-утилиту для сопровождения CI/CD" habr_url: "https://habr.com/company/flant/blog/333682/" diff --git a/_includes/en/guides/300_deployment_practices/030_resource_management.md.liquid b/_includes/en/guides/300_deployment_practices/030_resource_management.md.liquid index 3ccbb1182..9310e74bd 100644 --- a/_includes/en/guides/300_deployment_practices/030_resource_management.md.liquid +++ b/_includes/en/guides/300_deployment_practices/030_resource_management.md.liquid @@ -92,7 +92,7 @@ spec: controlledValues: RequestsAndLimits ``` -We will not go into detail about this manifest’s parameters: [this article](https://povilasv.me/vertical-pod-autoscaling-the-definitive-guide/) provides a detailed description of the features and aspects of VPA. In short, we specify the VPA target (`targetRef`) and select the update policy. Additionally, we specify the upper and lower limits for the resources VPA can use. The primary focus is on the `updateMode` field. In “Recreate” or “Auto” mode, VPA will recreate Pods with all consequences (until an above-mentioned patch for in-place Pod resource parameters update becomes available). Since we don’t want it, we use the “Off” mode: +We will not go into detail about this manifest’s parameters: [the VPA documentation](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) provides a detailed description of the features and aspects of VPA. In short, we specify the VPA target (`targetRef`) and select the update policy. Additionally, we specify the upper and lower limits for the resources VPA can use. The primary focus is on the `updateMode` field. In “Recreate” or “Auto” mode, VPA will recreate Pods with all consequences (until an above-mentioned patch for in-place Pod resource parameters update becomes available). Since we don’t want it, we use the “Off” mode: ```yaml apiVersion: autoscaling.k8s.io/v1