First Korean I10n work for release-1.14 (#13730)

* First Korean I10n work for release-1.14

- ko: Fix nav-menu sync in tutorials/statefulset #13374 (#13474)
- ko: add outdated files in dev-1.14-ko.1 branch (#13473)
- Translate title of concepts/../image.md Ko (#13507)
- ko: add translation tutorial/stateful-application/cassandra #12450 (#13515)
- Translate reference/kubectl/cheatsheet in Korean (#13549)
- Translate tasks/access-application-cluster/access-cluster in Korean (#13565)
- ko: add tutorials/stateful-application/mysql-wordpress-persistent-vol… (#13516)
- Issue 12838 object management kubectl imperative config (#13657)
- Translate standardized glossary Tag Fandamental in Korean (#13552)

Co-authored-by:    Kim Young Dae <38598117+zer0big@users.noreply.github.com>

Co-authored-by:    Yoon <learder@gmail.com>

Co-authored-by:    lapee79 <lapee79@gmail.com>

Co-authored-by:    Jesang Myung <jesang.myung@gmail.com>

Co-authored-by:    Seokho <shsongist@gmail.com>

Co-authored-by:    Claudia J.Kang <claudiajkang@gmail.com>

Co-authored-by:    June Yi <june.yi@samsung.com>

* Fix conflict : pick-right-solution

content/ko/case-studies/pinterest/index.html

@@ -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>