-
Notifications
You must be signed in to change notification settings - Fork 11
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
Explicitly reconcile firewall deployment in maintenance time window. #397
Explicitly reconcile firewall deployment in maintenance time window. #397
Conversation
…deployment-in-maintenance
needs rebase |
if !gardener.EffectiveShootMaintenanceTimeWindow(cluster.Shoot).Contains(time.Now()) { | ||
// note that this prevents updating the firewall image even when annotating the shoot explicitly with the maintainenance annotation | ||
// if a user wants to update the firewall immediately he needs to specify the new firewall image in the spec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might not work in all cases, e.g. if the image is already at the latest version. Therefore i propose to skip this check if the reconcile annotation is present. WDYT ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately the controller never sees a reconcile or maintenance annotation in these resources. If we remove this check it will update the firewall potentially outside the maintenance time window when changing something in the infrastructure config (e.g. when adding an egress rule or something like that).
So if a user wants like to immediately update outside the maintenance time window with a shorthand image, he needs to change to a specific firewall image instead.
References metal-stack/firewall-controller-manager#43, metal-stack/firewall-controller-manager#53.