)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":33330,"name":"Karl Kloppenborg","email":"k@rl.ag","username":"karl_kloppenborg"},"change_message_id":"7ddd1e3ae2a88b872ae12429d604b5627ed9636c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b54ccd01_c63c7d82","updated":"2023-04-11 03:40:39.000000000","message":"If we\u0027re going to be doing this, can we also remove any docker.io references? because currently this ends up with getting rate limited.\n\nWe should encourage users to setup a proxy/private registry anyways.","commit_id":"97ce6d7d8e9a090c748800d69a57bbd9af698b60"},{"author":{"_account_id":3009,"name":"Vladimir Kozhukalov","email":"kozhukalov@gmail.com","username":"kozhukalov"},"change_message_id":"19d8ff2448d1332450e456f60d60c4d0e9800202","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ce2acc4e_5f189b75","in_reply_to":"b54ccd01_c63c7d82","updated":"2023-04-11 04:27:53.000000000","message":"Yes, this is a good idea. The easiest way to deal with docker hub rate limiting is to setup a pull through cache registry how described here https://docs.docker.com/registry/recipes/mirror/ In this case you can still use original image URLs, but nodes will not pull images twice. For many cases this should be a good solution.\n\nI\u0027ll add this to my TODO list (use pull through cache for test env and update user documentation and recommend using this for their envs).\n\nIn case users have their private registries (and we have a helm chart to deploy registry), they can override docker.io via values.yaml (also worth it to to mention this in the user docs).","commit_id":"97ce6d7d8e9a090c748800d69a57bbd9af698b60"}]}