Cloud Services

Container Cluster Management

Google Cloud Platform
Published On Jun 05, 2024 - 1:31 PM

Google Cloud Platform

Container Cluster Management to pull data from Google Cloud Platform, we must configure a Google Cloud Platform account or project.
In the context of Google Cloud Platform support, Container Cluster Management also supports Google Cloud Monitoring tools.

Configure GCP for Container Cluster Management

Access Rights
: The project (Account) should have a service account of that particular project, and have access or at least Project Viewer role and, Create New key in JSON Format is useful to create or configure Container Cluster Management to pull data from Google Cloud Platform.
The Google Cloud Platform requires the following steps to create a Key respective Service account.
Step 1
:  Navigate to the Google Cloud Platform console at
https://console.cloud.google.com
Step 2
: Select the project that you want to monitor. Note down the project ID.
Step 3
: Confirm that the correct project is open on the dashboard.
Step 4
: From the left navigation pane, select
IAM & Admin
 >
Service Accounts
Step 5
: Select
CREATE SERVICE ACCOUNT
on the Service Accounts page. The
Create service account
 dialog box is displayed. Enter the account name.
Step 6
: On the Service Accounts page, in Role, select the
Project
 ->
Viewer
 role.
Step 7
: Optionally, grant users access to this service account and finalize by selecting Done.
Step 8
: Now, you will be redirected to the service accounts page. Here, select the service account's email address that you have created.
Step 9
: Select the Keys tab.
Step 10
: Click the Add key drop-down menu, then select Create new key.
Step 11
: Select JSON as the Key type and select Create. Selecting Create downloads a service account key file. After you download the key file, you cannot download it again.
At this point you have successfully configured GCP to exchange data with Kyndryl Container Cluster Management.

IAM connection

Once all configuration steps has been completed at a cloud provider level, you will need to configure the tenant in order to continue with the data exchange for cluster management.

Pre-requisites

Complete configuration on the Cloud Provider console.
Step 1:
 From the tenant landing page, select the Main menu or the
Manage IAM
 tile.
Step 2:
 Select Admin and then, select 
IAM
.
Step 3:
 On the IAM screen, select the
Connections
 tab from the left panel.
Step 4:
 Select the
Add New
 drop-down menu.
Step 5:
 Select the
Add a Connection
.
Step 6:
 Select the Technology Category as
Cloud Provider
.
Step 7:
 Select
GCP
.
Step 8:
 Enter the
Project Id
 and
Service Key
 from the GCP account referred to in the previous section.
Step 9:
 Validate your credentials by selecting
Test connection
.
Step 10:
 Once the connection is successful, select
Add
 to create a connection.
The visuals featured in this content were posted in April 2022. This implies that if you attempt these setups, Kyndryl is not liable or responsible for any errors or omissions caused by third-party content changes. For image revisions or clarifications, please contact support.

Configuring GCP Monitor

Prerequisite: You must create a Service Account and assign it the following roles or the permissions described on each role (applies to all metricsets):
  • Monitoring Viewer:
    • monitoring.metricDescriptors.list
    • monitoring.timeSeries.list
  • Compute Viewer:
    • compute.instances.get
    • compute.instances.list 
Use the following template to set these roles: 
metricbeat.modules:
- module: gcp
  period: 900s
  continuous: true
  project_id: "<project-id>"
  credentials_file_path: "<credentials-path>"
  exclude_labels: false
  metricsets: 
    - metrics
  metrics:
    - service: gke
      service_metric_prefix: kubernetes.io/
      metric_types:
      - "container/cpu/core_usage_time"
      - "container/cpu/limit_cores"
      - "container/cpu/limit_utilization"
      - "container/cpu/request_cores"
      - "container/cpu/request_utilization"
      - "container/memory/limit_bytes"
      - "container/memory/limit_utilization"
      - "container/memory/page_fault_count"
      - "container/memory/request_bytes"
      - "container/memory/request_utilization"
      - "container/memory/used_bytes"
This template yields the following YAML configuration, containing the query to fetch CPU and Memory stats and it is added in CMS:
metricbeat.modules:
- module: gcp
  period: 24h
  continuous: true
  exclude_labels: false
  metricsets: 
    - metrics
  metrics:
    - service: gke
      service_metric_prefix: kubernetes.io/
      aligner: ALIGN_MAX
      metric_types:
      - "container/cpu/limit_cores",
            - "container/cpu/limit_utilization",
            - "container/cpu/request_cores",
            - "container/cpu/request_utilization",
            - "container/memory/limit_bytes",
            - "container/memory/request_bytes",
            - "container/memory/used_bytes",
Do you have two minutes for a quick survey?
Take Survey