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
Currently, once the operator has parsed the HTTPScaledObject and generated the ScaledObject, it doesn't watch the ScaledObject until the operator is restarted. This isn't worth because the (add-on) operator is the owner of the ScaledObject and it should be always aware about any relevant change on it (even about deletions to recreate it)
Expected Behavior
The operator is the only owner of the generated ScaledObject and replaces any manual done change
Actual Behavior
The ScaledObject is created and ignored until a restart
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Mar 30, 2024
Report
Currently, once the operator has parsed the HTTPScaledObject and generated the ScaledObject, it doesn't watch the ScaledObject until the operator is restarted. This isn't worth because the (add-on) operator is the owner of the ScaledObject and it should be always aware about any relevant change on it (even about deletions to recreate it)
Expected Behavior
The operator is the only owner of the generated ScaledObject and replaces any manual done change
Actual Behavior
The ScaledObject is created and ignored until a restart
The text was updated successfully, but these errors were encountered: