remove broken links to examples

[dkarczmarski]

fix broken links to the kubernetes-examples repo

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	11f3b78
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/690b56e81d296e00087c4405
😎 Deploy Preview	https://deploy-preview-53020--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Gauravpadam]

Thanks @dkarczmarski for the contribution!

Other than the blog edit, LGTM for the rest of changes

[dkarczmarski]

Thanks @dkarczmarski for the contribution!

Other than the blog edit, LGTM for the rest of changes

@Gauravpadam
ok. I removed that change for that file :)

[Gauravpadam]

/lgtm

Thanks!

[dipesh-rawat]

@soltysh I noticed you originally archived these kubernetes/examples (as part of kubernetes/examples@8b3fa9a) and wanted to get your take. Do you think we should update the links, or remove them from the docs entirely because they’re no longer supported?
Thanks, and apologies for the ping!

[lmktfy]

Rather than link to archived content, we should remove the links.

@dkarczmarski would you be willing to do that instead?

/lgtm cancel

[lmktfy]

/remove-area blog

[dkarczmarski]

Rather than link to archived content, we should remove the links.

@dkarczmarski would you be willing to do that instead?

/lgtm cancel

@lmktfy

I found the PR that moved it to the _archived directory :
kubernetes/examples#564 .
he said :

As discussed in sig-apps meeting on 5/12 we are starting to cleanup this repository.

The initial take is to move all (almost 😉) to _archived/ directory, from where we'll go one by one and try to revive the examples which still work, and over time drop everything else.

so as I understand it, it does not mean that it will be definitely removed, but it might be removed or it might be revived.
so maybe it is better to update the links to '_archived' version for now ? it is easier to update the link than to insert it again after it has been removed. I can open an issue in the 'examples' project and ask them to notify us when the work on '_archived' directory is done.

how do you think ?

[soltysh]

so as I understand it, it does not mean that it will be definitely removed, but it might be removed or it might be revived.
so maybe it is better to update the links to '_archived' version for now ? it is easier to update the link than to insert it again after it has been removed. I can open an issue in the 'examples' project and ask them to notify us when the work on '_archived' directory is done.

Please do not over interpret my wording. It's moved to _archived on its way to be either fixed or removed. All of the PRs fixing the links in the docs ideally should not be pointing users to broken examples, and the current are just that - broken. So it's better not to have those links available at all. So just like Tim pointed above, please REMOVE the links.

[dkarczmarski]

@soltysh
thank you for your comment. I have no doubts now. I will do just that :)

[soltysh]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 8a4fb5e1f3420152e2ad7c6b98a71f991d3733a5

[dipesh-rawat]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dipesh-rawat, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS [dipesh-rawat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment