Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • C CRS Catalog
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe Software
  • Platform
  • System
  • Reference and Helper Services
  • CRS Catalog
  • Merge requests
  • !52

Add node selector

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Dzmitry_Paulouski (slb) requested to merge add_node_selector into master Jun 14, 2021
  • Overview 3
  • Commits 4
  • Pipelines 8
  • Changes 3

All Submissions:

[YES] Have you followed our code review guidelines? [YES] Have you added an explanation of what your changes do and why you'd like us to include them? [NO] I have updated the documentation accordingly. [NA] I have added tests to cover my changes. [YES] All new and existing tests passed. [YES] My code follows the code style of this project. [YES] I ran lint checks locally prior to submission.

What is the current behavior?

Currently, we have only one node pool for services and system workloads.

What is the new behavior?

We are going to move workloads to a new node pool with enabled autoscaling. Here you can find the details: Issue link

Does this introduce a breaking change?

[NO]

This change has a strong dependency on the following MR and should be merged only after it: osdu/platform/deployment-and-operations/infra-azure-provisioning!324 (merged)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: add_node_selector