-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TAS policy update #60
Comments
@togashidm is there more detail on this issue? It would be good if there are steps to recreate |
Some more details on the issue. TAS running with the initial health demo-policy: kubectl apply -f health-policy.yaml See logs below that when the target value is changed from 2 to 5. The same happens when changes to 7. Nothing happens when the target value is a return to 2. That is, TAS is considering the updated policy while running in the cluster as an addition. — Initial — — Target value Updated from 2 to 5 ---- — Target value Updated from 5 to 7 ---- — Target value Updated from 7 to 2 ---- |
An issue has appeared when trying to update a running TAS policy. If the target values in the policy specs under some strategy rule are changed, the new value should replace the old value. However, the new value is added as a new rule to that strategy. This issue is being investigated with the already raised issue #56 for which a resolution is to be released in the coming weeks.
The text was updated successfully, but these errors were encountered: