Contact UsGet started

Transferring Yandex Managed Service for Kubernetes cluster logs to Cloud Logging

Written by
Updated at December 18, 2024

You can send Managed Service for Kubernetes cluster logs to Cloud Logging:

Sending master logs to Managed Service for Kubernetes in Cloud Logging using master logging

To set up the transfer of Managed Service for Kubernetes master logs to Cloud Logging:

  1. Enable the master logging setting.
  2. Check the result.

If you no longer need the resources you created, delete them.

Getting started

Prepare the infrastructure:

  1. If you do not have a network yet, create one.

  2. If you do not have any subnets yet, create them in the availability zones where your Managed Service for Kubernetes cluster and node group will be created.

  3. Create service accounts:

    • Service account for Managed Service for Kubernetes resources with the editor role for the folder where the Managed Service for Kubernetes cluster is created.

    • Service account for Managed Service for Kubernetes nodes with the container-registry.images.puller role for the folder containing the Docker image registry. Managed Service for Kubernetes nodes will pull the required Docker images from the registry on behalf of this account.

      Tip

      You can use the same service account for both operations.

  4. Assign the logging.writer role to the service account for resources. This role is required by the Managed Service for Kubernetes cluster to send logs to Cloud Logging.

  5. Create a Managed Service for Kubernetes cluster and a node group. When creating a Managed Service for Kubernetes cluster, specify the previously created service accounts for the resources and nodes.

  6. Configure security groups for the Managed Service for Kubernetes cluster.

  7. Create a log group.

  1. If you do not have Terraform yet, install it.

  2. Download the file with provider settings. Place it in a separate working directory and specify the parameter values.

  3. Download the k8s-cluster-with-master-logging.tf configuration file of the Managed Service for Kubernetes cluster to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security groups and rules required for a Managed Service for Kubernetes cluster and node group:
      • Rules for service traffic.
      • Rules for accessing the Kubernetes API and managing a Managed Service for Kubernetes cluster using kubectl through ports 443 and 6443.
      • Rules for accessing services from the internet.
    • Service account for resources and Managed Service for Kubernetes nodes and sending cluster logs to Cloud Logging.
    • Managed Service for Kubernetes cluster.
    • Managed Service for Kubernetes node group.
    • Cloud Logging log group.

  4. Specify the following in the configuration file:

    • Folder ID.
    • Kubernetes version for the Managed Service for Kubernetes cluster and node groups.
    • Name of the service account for resources and Managed Service for Kubernetes nodes and for sending cluster logs to Cloud Logging.
    • Cloud Logging log group name.

  5. Run the terraform init command in the directory with the configuration files. This command initializes the provider specified in the configuration files and enables you to use the provider resources and data sources.

  6. Check that the Terraform configuration files are correct using this command:

    terraform validate

    If there are any errors in the configuration files, Terraform will point them out.

  7. Create the required infrastructure:

    1. Run the command to view planned changes:

      terraform plan

      If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.

    2. If you are happy with the planned changes, apply them:

      1. Run the command:

        terraform apply

      2. Confirm the update of resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Enable the master logging setting

If you created the infrastructure manually, enable the master logging setting:

  1. If you do not have the Yandex Cloud command line interface yet, install and initialize it.

    The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

  2. Run this command:

    yc managed-kubernetes cluster update <cluster_name> \
  --master-logging enabled=true,`
    `log-group-id=<log_group_ID>,`
    `kube-apiserver-enabled=<send_kube-apiserver_logs:_true_or_false>,`
    `cluster-autoscaler-enabled=<send_cluster-autoscaler_logs:_true_or_false>,`
    `events-enabled=<send_Kubernetes_events:_true_or_false>`
    `audit-enabled=<send_audit_events:_true_or_false>

    Where:

    • enabled: Flag that enables sending logs.
    • log-group-id: ID of the previously created log group to send the logs to.
    • kube-apiserver-enabled: Flag that enables sending kube-apiserver logs.
    • cluster-autoscaler-enabled: Flag that enables sending cluster-autoscaler logs.
    • events-enabled: Flag that enables sending Kubernetes events.
    • audit-enabled: Flag that enables sending audit events.

Check the result

Check the transfer of Managed Service for Kubernetes master logs to the Cloud Logging log group.

Delete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy

    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Sending pod logs and service logs via Fluent Bit

To set up the transfer of Yandex Managed Service for Kubernetes pod and service logs to Yandex Cloud Logging:

  1. Install and configure Fluent Bit.
  2. Check the result.

