[doc] Issue in "Component Versions" - Registry FQDN?

[peteingithub]

Component Versions:

https://documentation.suse.com/suse-edge/3.4/single-html/edge/#id-component-versions

Points to registry.suse.com here.
https://documentation.suse.com/suse-edge/3.4/single-html/edge/#suse-storage-install has registry.rancher.com.

Which one is correct?

[e-minguez]

Both are the same:

❯ dig +short @8.8.8.8 registry.suse.com
abb6b777297e9c2b1.awsglobalaccelerator.com.
75.2.43.231
99.83.188.102

❯ dig +short @8.8.8.8 registry.rancher.com
abb6b777297e9c2b1.awsglobalaccelerator.com.
75.2.43.231
99.83.188.102

and

❯ crane ls registry.rancher.com/rancher/mirrored-longhornio-csi-attacher
v2.2.1-lh1
v2.2.1-lh2
v3.2.1
v3.4.0
v4.2.0
v4.4.2
v4.5.1
v4.6.1
v4.7.0
v4.7.0-20241219
v4.8.0
v4.8.1
v4.9.0
v4.9.0-20250709

❯ crane ls registry.suse.com/rancher/mirrored-longhornio-csi-attacher
v2.2.1-lh1
v2.2.1-lh2
v3.2.1
v3.4.0
v4.2.0
v4.4.2
v4.5.1
v4.6.1
v4.7.0
v4.7.0-20241219
v4.8.0
v4.8.1
v4.9.0
v4.9.0-20250709

Given said that, I agree we should be consistent. @ranjinimn would you mind taking a look at this? Thanks!

[ranjinimn]

@peteingithub @e-minguez Following are the changes I intend to make:

embeddedArtifactRegistry:
  images:
    - name: registry.suse.com/rancher/mirrored-longhornio-csi-attacher:v4.9.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-csi-node-driver-registrar:v2.14.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-csi-provisioner:v5.3.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-csi-resizer:v1.14.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-csi-snapshotter:v8.3.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-livenessprobe:v2.16.0-20250709
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-engine:v1.9.1
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-instance-manager:v1.9.1
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-manager:v1.9.1
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-share-manager:v1.9.1
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-ui:v1.9.1
    - name: registry.suse.com/rancher/mirrored-longhornio-support-bundle-kit:v0.0.52
    - name: registry.suse.com/rancher/mirrored-longhornio-longhorn-cli:v1.9.1

I see that the code block does not have registry.suse.com/rancher/mirrored-longhornio-backing-image-manager:v1.9.1, Should I include that as well?

Also, the "Modifications in the definition file" section has registry.rancher.com/rancher/ for Longhorn and Neuvector. Should I replace that with registry.suse.com?

[e-minguez]

Just in case, let me summon @dprodanov4 as he is our release manager expert :) to confirm this.

[hardys]

I think we need to proceed quite carefully with any renaming - although we know the two dns records point at the same registry, we have systemDefaultRegistry configuration which references registry.rancher.com which won't work if we switch all the embeddedArtifactRegistry paths to registry.suse.com

We have the same problem if there are any fully qualified image references in any chart that refers to registry.rancher.com - we can't just switch the mirrored image to a different path in that case so any global replacement carries a pretty high risk of regression IMO.

Since this is a cosmetic issue, I'd suggest we perhaps de-prioritize the fix and/or make any changes incrementally with careful testing, just to make sure we don't accidentally break anything.

[ranjinimn]

Sure @hardys Let me know when the testing is complete. I will put this on hold for now.

[peteingithub]

@hardys
My point with this is solely cosmetic (as almost always), not technically oriented at all. :)

I'm not talking about renaming a repo, but about changing one part of the Edge documentation
to match with the other. Since the two URLs seem to point to the same content (if I have not
misunderstood), would it be possible to only have one (the "more correct") included in the
documentation.

Minor change, priority low.

[hardys]

Ah thanks for clarifying @peteingithub - if we can resolve this by only updating the release notes table, then I'm fine with doing it now - my main concern is we shouldn't change the EIB examples or other docs without testing, as it has the possibility of breaking in some cases.

[ranjinimn]

@hardys I see that the release notes table is updated with registry.suse.com.

Can you please let me know the changes I need to make for the reported issue?

https://documentation.suse.com/suse-edge/3.4/single-html/edge/#id-component-versions
Points to registry.suse.com here.
https://documentation.suse.com/suse-edge/3.4/single-html/edge/#suse-storage-install has registry.rancher.com.