Remove WeaveWorks URLs from Kubernetes Documentation Website about website HOT 7 OPEN

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from website.

/language en
/sig docs

from website.

I don't think we want to remove this just because the company originally behind it is out of business. It is an open source project that at least appears to be living on.

from website.

Hello @stmcginnis ,
Yes, as I proposed in my issue we can Remove or replace these URLs with alternative resources to ensure the documentation remains accurate and useful.

Because their website (https://www.weave.works/) is officially decommissioned and not accessible anymore.

from website.

So this seems to be coming up a bunch of other issues as well, #45201 and a few other issues/prs. So i think its worth talking about to get on the same page about what to do about the links.

Consider updating documentation guidelines to periodically review and update third-party URLs.

I'm not sure if there was ever a conversation around this when we put together the third party content policy. I think we generally rely on the community to help keep the links updated, as we might not have the depth of knowledge or dedicated resources to always staff doing this research with in the SIG.

from website.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from website.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from website.