Release 18.12.2024

* Certificate Manager: added certificate issuance statuses.
* Translations updated.
* Fixes and improvements.

Author: DataUI VCS Robot

en/_includes/managed-kubernetes/alb-ingress-controller-install.md

@@ -36,7 +36,7 @@ To balance the load and distribute traffic between {{ k8s }} applications, use a
 1. Under **{{ ui-key.yacloud.marketplace-v2.label_available-products }}**, select [ALB Ingress Controller](/marketplace/products/yc/alb-ingress-controller) and click **{{ ui-key.yacloud.marketplace-v2.button_k8s-product-use }}**.
 1. Configure the application:
 
-   * **Namespace**: Select a [namespace](../../managed-kubernetes/concepts/index.md#namespace) other than `default` or create a new one. If you select the default namespace, ALB Ingress Controller may not work correctly.
+   * **Namespace**: Select a [namespace](../../managed-kubernetes/concepts/index.md#namespace) other than `default` or create a new one. If you select a default namespace, ALB Ingress Controller may run incorrectly.
    * **Application name**: Specify the app name.
    * **Folder ID**: Specify a [folder ID](../../resource-manager/operations/folder/get-id.md).
    * **Cluster ID**: Specify a [cluster ID](../../managed-kubernetes/operations/kubernetes-cluster/kubernetes-cluster-list.md).
@@ -65,7 +65,6 @@ To balance the load and distribute traffic between {{ k8s }} applications, use a
 
 1. To install a [Helm chart](https://helm.sh/docs/topics/charts/) with the Ingress controller, run this command:
 
-
    ```bash
    cat sa-key.json | helm registry login {{ registry }} --username 'json_key' --password-stdin && \
    helm pull oci://{{ mkt-k8s-key.yc_alb-ingress-controller.helmChart.name }} \
@@ -83,7 +82,7 @@ To balance the load and distribute traffic between {{ k8s }} applications, use a
 
    {% include [Support OCI](../../_includes/managed-kubernetes/note-helm-experimental-oci.md) %}
 
-   If you specify the default `namespace`, ALB Ingress Controller may not work correctly. We recommend using other values rather than `default`.
+   If you set the `namespace` parameter to `default`, ALB Ingress Controller may run incorrectly. We recommend that you use other values rather than `default`.
 
    The `enableDefaultHealthChecks` parameter enables health checks for applications in a cluster. To do this, the Ingress controller installs the [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) resource in the node group network.
 

en/_includes/managed-kubernetes/gateway-api-install.md

@@ -51,7 +51,6 @@ In {{ managed-k8s-name }}, Gateway API launches [{{ alb-full-name }}](../../appl
 1. {% include [Install and configure kubectl](kubectl-install.md) %}
 1. To install a [Helm chart](https://helm.sh/docs/topics/charts/) with Gateway API, run the command below:
 
-
    ```bash
    helm pull oci://{{ mkt-k8s-key.yc_gateway-api.helmChart.name }} \
      --version {{ mkt-k8s-key.yc_gateway-api.helmChart.tag }} \
@@ -68,7 +67,6 @@ In {{ managed-k8s-name }}, Gateway API launches [{{ alb-full-name }}](../../appl
      gateway-api ./gateway-api/
    ```
 
-
    In the command, specify the network and its subnets to host the [load balancers](../../application-load-balancer/concepts/application-load-balancer.md#lb-location).
 
    {% include [Support OCI](../../_includes/managed-kubernetes/note-helm-experimental-oci.md) %}

en/_includes/managed-kubernetes/install-externaldns.md

@@ -1 +1 @@
-Optionally, [install](../../managed-kubernetes/operations/applications/externaldns.md) ExternalDNS with a plugin for {{ dns-full-name }} to automatically create a [DNS record](../../dns/concepts/resource-record.md) in [{{ dns-full-name }}](../../../dns/) when creating an Ingress controller.
+Optionally, [install](../../managed-kubernetes/operations/applications/externaldns.md) ExternalDNS with a plugin for {{ dns-full-name }} to automatically create a [DNS record](../../dns/concepts/resource-record.md) in [{{ dns-full-name }}](../../../dns/) when creating an Ingress controller.

en/_includes/managed-kubernetes/install-velero.md

@@ -2,6 +2,7 @@ Install the Velero application as follows:
 
 {% list tabs group=instructions %}
 
+
 - {{ marketplace-full-name }} {#marketplace}
 
     Install the Velero application by following [this guide](../../managed-kubernetes/operations/applications/velero-yc-csi.md). In the **Object Storage bucket name** field, specify the bucket you [created earlier](#before-you-begin).
@@ -12,6 +13,7 @@ Install the Velero application as follows:
 
     {% endnote %}
 
+
 - Manually {#manual}
 
     1. {% include [cli-install](../../_includes/cli-install.md) %}

en/_includes/monitoring/metrics-ref/unifiedagent.md

@@ -1,14 +1,14 @@
-The metric name is written in the `name` label.
+The name of the metric is written to the `name` label.
 
 All {{ unified-agent-short-name }} metrics share the `service=custom` label.
 
 ## Native {{ unified-agent-short-name }} metrics {#ua-metrics}
 
-| Metric name<br>Type, unit | Description |
+| Metric name<br>Type, units | Description |
 | --- | --- |
-| `ua.backlog`<br>`DGAUGE`, number | Number of incoming messages for which no outgoing messages have been sent yet. Includes messages from the storage and all incoming but unsent messages. You can safely delete {{ unified-agent-short-name }} along with directories on the disk, if this metric equals zero and is not incrementing. |
+| `ua.backlog`<br>`DGAUGE`, number | Number of incoming messages for which no outgoing messages have been sent yet. Includes messages from the storage and all incoming but unsent messages. You can safely delete {{ unified-agent-short-name }} together with directories on the disk if this metric equals zero and is not incrementing. |
 | `ua.bytes_lost`<br>`RATE`, bytes | Amount of data lost in transit. |
-| `ua.errors`<br>`RATE`, number | Number of {{ unified-agent-short-name }} events with `ERROR` level. For example, data loss due to a corrupted file on disk or exceeded limits, plugin errors while creating a session, or unavailable external services. |
+| `ua.errors`<br>`RATE`, number | Number of {{ unified-agent-short-name }} events with the `ERROR` level. For example, data loss due to a corrupted file on disk or exceeded limits, plugin errors while creating a session, or unavailable external services. |
 | `ua.messages_lost`<br>`RATE`, number | Number of messages lost in transit. |
 | `ua.metrics_lost`<br>`RATE`, number | Number of metrics lost in transit. |
 

en/_includes/organization/get-federation-id.md

@@ -1,5 +1,3 @@
 1. Log in to [{{ org-full-name }}]({{ link-org-cloud-center }}).
-
 1. In the left-hand panel, select ![VectorSquare](../../_assets/console-icons/vector-square.svg) **{{ ui-key.yacloud_org.pages.federations }}**.
-
 1. Select the required federation and copy the **{{ ui-key.yacloud_org.common.columns.column_id }}** field value on the federation info page.

en/_includes/pricing/price-formula/free-tier.md

@@ -1,2 +1 @@
-After you've used up your free service amounts, you will be charged at the applicable rate. The unused balance of free services is reset at the end of the month.
-
+After you spend the free amount of services, you will be charged at the applicable rate. The unused balance of free services is reset at the end of the month.

en/_qa/backup/troubleshooting.md

@@ -7,7 +7,7 @@ This section describes typical problems you may encounter while using {{ backup-
 Make sure that:
 
 * [{{ backup-name }} supports](../../backup/concepts/vm-connection.md#os) the VM operating system.
-* Service account linked to your VM has the `backup.editor` [role](../../backup/security/index.md#backup-editor) assigned.
+* Service account linked to your VM has the `backup.editor` [role](../../backup/security/index.md#backup-editor).
 * [Security group](../../vpc/concepts/security-groups.md) is [correctly](../../backup/concepts/vm-connection.md#vm-network-access) configured for your VM.
 
 For more information, see [Connecting Compute Cloud VM instances to {{ backup-name }}](../../backup/concepts/vm-connection.md).
@@ -28,7 +28,7 @@ A virtual machine becomes outdated after [restoring its backup to another VM](..
 Error message:
 
 ```text
-Not all of the items are mapped. Please, check your target instance and its volumes.
+Not all of the items are mapped. Please, check your goal instance and its volumes.
 ```
 
 The error occurs because {{ backup-name }} cannot find a disk on the target VM that matches the size criterion.
@@ -49,6 +49,10 @@ Iteration 0: The term 'acropsh' is not recognized as the name of a cmdlet, funct
 Make sure that:
 
 * [{{ backup-name }} supports](../../backup/concepts/vm-connection.md#os) the VM operating system.
-* Service account linked to your VM has the `backup.editor` [role](../../backup/security/index.md#backup-editor) assigned.
+* Service account linked to your VM has the `backup.editor` [role](../../backup/security/index.md#backup-editor).
 * [Network access for your VM](../../backup/concepts/vm-connection.md#vm-network-access) is enabled.
-* The PowerShell execution policies allow scripts. If they do not, allow scripts and restart PowerShell. For more information, see the [Microsoft documentation](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies).
+* The PowerShell execution policies allow scripts. If they do not, allow scripts and restart PowerShell. For more information, see the [Microsoft documentation](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies).
+
+#### How to update a {{ backup-name }} backup agent on a VM? {#update-backup-agent}
+
+See [How to update a {{ backup-name }} backup agent on a VM](../../backup/operations/update-backup-agent.md).

en/_tutorials/_tutorials_includes/alb-ingress-balancer-additional-settings.md

@@ -0,0 +1,7 @@
+{% note info %}
+
+The settings listed below will only apply to the [virtual hosts](../../application-load-balancer/tools/k8s-ingress-controller/principles.md#mapping) of the Ingress resource in which the corresponding annotations are configured.
+
+They will not apply to the virtual hosts of the group's other Ingress resources.
+
+{% endnote %}

en/_tutorials/containers/k8s-fluent-bit-logging.md

@@ -14,11 +14,11 @@ Prepare the infrastructure:
 
 - Manually {#manual}
 
-   1. If you do not have a [network](../../vpc/concepts/network.md#network) yet, [create one](../../vpc/operations/network-create.md).
-   1. If you do not have any [subnets](../../vpc/concepts/network.md#subnet), [create them](../../vpc/operations/subnet-create.md) in the [availability zones](../../overview/concepts/geo-scope.md) where your [{{ managed-k8s-name }} cluster](../../managed-kubernetes/concepts/index.md#kubernetes-cluster) and [node group](../../managed-kubernetes/concepts/index.md#node-group) will be created.
-   1. [Create service accounts](../../iam/operations/sa/create.md):
-      * [Service account](../../iam/concepts/users/service-accounts.md) for {{ managed-k8s-name }} resources with the [{{ roles-editor }}](../../iam/roles-reference.md#editor) [role](../../iam/concepts/access-control/roles.md) for the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) where the {{ managed-k8s-name }} cluster is created.
-      * Service account for {{ managed-k8s-name }} nodes with the [{{ roles-cr-puller }}](../../container-registry/security/index.md#container-registry-images-puller) role for the folder with the [Docker image](../../container-registry/concepts/docker-image.md) [registry](../../container-registry/concepts/registry.md). {{ managed-k8s-name }} nodes will pull the required Docker images from the registry on behalf of this account.
+  1. If you do not have a [network](../../vpc/concepts/network.md#network) yet, [create one](../../vpc/operations/network-create.md).
+  1. If you do not have any [subnets](../../vpc/concepts/network.md#subnet) yet, [create them](../../vpc/operations/subnet-create.md) in the [availability zones](../../overview/concepts/geo-scope.md) where your [{{ managed-k8s-name }} cluster](../../managed-kubernetes/concepts/index.md#kubernetes-cluster) and [node group](../../managed-kubernetes/concepts/index.md#node-group) will be created.
+  1. [Create service accounts](../../iam/operations/sa/create.md):
+     * [Service account](../../iam/concepts/users/service-accounts.md) for {{ managed-k8s-name }} resources with the [{{ roles-editor }}](../../iam/roles-reference.md#editor) [role](../../iam/concepts/access-control/roles.md) for the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) where the {{ managed-k8s-name }} cluster is created.
+     * Service account for {{ managed-k8s-name }} nodes with the [{{ roles-cr-puller }}](../../container-registry/security/index.md#container-registry-images-puller) role for the folder containing the [Docker image](../../container-registry/concepts/docker-image.md) [registry](../../container-registry/concepts/registry.md). {{ managed-k8s-name }} nodes will pull the required Docker images from the registry on behalf of this account.
 
      {% note tip %}
 
@@ -76,10 +76,12 @@ Prepare the infrastructure:
 
 {% list tabs %}
 
+
 - Using {{ yandex-cloud }}
 
   Install Fluent Bit by following [this guide](../../managed-kubernetes/operations/applications/fluentbit.md). In the application settings, specify the ID of the [log group](#before-you-begin) you [created earlier](../../logging/concepts/log-group.md). You can request the log group ID with a [list of log groups in the folder](../../logging/operations/list.md).
 
+
 - Manually
 
   1. {% include [Install and configure kubectl](../../_includes/managed-kubernetes/kubectl-install.md) %}
@@ -159,27 +161,14 @@ Some resources are not free of charge. To avoid paying for them, delete the reso
 
 - Manually {#manual}
 
-   1. [Delete the {{ managed-k8s-name }} cluster](../../managed-kubernetes/operations/kubernetes-cluster/kubernetes-cluster-delete.md).
-   1. If you reserved a static [public IP address](../../vpc/concepts/address.md#public-addresses) for your {{ managed-k8s-name }} cluster, release and [delete it](../../vpc/operations/address-delete.md).
-   1. [Delete the created subnets](../../vpc/operations/subnet-delete.md) and [networks](../../vpc/operations/network-delete.md).
-   1. [Delete the created service accounts](../../iam/operations/sa/delete.md).
-   1. [Delete the log group](../../logging/operations/delete-group.md).
+  1. [Delete the {{ managed-k8s-name }} cluster](../../managed-kubernetes/operations/kubernetes-cluster/kubernetes-cluster-delete.md).
+  1. If you reserved a static [public IP address](../../vpc/concepts/address.md#public-addresses) for your {{ managed-k8s-name }} cluster, release and [delete it](../../vpc/operations/address-delete.md).
+  1. [Delete the created subnets](../../vpc/operations/subnet-delete.md) and [networks](../../vpc/operations/network-delete.md).
+  1. [Delete service accounts you created](../../iam/operations/sa/delete.md).
+  1. [Delete the log group](../../logging/operations/delete-group.md).
 
 - {{ TF }} {#tf}
 
-  1. In the command line, go to the directory with the current {{ TF }} configuration file with an infrastructure plan.
-  1. Delete the `k8s-cluster-with-log-group.tf` configuration file.
-  1. Check that the {{ TF }} configuration files are correct using this command:
-
-     ```bash
-     terraform validate
-     ```
-
-     If there are any errors in the configuration files, {{ TF }} will point them out.
-  1. Confirm updating the resources.
-
-     {% include [terraform-apply](../../_includes/mdb/terraform/apply.md) %}
-
-     All the resources described in the `k8s-cluster-with-log-group.tf` configuration file will be deleted.
+  {% include [terraform-clear-out](../../_includes/mdb/terraform/clear-out.md) %}
 
 {% endlist %}