DOC-7003 retarget dead k8s API anchors to the local reference

[andy-stark-redis]

Third PR for DOC-7003, covering Part A2 — the Kubernetes API anchor retargets.
Independent of #3863 and #3864, based directly on main, so it can be reviewed and
merged on its own.

The problem

Upstream restructured redis_enterprise_cluster_api.md and
redis_enterprise_database_api.md on master: each file now contains exactly one
heading, so every Go-type anchor we linked (#ldapspec, #ssospec,
#redisenterpriseclusterspec, #redisenterprisedatabasespec) is gone. Four live pages
pointed at them.

Instructive detail from the audit worth keeping in mind for the house rules in a later
PR: our pinned-SHA links to these same upstream files still resolve. Pinning survived;
master rotted.

The judgment calls

The ticket flagged this as not a mechanical retarget, and it isn't — the local pages are
organised by field path (### spec.ldap), not by Go type name, and the string
LdapSpec appears nowhere in them. Each link was resolved on what its sentence promises:

Page	Was	Now	Reasoning
security/authentication/ldap.md:50	#ldapspec	…cluster_api#specldap	Section opens "Cluster-level LDAP configuration, such as server addresses, protocol, authentication and query settings" — matches the "full details on the available fields" the sentence offers
security/authentication/sso.md:364	#ssospec	…cluster_api#specsso	Section opens "Cluster-level SSO configuration for authentication to the Cluster Manager UI"
recommendations/node-resources.md:45	#redisenterpriseclusterspec	…cluster_api#spec	Link text is the bare RedisEnterpriseCluster identifier, so the whole spec table is the faithful target; narrowing to #specredisenterprisenoderesources would make the link say something the sentence doesn't
re-databases/db-controller.md:91	#redisenterprisedatabasespec	link deleted	The same line already carried a relref to that exact page. Retargeting would have produced the same link twice, so the dead one came out

Per content/operate/kubernetes/AGENTS.md, the RedisEnterpriseCluster link text is left
exactly as it is — custom resource identifiers are never reworded.

These anchors are more stable than the ones they replace

Not by luck. k8s_apis_sync.yaml runs a sed pass over crdoc's output that strips the
RedisEnterpriseCluster. prefix from every heading, which is why the headings read
### spec.ldap. The anchor scheme is ours, not upstream's — these links now rot only
if we change our own sync workflow, rather than whenever upstream renames a Go type.
Recorded as a Constraint: trailer on the commit so a future edit to that sed knows what
depends on it.

Verification

Built the site and checked the rendered ids, not assumed slugs — the ticket specifically
warned not to assume the slug for headings containing dots. The dots are stripped:
### spec.ldap renders as id="specldap".

Check	Result
id="spec", id="specldap", id="specsso" on the built cluster API page	all present
id="spec" on the built database API page	present
Rendered hrefs on all four edited pages	resolve to those exact anchors
href="" on the four edited pages	zero — no relref silently failed
Topical fit of each target section	confirmed by reading the section's lead sentence, not just matching the name

Only the unversioned current pages are touched. The same dead anchors appear across the
7.22/, 7.8.x/ and 8.0/ snapshots; per AGENTS.md a current-version change is never
propagated backward into a frozen snapshot, and the ticket scopes archived trees out.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only link fixes with no runtime, security, or configuration behavior changes.

Overview
Replaces dead upstream GitHub API anchors (removed when redis-enterprise-k8s-docs restructured headings) with in-site relref links to the synced Kubernetes API reference pages.

On LDAP and SSO auth docs, the RedisEnterpriseCluster API reference now points to #specldap and #specsso on redis_enterprise_cluster_api. Node resources links RedisEnterpriseCluster to #spec instead of #redisenterpriseclusterspec. Database controller drops the redundant GitHub RedisEnterpriseDatabaseSpec link because the same line already links to the local database API page.

^{Reviewed by Cursor Bugbot for commit 0c6d85e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

DOC-7003

[github-actions]

Staging links:
https://redis.io/docs/staging/DOC-7003-k8s-api-retargets/operate/kubernetes/re-databases/db-controller/
https://redis.io/docs/staging/DOC-7003-k8s-api-retargets/operate/kubernetes/recommendations/node-resources/
https://redis.io/docs/staging/DOC-7003-k8s-api-retargets/operate/kubernetes/security/authentication/ldap/
https://redis.io/docs/staging/DOC-7003-k8s-api-retargets/operate/kubernetes/security/authentication/sso/

[github-actions]

🧠 Redis Memory

Found 5 related items from repository history (5 new this commit):

• PR — DOC-7003 fix dead and brittle links in the develop docs 🆕

  Second of four PRs for DOC-7003, covering Part A1, A3 and A4 — the develop/ link

• Commit — DOC-7003 fix dead and brittle links in the develop docs 🆕

  DOC-7003 fix dead and brittle links in the develop docs

• PR — DOC-6955 Repoint the Google ADK links at Agent Memory's new home 🆕

  Fixes DOC-6955. Ten relref calls across three Google ADK pages named Agent Memory paths

• PR — DOC-6909 Fix pre-existing broken links across the docs 🆕

  Part 1 of 4 of a stack that splits DOC-6909 Add link render hook to replace relref (investigation) #3732 into independently reviewable pieces, after @paoloredis noted the single PR was too much to review

• PR — DOC-7003 document RESP3 streamed types in the protocol spec 🆕

  First of four PRs for DOC-7003. Adds two sections to the protocol spec page so the

Memory updated at 0c6d85e