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
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
The current (from 2018-04-27) status of quay.io/coreos/hyperkube as reported in upstream announcement is:
[we] don't plan on releasing images for the 1.11 series. If you currently depend on
our quay images, the k8s.gcr.io ones are a drop in replacement.
However, the GCR image is unfortunately not a drop-in replacement. The kubelet-wrapper consumes the ACI image out of quay.io. Such transport format is not supported by gcr.io.
This means that just changing the ${KUBELET_IMAGE_URL} to GCR will fail when trying to discover the ACI endpoint (run: discovery failed).
For this to work, it will additionally require an explicit docker:// schema and --insecure-options=image.
However I'm not exactly sure if this can be done in a compatible way without breaking existing users that customized the image/tag it via a drop-in (IIRC tectonic does this).
I'm still not optimistic that we can accommodate all usecases in retro-compatible way, at least not without making the script a shell-soup.
After quick brainstorming, some alternative options that have been suggested:
investigate quay.io support for auto-mirroring and syncing images from GCR
put the kubelet-wrapper in maintenance mode, track down and change all documentation around it, announce to the user-list that support stops at 1.10.x and newer versions of kubernetes requires a different service config (as mentioned above)
Automirroring in coming in Quay next quarter, which is probably too late. Perhaps we could make an internal scheduled job to manually mirror from GCR until then? A bit of shell-soup, but should definitely work, and we could remove after Quay adds the functionality.
It was very easy for me to move from quay.io to the docker gcr.io , i am using a systemd drop in /etc/systemd/system/kubelet.service as documented here
The current (from 2018-04-27) status of
quay.io/coreos/hyperkube
as reported in upstream announcement is:However, the GCR image is unfortunately not a drop-in replacement. The kubelet-wrapper consumes the ACI image out of quay.io. Such transport format is not supported by gcr.io.
This means that just changing the
${KUBELET_IMAGE_URL}
to GCR will fail when trying to discover the ACI endpoint (run: discovery failed
).For this to work, it will additionally require an explicit
docker://
schema and--insecure-options=image
.However I'm not exactly sure if this can be done in a compatible way without breaking existing users that customized the image/tag it via a drop-in (IIRC tectonic does this).
/cc @coverprice
The text was updated successfully, but these errors were encountered: