You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resources are created out of order, speaking mostly about limitador resources, the removal of the kuadrant CR should undo the changes in limitador CR.
If you rerun the curl commands from the guide you will see the routes are no longer protect, which is expected. However if you check the limitador CR that was created before kuadrant, it still has all the limits which kuadrant placed.
This should not be the case. The removal of kuadrant should remove those limits. Only in the case were the user created the limitador resource before kuadrant does this issue apply.
The text was updated successfully, but these errors were encountered:
What
When resources are created out of order, speaking mostly about limitador resources, the removal of the kuadrant CR should undo the changes in limitador CR.
This is related to #1004
Steps to reproduce
Deploy an instance of limitador before running the RateLimitPolicy for Platform Engineers. Don't do the last cleanup step.
Remove the kuadrant CR.
If you rerun the curl commands from the guide you will see the routes are no longer protect, which is expected. However if you check the limitador CR that was created before kuadrant, it still has all the limits which kuadrant placed.
This should not be the case. The removal of kuadrant should remove those limits. Only in the case were the user created the limitador resource before kuadrant does this issue apply.
The text was updated successfully, but these errors were encountered: