Description of problem:
There is no "virtualHostedStyle" option when cluster is upgrade from 4.4 to 4.5 latest nightly build.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start a 4.4.z stable build
2.Define regionEndpoint or not - optional
3.Upgrade to 4.5 latest nightly build
There is no option virtualHostedStyle after upgrade.
There should be an option virtualHostedStyle to indicate true/false
Created attachment 1690989 [details]
Image registry operator log
This parameter works only when regionEndpoint is set. When it's unset, virtualHostedStyle should have the backward compatible value, i.e. "false".
If someone has a script that patches regionEndpoint after the installer finishes its job, "false" won't break this script. "true" will break this script, i.e. the default "true" it's not backward compatible.
I'm going to update the default to be "false". Thanks for catching this.
I can see below env var by accessing pod env list, but still no option in configs.imageregistry exposed by default after upgrade:
$ oc set env pods/image-registry-564d4fdb7b-6vtkk --list | grep REGISTRY_STORAGE_S3_VIRTUALHOSTEDSTYLE
Whether the option "virtualHostedStyle" should display after upgrade in configs.imageregistry?
No, it shouldn't. No value and false have the exact same meaning.
OK, thanks, then this bug can be verified now.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.