IPE-1705: Linking Consul Multiport to Consul K8s multiport

[krastin]

Description

For better end user awareness, we are linking Consul Multiport to the K8s multiport implementation.
Also, for supported Consul versions that do not have Multiport enabled, we redirect to the K8s multiport workaround.

Links

Jira: IPE-1705

Contributor checklists

Review urgency:

• ASAP: Bug fixes, broken content, imminent releases
• 3 days: Small changes, easy reviews
• 1 week: Default expectation
• Best effort: No urgency

Pull request:

• Verify that the PR is set to merge into the correct base branch
• Verify that all status checks passed
• Verify that the preview environment deployed successfully
• Add additional reviewers if they are not part of assigned groups

Content:

• I added redirects for any moved or removed pages
• I followed the Education style guide
• I looked at the local or Vercel build to make sure the content rendered correctly

Reviewer checklist

• This PR is set to merge into the correct base branch.
• The content does not contain technical inaccuracies.
• The content follows the Education content and style guides.
• I have verified and tested changes to instructions for end users.

[github-actions]

Vercel Previews Deployed

Name	Status	Preview	Updated (UTC)
Dev Portal	✅ Ready (Inspect)	Visit Preview	Mon Aug 10 13:38:44 UTC 2026
Unified Docs API	✅ Ready (Inspect)	Visit Preview	Mon Aug 10 13:34:02 UTC 2026

[github-actions]

Broken Link Checker

This PR contains broken links, but won't be blocked. Use this report to improve content quality:

Quick Actions

• Internal links (HashiCorp sites): Please fix these - they impact user experience
• External links: Consider if these are essential or can be updated/removed
• Temporary issues: External sites may recover - check again before merging

Need Help?

• Review our Broken Link Monitoring docs
• Check the monthly production report for context

---

Internal Links

Full Github Actions output

External Links

Summary

Status	Count
🔍 Total	6
✅ Successful	0
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	6
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[aimeeu]

@krastin If I recall correctly, editing a prior version's redirects.jsonc file is not relevant. I think the build process only uses the most recent version's redirects.jsonc file when compiling the master redirect.json file.
We do have a redirects guide in the repo docs.