-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://k8s.io/dockershim is marked outdated #31663
Comments
Right now, https://k8s.io/dockershim is a Hugo alias; PR #30840 would replace that with a Netlify redirect (experience suggests that these cause fewer issues). |
/retitle https://k8s.io/dockershim is marked outdated |
/assign rolfedh |
/assign |
/triage accepted |
BTW folks, which approach are we taking? I strongly favor adding a new article (which can be much the same as the one it replaces, just newer) rather than more complex & technical fixes. |
Could we bump the date forward? This FAQ is something I routinely point people to. |
It's a blog. We wouldn't remove the existing article - people will have bookmarked it with it's URL, and also it's just a bit weird to change an already-published article have a new date. Nothing wrong with duplicating (or near-duplicating) the article as I've suggested, though. |
It's a FUD machine at the moment. I don't care what happens to make it not a FUD machine. It just needs to happen fast; anything I can do to help? |
@chris-short this? |
On it. |
/assign Please see #31765 for my first attempt at this. |
/close Fixed in #31765 |
@sftim: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a Bug Report
Problem: https://k8s.io/dockershim is marked deprecated (since the merge of #31594)
Proposed Solutions:
Either:
Page to Update:
https://k8s.io/dockershim etc (see above)
Additional Information:
/priority important-soon
/sig node
/language en
Also see #30840
The text was updated successfully, but these errors were encountered: