Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • D drupalSite-operator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drupal
  • paas
  • drupalSite-operator
  • Issues
  • #16

Closed
Open
Created Dec 10, 2020 by Konstantinos Samaras-Tsakiris@kosamaraOwner0 of 1 task completed0/1 task

Filter watches on generic resources that we watch by label [performance]

This should significantly affect cluster performance in production.

  • @kosamara started a discussion: (+1 comment)

    @rvineetr all these owns clauses trigger reconciliations for the resource's owner, even if that isn't us: Watches(&source.Kind{Type: <ForType-forInput>}, &handler.EnqueueRequestForOwner{OwnerType: apiType, IsController: true}) (ref). I think we need to play with predicates and filter on a label, so that we don't produce that many unnecessary reconciliations. Imagine how many Svc/Jobs/etc that we don't own might be running on the cluster ;)

    Feel free to follow this up on another MR by making a follow-up issue.

Assignee
Assign to
Time tracking