If you no longer need the resources you created, delete them.

Getting started

Prepare the infrastructure:

  1. If you do not have a network yet, create one.

  2. If you do not have any subnets yet, create them in the availability zones where your Managed Service for Kubernetes cluster and node group will be created.

  3. Create service accounts:

    • Service account for Managed Service for Kubernetes resources with the editor role for the folder where the Managed Service for Kubernetes cluster is created.
    • Service account for Managed Service for Kubernetes nodes with the container-registry.images.puller role for the folder containing the Docker image registry. Managed Service for Kubernetes nodes will pull the required Docker images from the registry on behalf of this account.

    Tip

    You can use the same service account for both operations.

  4. Create security groups for the Managed Service for Kubernetes cluster and its node groups.

    Warning

    The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

  5. Create a Managed Service for Kubernetes cluster and a node group. When creating a Managed Service for Kubernetes cluster, specify the previously created service accounts for the resources and nodes as well as the security group.

  6. Create a log group.

  1. If you do not have Terraform yet, install it.

  2. Download the file with provider settings. Place it in a separate working directory and specify the parameter values.

  3. Download the k8s-cluster-with-log-group.tf configuration file of the Managed Service for Kubernetes cluster to the same working directory.

    This file describes:

    • Network.

    • Subnet.

    • Cloud Logging log group.

    • Managed Service for Kubernetes cluster.

    • Managed Service for Kubernetes node group.

    • Service account for Managed Service for Kubernetes resources and nodes.

    • Security groups which contain rules required for the Managed Service for Kubernetes cluster and its node groups.

      Warning

      The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

  4. Specify the following in the configuration file:

    • Folder ID.
    • Kubernetes version for the Managed Service for Kubernetes cluster and node groups.
    • Name of the service account for Managed Service for Kubernetes resources and nodes.
    • Cloud Logging log group name.

  5. Run the terraform init command in the directory with the configuration files. This command initializes the provider specified in the configuration files and enables you to use the provider resources and data sources.

  6. Check that the Terraform configuration files are correct using this command:

    terraform validate

    If there are any errors in the configuration files, Terraform will point them out.

  7. Create the required infrastructure:

    1. Run the command to view planned changes:

      terraform plan

      If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.

    2. If you are happy with the planned changes, apply them:

      1. Run the command:

        terraform apply

      2. Confirm the update of resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Install and configure Fluent Bit

Install Fluent Bit by following this guide. In the application settings, specify the ID of the log group you created earlier. You can request the log group ID with a list of log groups in the folder.

  1. Install kubectl and configure it to work with the created cluster.

  2. Create the objects required for Fluent Bit to run:

    kubectl create namespace logging && \
kubectl create -f https://raw.githubusercontent.com/fluent/fluent-bit-kubernetes-logging/master/fluent-bit-service-account.yaml && \
kubectl create -f https://raw.githubusercontent.com/fluent/fluent-bit-kubernetes-logging/master/fluent-bit-role-1.22.yaml && \
kubectl create -f https://raw.githubusercontent.com/fluent/fluent-bit-kubernetes-logging/master/fluent-bit-role-binding-1.22.yaml

  3. Create a secret containing the key of the service account:

    kubectl create secret generic secret-key-json \
  --from-file=key.json \
  --namespace logging

  4. Download the config.yaml configuration file:

    wget https://raw.githubusercontent.com/knpsh/yc-logging-fluent-bit-example/main/config.yaml

  5. Specify the log output parameters in the data.output-elasticsearch.conf section in config.yaml:

    ...
  output-elasticsearch.conf: |
    [OUTPUT]
      Name            yc-logging
      Match           *
      group_id        <log_group_ID>
      resource_id     <optional_cluster_ID>
      message_key     log
      authorization   iam-key-file:/etc/secret/key.json
...

    You can request the log group ID with a list of log groups in the folder.

    Specify additional settings for Fluent Bit, if required.

  6. Create Fluent Bit objects:

    kubectl apply -f config.yaml

    Result:

    configmap/fluent-bit-config created
daemonset.apps/fluent-bit created

  7. Make sure the Fluent Bit pod has entered the Running state:

    kubectl get pods -n logging

Check the result

Test the transfer of logs of Managed Service for Kubernetes pods and services to your Cloud Logging log group.

Delete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy

    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Previous
All tutorials
Next
Transferring logs from a VM instance to Cloud Logging