Remove redundant Kubernetes doc

[kate-goldenring]

The Kubernetes document is redundant to the linking we do in deploying.md. In general, when we remove a document, should we remove it from v1, v2 and v3? I just removed from v3 here

[itowlson]

It looks like we've removed the Kubernetes entry from the TOC, so there's no point keeping the page.

cc @flynnduism to confirm that this was intentional

[flynnduism]

The Deployment Options page and SpinKube menu entries make the Kubernetes path pretty clear, so IMO removing this is good.

We should include a redirect for the page being removed, so any prior /kubernetes paths go to the /deploy-options page

[kate-goldenring]

@flynnduism how do i add a redirect? Also should we delete the v1 and v2 doc as well?

[itowlson]

@kate-goldenring we used to do redirects like https://github.com/fermyon/developer/blob/cba4bb3594c04869d7e18d6a54e64ec782dbbc33/spin.toml#L90 and https://github.com/fermyon/developer/blob/cba4bb3594c04869d7e18d6a54e64ec782dbbc33/spin.toml#L266 - I am not sure if there is a New And Improved way though.

[itowlson]

@vdice Any guidance on redirects so we can close out the remaining request on this PR and get it in? Thanks!

[vdice]

@kate-goldenring adding the following to the spin manifest should work for these purposes:

[[trigger.http]]
id = "trigger-redirect-kubernetes"
component = "redirect-kubernetes"
route = "/kubernetes"

[component.redirect-kubernetes]
source = "modules/redirect.wasm"
environment = { DESTINATION = "/deploying", STATUSCODE = "301" }

(It looks like we already have the redirect module in the modules directory - must've been from the initial docs migration.)

should we remove it from v1, v2 and v3?

I'd vote yes. Potential inbound redirects from the developer.fermyon.com appear to all be unversioned, so I believe we're good there.

[kate-goldenring]

Thanks for bumping this @itowlson and adding the suggestion @vdice. I've updated it and ran locally to confirm the redirect works