Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Chart
GitLab Chart
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 484
    • Issues 484
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 31
    • Merge Requests 31
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • charts
  • GitLab ChartGitLab Chart
  • Issues
  • #2075

Closed
Open
Opened May 11, 2020 by Dustin Collins@dustinmm80Developer

Auto-stop successful GKE review environments after X days

To be more efficient with GKE cloud-native cluster resources, we should automatically stop review environments that have been up for X days. We need to decide what X makes sense for our enviroment.

Currently, running stale review environments in GKE are taking up cluster resources, causing high CPU and memory usage. This causes other gke_review jobs to fail when the cluster resources are not available. This seems to happen often, requiring manual intervention from Distribution engineers.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/charts/gitlab#2075