Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • See what's new at GitLab
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,552
    • Issues 34,552
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,134
    • Merge Requests 1,134
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #5029

Closed
Open
Opened Oct 04, 2017 by Joshua Lambert@joshlambertMaintainer

Add CPU & Memory metrics to k8s cluster page

Description

As a first step towards https://gitlab.com/gitlab-org/gitlab-ce/issues/27890, we should show some basic health metrics about the cluster.

We should include:

  • CPU Cores Used vs. Available
  • Memory % Used vs. Available
  • gitlab-ce~992792 would be to also provide a series for requested CPU/Memory as well.
  • Pod limit (currently 100 per Node)

100% utilization in this case would be all Cores/RAM available within the cluster. (Summarization of the Node CPU/RAM)

If we can achieve this, we will be delivering more value than what can be obtained easily via the k8s console.

Proposal

We can gather the % used today, but to gather the amount requested we will need to deploy kube-state-metrics.

The general actions:

  • Deploy kube-state-metrics along with Prometheus for managed clusters. If a cluster already had Prometheus deployed, we should deploy this as well. We will need to think about the scaling needs.
  • Add the charts to the cluster management page. Will need UX input on this.

Edited Jan 26, 2018 by Mark Pundsack
Assignee
Assign to
10.6
Milestone
10.6 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#5029