Skip to content

Renaming a ConsumptionQuota silently disables enforcement until controller pod restart #16

Description

@BergCyrill

Deleting & Creating a ConsumptionQuota for the same resource currently leaves the old controller running so a new cannot be established (since they are named based upon resource + identityHash so the controller name will be the same).

 unable to ensure accounting informer {"cq":"buckets-limit",
   "error":"building governed-usage controller: controller with name
    governed-usage-buckets-ae11d60a already exists..."}

Besides not able to reregister it now fails open, leaving the strong enforcement.

Repro

Repro: create a CQ, delete it, create another governing the same resource without restarting.

Suggested test

Ensure → Remove → Ensure for one key

Activity

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions