-
Notifications
You must be signed in to change notification settings - Fork 21
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
HA: ensure s3gw backend image is preloaded on every k8s node #734
Labels
area/kubernetes
k8s and related
Comments
giubacc
changed the title
Ensure s3gw backend image is preloaded on every k8s node
HA: ensure s3gw backend image is preloaded on every k8s node
Oct 2, 2023
cc @m-ildefons |
jecluis
added
priority/0
Needs to go into the next release or force a patch
area/kubernetes
k8s and related
LH 1.6
and removed
triage/waiting
Waiting for triage
labels
Oct 15, 2023
After checking with @l-mb and @m-ildefons , we believe it's better to push this to after v0.23.0. That frees @m-ildefons to focus on pushing for the initial version of LH controller without adding new requirements, and grants us time to figure out what's the best approach to deal with this. |
jecluis
added
priority/1
Should be fixed for next release
and removed
LH 1.6
priority/0
Needs to go into the next release or force a patch
labels
Oct 25, 2023
We believe this is no longer something we should focus on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to be done
We need to ensure that the s3gw backend image is preloaded on every k8s node.
Failing to guarantee this implies that if the s3gw is scheduled to load on a node where the s3gw image is not cached, the system should pay the time needed to download the image from the registry before starting it.
In general on Kubernetes, it can not be assumed that an image is pre-pulled, since nodes may come and go dynamically.
Pre-pulled images is something we do want to ensure for eligible nodes. Otherwise, our restart is unpredictably long.
It's always possible that a fault occurs exactly at the time where we are pre-loading the image, but that's just bad luck.
Why it needs to be done
This requirement is needed by the s3gw HA model: Active/Standby.
Acceptance Criteria
Additional Information
The text was updated successfully, but these errors were encountered: