Docs: 404 on all resources from https://operator.docs.scylladb.com/stable/resources/overview#cluster-scoped-resources

[mykaul]

What happened?

Any resource you click on -> 404

What did you expect to happen?

Docs appear.

How can we reproduce it (as minimally and precisely as possible)?

Click on any resource.

Scylla Operator version

1.15

Kubernetes platform name and version

N/A

Please attach the must-gather archive.

N/A

Anything else we need to know?

No response

[mflendrich]

duplicate of the #2270 (comment) comment, already fixed in #2499.

I'll close this when the change rolls out and the live docs are confirmed fixed

[mflendrich]

Okay - It seems that the docs site is not rendering links as expected.

On the resources overview page, the "Learn more" links have an absolute path that removes the first segment (latest, v1.15) and results in a 404 despite the markdown definitions being relative.

The reason this was not caught in review is that the make preview renders the pages with a different context path (without the version prefix in the context path) and therefore the bug did not manifest there.

@annastuchlik can you help us understand why the paths are rendered incorrectly?

[annastuchlik]

The expected outcome is a link with a component that either specifies the version or is stable (i.e., the latest stable version).
For example, the following links will work:
https://operator.docs.scylladb.com/stable/quickstarts/index.html https://operator.docs.scylladb.com/v1.15/quickstarts/index.html https://operator.docs.scylladb.com/v1.16/quickstarts/index.html
but this will never work:

https://operator.docs.scylladb.com/quickstarts/index.html

I think that the reason is that the {grid-item-card} components have relative paths, for example:
[Learn more »](./nodeconfigs.md).
As a workaround, you may consider replacing them with full folder paths, as it is done on the main index page, for example:
[Learn more »](support/overview)

However, I'm not sure why links using the ./ prefix don't work in multiversion.
@dgarcia360 Can you look into it?

[ylebi]

As a workaround, you may consider replacing them with full folder paths, as it is done on the main index page, for example:
Learn more »

Reopening.
Looks like it didn't fix the issue.

[zimnx]

Weird, I tested your PR locally and links were working fine. Maybe multiversion builds are only affected.

[ylebi]

Weird, I tested your PR locally and links were working fine. Maybe multiversion builds are only affected.

Correct, the issue is with multiversion.