Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Optimize Status Updates in the Scan Controller to reduce number of write conflicts #29

Closed

Description

@J12934

When the controller / operator is updating the status of a scan it can come to write conflicts as the status of a Scan has been altered between the time the controller fetched the resource and send the update request.

The most likely reason this happens is that the controller updates the status more than once in a reconciliation cycle. When this happens the operator takes to cycles to properly update the scan which is unnecessary and pollutes the logs.

Desired behavior

The number of conflicts should be reduced by optimizing the Scan controller.

Notes

Currently especially the handling of hooks seems to have at least one of these problems

Activity

  1. self-assigned this
    on Jun 30, 2020
  2. added 3 commits that reference this issue on Jun 30, 2020
  3. linked a pull request that will close this issuePrevent duplicated hooks #44on Jul 2, 2020
  4. added 3 commits that reference this issue on Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions