-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
[en] Clean up various broken links #32913
Conversation
01b2a80
to
699c711
Compare
✅ Deploy Preview for kubernetes-io-main-staging ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for kubernetes-io-main-staging ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/remove-language de |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SIG Docs policy is not to revise blog posts more than 1 year old. We add a banner advising readers to check pages haven't gone out of date.
http://romana.io/ is not malware, it's just a broken link.
I want to record that accepting this change does not set a precedent for other PRs that propose to revise old articles.
How do these suggestions look?
content/en/blog/_posts/2016-04-00-Kubernetes-Network-Policy-APIs.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2016-09-00-High-Performance-Network-Policies-Kubernetes.md
Outdated
Show resolved
Hide resolved
The security risk is that someone could purchase that domain, make a look-alike page to the real romana destination, and provide malware downloads. I agree it's low priority, but that's why we're treating this as a security vulnerability. Note that this only applies to nxdomains (or unregistered domains), not to broken paths that 404. |
Usual SIG Docs blog policy is not to revise blog posts more than 1 year old; we can make an exception of course. How do you feel about removing the links to Romana as I've suggested @tallclair ? |
Yeah, I'm fine with removing the links. |
@@ -73,8 +73,5 @@ When using Romana v2.0, native VPC networking is now available for clusters of a | |||
![](https://archive.org/download/hpc-ec2-vpc-2/hpc-ec2-vpc-2.png) | |||
|
|||
|
|||
The preview release of Romana v2.0 is available [here](http://romana.io/preview). We welcome comments and feedback so we can make EC2 deployments of Kubernetes as fast and reliable as possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer not to remove this whole paragraph. Could we do something like this instead:
The preview release of Romana v2.0 is available [here](http://romana.io/preview). We welcome comments and feedback so we can make EC2 deployments of Kubernetes as fast and reliable as possible. | |
The preview release of Romana v2.0 is available here _Editor's Note:_ link removed. We welcome comments and feedback so we can make EC2 deployments of Kubernetes as fast and reliable as possible. |
@sftim do we have any history of providing Editor's Notes? is this the format they'd be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nate-double-u We've used editor's notes at the top of other blog posts. I'd prefer a different format, but I'd rather expedite the security concern so we can discuss formatting in a non-blocking way.
@tallclair Thanks for your patience. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zacharysarah 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:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: 5f8e05cb0c09d3b85499b02842ccfd48c0d6f467
|
Clean up broken links reported through the HackerOne bug bounty program.
Localized version of #32783
/committee security-response