whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Final Korean I10n work for release-1.13 (#13593)

Browse Source 
* ko: Fix nav-menu sync in tutorials/statefulset #13374 (#13469)

* ko: add outdated files in dev-1.13-ko.9 branch (#13464)

Co-authored-by: Yoon <learder@gmail.com>
Co-authored-by:	Claudia J. Kang <claudiajkang@gmail.com>
This commit is contained in:
Claudia J.Kang
2019-04-04 00:05:48 +09:00
committed by Kubernetes Prow Robot
parent 8d6823ba24
commit 240c0e7886
22 changed files with 243 additions and 1012 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/ko/case-studies/pinterest/index.html
+7 -8
View File
@@ -26,28 +26,27 @@ quote: >
<section class="section1">
<div class="cols">
<div class="col1">
<br><br>
<h2>Challenge</h2>
After eight years in existence, Pinterest had grown into 1,000 microservices and multiple layers of infrastructure and diverse set-up tools and platforms. In 2016 the company launched a roadmap towards a new compute platform, led by the vision of creating the fastest path from an idea to production, without making engineers worry about the underlying infrastructure.
<br>
<br><br>
<h2>Solution</h2>
The first phase involved moving services to Docker containers. Once these services went into production in early 2017, the team began looking at orchestration to help create efficiencies and manage them in a decentralized way. After an evaluation of various solutions, Pinterest went with Kubernetes.
</div>
<div class="col2">
<br><br>
<h2>Impact</h2>
"By moving to Kubernetes the team was able to build on-demand scaling and new failover policies, in addition to simplifying the overall deployment and management of a complicated piece of infrastructure such as Jenkins," says Micheal Benedict, Product Manager for the Cloud and the Data Infrastructure Group at Pinterest. "We not only saw reduced build times but also huge efficiency wins. For instance, the team reclaimed over 80 percent of capacity during non-peak hours. As a result, the Jenkins Kubernetes cluster now uses 30 percent less instance-hours per-day when compared to the previous static cluster."
</div>
</div>
</div>
</section>
<div class="banner2">
<div class="banner2text">
<div class="banner2" style="text-align:center">
<iframe width="500" height="260" src="https://www.youtube.com/embed/I36NNJH1xQY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<div class="banner2text"><br><br>
"So far it’s been good, especially the elasticity around how we can configure our Jenkins workloads on that Kubernetes shared cluster. That is the win we&nbsp;were&nbsp;pushing&nbsp;for." <span style="font-size:14px;letter-spacing:0.12em;padding-top:20px;text-transform:uppercase;line-height:14px"><br><br>— Micheal Benedict, Product Manager for the Cloud and the Data Infrastructure Group at Pinterest</span>
</div>