Skip to content

Designing Lean Operators #6581

Closed
Closed

Description

@fgiloux

The page needs to be updated.

There was a breaking change in controller-runtime so that BuilderWithOptions has been removed.
The use case should now be covered by cache.Options, the ByObject field being now a map.

Controller-runtime design document: https://github.com/kubernetes-sigs/controller-runtime/blob/main/designs/cache_options.md

Activity

  1. acornett21 commented on Sep 25, 2023

    @acornett21
    Contributor
  2. fgiloux commented on Sep 25, 2023

    @fgiloux
    ContributorAuthor

    Changes introduced in v0.15.0
    SDK currently using v0.14.1.
    Thanks for linking the bump issue.

  3. added this to the Backlog milestone on Oct 2, 2023
  4. added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 2, 2023
  5. openshift-bot commented on Jan 1, 2024

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 1, 2024
  7. fgiloux commented on Jan 2, 2024

    @fgiloux
    ContributorAuthor

    /remove-lifecycle stale

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 2, 2024
  9. fgiloux commented on Jan 2, 2024

    @fgiloux
    ContributorAuthor

    More relevant than even since #6613 has merged

  10. openshift-bot commented on Apr 1, 2024

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  11. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 1, 2024
  12. fgiloux commented on Apr 1, 2024

    @fgiloux
    ContributorAuthor

    /remove-lifecycle stale

  13. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 1, 2024
  14. openshift-bot commented on Jul 1, 2024

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  15. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions