A user complains about “As a user, I can expect container repo names to follow the latest standard (#37988, 9c985331)” not being visible as a breaking change.
Should we add this as an upgrade warning even with 4.17 on the horizon? Very likely not all have upgraded yet to be affected.
