-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
fix-up the broken link #17601
fix-up the broken link #17601
Conversation
/assign @daminisatya |
Deploy preview for kubernetes-io-master-staging ready! Built with commit 1028594 https://deploy-preview-17601--kubernetes-io-master-staging.netlify.com |
@@ -2,7 +2,7 @@ | |||
title: Helm Chart | |||
id: helm-chart | |||
date: 2018-04-12 | |||
full_link: https://helm.sh/docs/developing_charts/ | |||
full_link: https://helm.sh/docs/ |
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.
Isn't it suppose to be https://helm.sh/docs/howto/charts_tips_and_tricks/ or even https://helm.sh/docs/topics/charts/ ?
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.
@butuzov OK. I will update https://helm.sh/docs/topics/charts/
@@ -101,7 +101,7 @@ <h2>In less than a decade, <a href="https://ygrene.com/index.html" style="text-d | |||
|
|||
<div class="fullcol"> | |||
Before, deployments typically took three to four hours, and two or three months’ worth of work would be deployed at low-traffic times every week or two weeks. Now, they take five minutes for Kubernetes, and an hour for an overall deploy with smoke testing. And "we’re able to deploy three or four times a week, with just one week’s or two days’ worth of work," Adams says. "We’re deploying during the work week, in the daytime and without any downtime. We had to ask for business approval to take the systems down for 30 minutes to an hour, even in the middle of the night, because people could be doing loans. Now we can deploy, ship code, and migrate databases, all without taking the system down. The company gets new features without worrying that some business will be lost or delayed."<br><br> | |||
Cloud native also affected how Ygrene’s 50+ developers and contractors work. Adams and Arnold spent considerable time "teaching people to think distributed out of the box," says Arnold. "We ended up picking what we call the Four S’s of Shipping: safely, securely, stably, and speedily." (For more on the security piece of it, see their <a href="https://thenewstack.io/beyond-ci-cd-how-continuous-hacking-of-docker-containers-and-pipeline-driven-security-keeps-ygrene-secure/index.html">article</a> on their "continuous hacking" strategy.) As for the engineers, says Adams, "they have been able to advance as their software has advanced. I think that at the end of the day, the developers feel better about what they’re doing, and they also feel more connected to the modern software development community."<br><br> |
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.
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.
@butuzov Thanks!
@butuzov done. |
/lgtm But I am not code owner (just a contributor as you), let's wait for Monday so PR can be reviewed by someone from sig-docs |
@butuzov: changing LGTM is restricted to collaborators 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. |
Yeap, @k8s-ci-bot, that what I have said! I love robo-talking. |
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.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
ref:#17649 |
There urls are not valid.They will return 404 when clicking them.
https://istio.io/docs/concepts/what-is-istio/overview.html ==> https://istio.io/docs/concepts/what-is-istio/
https://jobs.lever.co/openai/f163bf64-278e-417b-ad2e-5e508a29eb71 ==> https://jobs.lever.co/openai
https://github.com/containernetworking/cnihttps://github.com/containernetworking/cni ==> https://github.com/containernetworking/cni
https://thenewstack.io/beyond-ci-cd-how-continuous-hacking-of-docker-containers-and-pipeline-driven-security-keeps-ygrene-secure/index.html ==> https://thenewstack.io/beyond-ci-cd-how-continuous-hacking-of-docker-containers-and-pipeline-driven-security-keeps-ygrene-secure/
https://github.com/kubernetes/test-infra/blob/master/prow/plugins.yaml#L210 ==> https://github.com/kubernetes/test-infra/tree/master/prow/plugins
https://helm.sh/docs/developing_charts/ ==> https://helm.sh/docs/topics/charts/
https://istio.io/docs/concepts/what-is-istio/overview.html ==> https://istio.io/docs/concepts/what-is-istio/