Skip to content

Commit e2ea8ff

Browse files
jihoon-seoReung37seokho-sonpjhwacoolguyhong
committed
Ninth Korean l10n work for release 1.18
- Fix error in k8s.io/ko/docs/concepts/workloads/pods/pod-lifecycle/ (#22681) - Translate docs/reference/setup-tools/kubeadm/kubeadm.md in Korean (#22684) - Update outdated files in dev-1.18-ko.9 branch (#22686) - Fix issues of ko-doc links in translated docs (#22718) - Translate concepts/cluster-administration/monitoring.md into Korean (#22808) - Translate tasks/access-application-cluster/service-access-application-cluster in Korean (#22800) - Translate concepts/storage/storage-limits.md into Korean (#22795) Co-authored-by: Jihoon Seo <jihoon.seo@etri.re.kr> Co-authored-by: Reung37 <reung37@naver.com> Co-authored-by: Seokho Son <shsongist@gmail.com> Co-authored-by: Jerry Park <jaehwa@gmail.com> Co-authored-by: coolguyhong <podolsmith@naver.com>
1 parent cac85d2 commit e2ea8ff

File tree

75 files changed

+795
-337
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

75 files changed

+795
-337
lines changed

content/ko/_index.html

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,6 @@ <h2>150+ 마이크로서비스를 쿠버네티스로 마이그레이션하는
4141
<button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button>
4242
<br>
4343
<br>
44-
<br>
4544
<a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu20" button id="desktopKCButton">Attend KubeCon in Amsterdam on August 13-16, 2020</a>
4645
<br>
4746
<br>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
Kubernetes enabled the self-healing and immutable infrastructure. We can do faster releases, so our developers are really happy. They can ship our features faster than before, and that makes our clients happier.
1313
---
1414

15-
<div class="banner1 desktop" style="background-image: url('/images/CaseStudy_adform_banner1.jpg')">
15+
<div class="banner1 desktop" style="background-image: url('/images/case-studies/adform/banner1.jpg')">
1616
<h1> CASE STUDY:<img src="/images/adform_logo.png" style="width:15%;margin-bottom:0%" class="header_logo"><br> <div class="subhead">Improving Performance and Morale with Cloud Native
1717

1818
</div></h1>
@@ -66,7 +66,7 @@ <h2>Adform made <a href="https://www.wsj.com/articles/fake-ad-operation-used-to-
6666

6767
</div>
6868
</section>
69-
<div class="banner3" style="background-image: url('/images/CaseStudy_adform_banner3.jpg')">
69+
<div class="banner3" style="background-image: url('/images/case-studies/adform/banner3.jpg')">
7070
<div class="banner3text">
7171
"The fact that Cloud Native Computing Foundation incubated Kubernetes was a really big point for us because it was vendor neutral. And we can see that a community really gathers around it. Everyone shares their experiences, their knowledge, and the fact that it’s open source, you can contribute."<span style="font-size:14px;letter-spacing:0.12em;padding-top:20px;text-transform:uppercase;line-height:14px"><br><br>— Edgaras Apšega, IT Systems Engineer, Adform</span>
7272
</div>
@@ -83,7 +83,7 @@ <h2>Adform made <a href="https://www.wsj.com/articles/fake-ad-operation-used-to-
8383

8484
</div>
8585
</section>
86-
<div class="banner4" style="background-image: url('/images/CaseStudy_adform_banner4.jpg')">
86+
<div class="banner4" style="background-image: url('/images/case-studies/adform/banner4.jpg')">
8787
<div class="banner4text">
8888
"Releases are really nice for them, because they just push their code to Git and that’s it. They don’t have to worry about their virtual machines anymore." <span style="font-size:14px;letter-spacing:0.12em;padding-top:20px;text-transform:uppercase;line-height:14px"><br><br>— Andrius Cibulskis, IT Systems Engineer, Adform</span>
8989
</div>

content/ko/case-studies/capital-one/index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
css: /css/style_case_studies.css
66
---
77

8-
<div class="banner1 desktop" style="background-image: url('/images/CaseStudy_capitalone_banner1.jpg')">
8+
<div class="banner1 desktop" style="background-image: url('/images/case-studies/capitalone/banner1.jpg')">
99
<h1> CASE STUDY:<img src="/images/capitalone-logo.png" style="margin-bottom:-2%" class="header_logo"><br> <div class="subhead">Supporting Fast Decisioning Applications with Kubernetes
1010

1111
</div></h1>
@@ -55,7 +55,7 @@ <h2></h2>
5555

5656
</div>
5757
</section>
58-
<div class="banner3" style="background-image: url('/images/CaseStudy_capitalone_banner3.jpg')">
58+
<div class="banner3" style="background-image: url('/images/case-studies/capitalone/banner3.jpg')">
5959
<div class="banner3text">
6060
"We want to provide the tools in the same ecosystem, in a consistent way, rather than have a large custom snowflake ecosystem where every tool needs its own custom deployment. Kubernetes gives us the ability to bring all of these together, so the richness of the open source and even the license community dealing with big data can be corralled."
6161

@@ -69,7 +69,7 @@ <h2></h2>
6969

7070
</div>
7171
</section>
72-
<div class="banner4" style="background-image: url('/images/CaseStudy_capitalone_banner4.jpg')">
72+
<div class="banner4" style="background-image: url('/images/case-studies/capitalone/banner4.jpg')">
7373
<div class="banner4text">
7474
With Kubernetes, "a team can come to us and we can have them up and running with a basic decisioning app in a fortnight, which before would have taken a whole quarter, if not longer. Kubernetes is a manifold productivity multiplier."
7575
</div>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
featured: false
1010
---
1111

12-
<div class="banner1" style="background-image: url('/images/CaseStudy_ibm_banner1.jpg')">
12+
<div class="banner1" style="background-image: url('/images/case-studies/ibm/banner1.jpg')">
1313
<h1> CASE STUDY:<img src="/images/ibm_logo.png" class="header_logo" style="width:10%"><br> <div class="subhead">Building an Image Trust Service on Kubernetes with Notary and TUF</div></h1>
1414

1515
</div>
@@ -58,7 +58,7 @@ <h2>Docker had already created the Notary project as an implementation of <a hre
5858

5959
</div>
6060
</section>
61-
<div class="banner3" style="background-image: url('/images/CaseStudy_ibm_banner3.jpg')">
61+
<div class="banner3" style="background-image: url('/images/case-studies/ibm/banner3.jpg')">
6262
<div class="banner3text">
6363
"Image signing is one key part of our Kubernetes container service offering, and our container registry team saw Notary as the de facto way to implement that capability in the current Docker and container ecosystem"<span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br><br>- Michael Hough, a software developer with the IBM Cloud Container Registry team</span>
6464
</div>
@@ -75,7 +75,7 @@ <h2>Docker had already created the Notary project as an implementation of <a hre
7575

7676
</div>
7777
</section>
78-
<div class="banner4" style="background-image: url('/images/CaseStudy_ibm_banner4.jpg')">
78+
<div class="banner4" style="background-image: url('/images/case-studies/ibm/banner4.jpg')">
7979
<div class="banner4text">
8080
"With our IBM Cloud Kubernetes as-a-service offering and the admission controller we have made available, it allows both IBM services as well as customers of the IBM public cloud to use security policies to control service deployment."<span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br><br>- Michael Hough, a software developer with the IBM Cloud Container Registry team</span>
8181
</div>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
---
1212

1313

14-
<div class="banner1" style="background-image: url('/images/CaseStudy_ing_banner1.jpg')">
14+
<div class="banner1" style="background-image: url('/images/case-studies/ing/banner1.jpg')">
1515
<h1> CASE STUDY:<img src="/images/ing_logo.png" style="margin-bottom:-1.5%;" class="header_logo"><br> <div class="subhead"> Driving Banking Innovation with Cloud Native
1616
</div></h1>
1717

@@ -58,7 +58,7 @@ <h2>ING has long embraced innovation in banking, launching the internet-based IN
5858

5959
</div>
6060
</section>
61-
<div class="banner3" style="background-image: url('/images/CaseStudy_ing_banner3.jpg')">
61+
<div class="banner3" style="background-image: url('/images/case-studies/ing/banner3.jpg')">
6262
<div class="banner3text">
6363
"We decided to standardize ING on a Kubernetes framework." Everything is run on premise due to banking regulations, he adds, but "we will be building an internal public cloud. We are trying to get on par with what public clouds are doing. That’s one of the reasons we got Kubernetes."
6464
<span style="font-size:16px;text-transform:uppercase;letter-spacing:0.1em;"><br><br>— Thijs Ebbers, Infrastructure Architect, ING</span>
@@ -72,7 +72,7 @@ <h2>ING has long embraced innovation in banking, launching the internet-based IN
7272

7373
</div>
7474
</section>
75-
<div class="banner4" style="background-image: url('/images/CaseStudy_ing_banner4.jpg')">
75+
<div class="banner4" style="background-image: url('/images/case-studies/ing/banner4.jpg')">
7676
<div class="banner4text">
7777
"We have to run the complete platform of services we need, many routing from different places. We need this Kubernetes framework for deploying the containers, with all those components, monitoring, logging. It’s complex." <span style="font-size:16px;text-transform:uppercase;letter-spacing:0.1em;"><br><br>— Onno Van der Voort, Infrastructure Architect, ING</span>
7878
</div>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
featured: false
1010
---
1111

12-
<div class="banner1" style="background-image: url('/images/CaseStudy_naic_banner1.jpg')">
12+
<div class="banner1" style="background-image: url('/images/case-studies/naic/banner1.jpg')">
1313
<h1> CASE STUDY:<img src="/images/naic_logo.png" class="header_logo" style="width:18%"><br> <div class="subhead" style="margin-top:1%">A Culture and Technology Transition Enabled by Kubernetes</div></h1>
1414

1515
</div>
@@ -59,7 +59,7 @@ <h2>Impact</h2>
5959

6060
</div>
6161
</section>
62-
<div class="banner3" style="background-image: url('/images/CaseStudy_naic_banner3.jpg')">
62+
<div class="banner3" style="background-image: url('/images/case-studies/naic/banner3.jpg')">
6363
<div class="banner3text">
6464
"In our experience, vendor lock-in and tooling that is highly specific results in less resilient technology with fewer minds working to solve problems and grow the community." <br style="height:25px"><span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br>- Dan Barker, Chief Enterprise Architect, NAIC</span>
6565
</div>
@@ -77,7 +77,7 @@ <h2>Impact</h2>
7777

7878
</div>
7979
</section>
80-
<div class="banner4" style="background-image: url('/images/CaseStudy_naic_banner4.jpg')">
80+
<div class="banner4" style="background-image: url('/images/case-studies/naic/banner4.jpg')">
8181
<div class="banner4text">
8282
"We knew that Kubernetes had become the de facto standard for container orchestration. Two major factors for selecting this were the three major cloud vendors hosting their own versions and having it hosted in a neutral party as fully open source."<span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br><br>- Dan Barker, Chief Enterprise Architect, NAIC</span>
8383
</div>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
css: /css/style_case_studies.css
66
---
77

8-
<div class="banner1" style="background-image: url('/images/CaseStudy_nordstrom_banner1.jpg')">
8+
<div class="banner1" style="background-image: url('/images/case-studies/nordstrom/banner1.jpg')">
99
<h1> CASE STUDY:<img src="/images/nordstrom_logo.png" class="header_logo" style="margin-bottom:-1.5% !important;width:20% !important;"><br> <div class="subhead">Finding Millions in Potential Savings in a Tough Retail Climate
1010

1111

@@ -60,7 +60,7 @@ <h2>Impact</h2>
6060

6161
</div>
6262
</section>
63-
<div class="banner3" style="background-image: url('/images/CaseStudy_nordstrom_banner3.jpg')">
63+
<div class="banner3" style="background-image: url('/images/case-studies/nordstrom/banner3.jpg')">
6464
<div class="banner3text">
6565
"We made a bet that Kubernetes was going to take off, informed by early indicators of community support and project velocity, so we rebuilt our system with Kubernetes at the core,"
6666
</div>
@@ -77,7 +77,7 @@ <h2>Impact</h2>
7777

7878
</div>
7979
</section>
80-
<div class="banner4" style="background-image: url('/images/CaseStudy_nordstrom_banner4.jpg')">
80+
<div class="banner4" style="background-image: url('/images/case-studies/nordstrom/banner4.jpg')">
8181
<div class="banner4text">
8282
"Teams running on our Kubernetes cluster loved the fact that they had fewer issues to worry about. They didn’t need to manage infrastructure or operating systems," says Grigoriu. "Early adopters loved the declarative nature of Kubernetes. They loved the reduced surface area they had to deal with."
8383
</div>

content/ko/case-studies/northwestern-mutual/index.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
css: /css/style_case_studies.css
66
---
77

8-
<div class="banner1 desktop" style="background-image: url('/images/CaseStudy_northwestern_banner1.jpg')">
8+
<div class="banner1 desktop" style="background-image: url('/images/case-studies/northwestern/banner1.jpg')">
99
<h1> CASE STUDY:<img src="/images/northwestern_logo.png" style="margin-bottom:-1%" class="header_logo"><br> <div class="subhead">Cloud Native at Northwestern Mutual
1010

1111

@@ -22,7 +22,7 @@ <h1> CASE STUDY:<img src="/images/northwestern_logo.png" style="margin-bottom:-1
2222
<div class="cols">
2323
<div class="col1">
2424
<h2>Challenge</h2>
25-
In the spring of 2015, Northwestern Mutual acquired a fintech startup, LearnVest, and decided to take "Northwestern Mutual’s leading products and services and meld it with LearnVest’s digital experience and innovative financial planning platform," says Brad Williams, Director of Engineering for Client Experience, Northwestern Mutual. The company’s existing infrastructure had been optimized for batch workflows hosted on on-prem networks; deployments were very traditional, focused on following a process instead of providing deployment agility. "We had to build a platform that was elastically scalable, but also much more responsive, so we could quickly get data to the client website so our end-customers have the experience they expect," says Williams.
25+
In the spring of 2015, Northwestern Mutual acquired a fintech startup, LearnVest, and decided to take "Northwestern Mutual’s leading products and services and meld it with LearnVest’s digital experience and innovative financial planning platform," says Brad Williams, Director of Engineering for Client Experience, Northwestern Mutual. The company’s existing infrastructure had been optimized for batch workflows hosted on on-prem networks; deployments were very traditional, focused on following a process instead of providing deployment agility. "We had to build a platform that was elastically scalable, but also much more responsive, so we could quickly get data to the client website so our end-customers have the experience they expect," says Williams.
2626
<br>
2727
<h2>Solution</h2>
2828
The platform team came up with a plan for using the public cloud (AWS), Docker containers, and Kubernetes for orchestration. "Kubernetes gave us that base framework so teams can be very autonomous in what they’re building and deliver very quickly and frequently," says Northwestern Mutual Cloud Native Engineer Frank Greco Jr. The team also built and open-sourced <a href="https://github.com/northwesternmutual/kanali">Kanali</a>, a Kubernetes-native API management tool that uses OpenTracing, Jaeger, and gRPC.
@@ -53,7 +53,7 @@ <h2>For more than 160 years, Northwestern Mutual has maintained its industry lea
5353

5454
</div>
5555
</section>
56-
<div class="banner3" style="background-image: url('/images/CaseStudy_northwestern_banner3.jpg')">
56+
<div class="banner3" style="background-image: url('/images/case-studies/northwestern/banner3.jpg')">
5757
<div class="banner3text">
5858
"Kubernetes has definitely been the right choice for us. It gave us that base framework so teams can be autonomous in what they’re building and deliver very quickly and frequently."
5959

@@ -63,12 +63,12 @@ <h2>For more than 160 years, Northwestern Mutual has maintained its industry lea
6363
<div class="fullcol">
6464
Williams and the rest of the platform team decided that the first step would be to start moving from private data centers to AWS. With a new microservice architecture in mind—and the freedom to implement what was best for the organization—they began using Docker containers. After looking into the various container orchestration options, they went with Kubernetes, even though it was still in beta at the time. "There was some debate whether we should build something ourselves, or just leverage that product and evolve with it," says Northwestern Mutual Cloud Native Engineer Frank Greco Jr. "Kubernetes has definitely been the right choice for us. It gave us that base framework so teams can be autonomous in what they’re building and deliver very quickly and frequently."<br><br>
6565
As early adopters, the team had to do a lot of work with Ansible scripts to stand up the cluster. "We had a lot of hard security requirements given the nature of our business," explains Bryan Pfremmer, App Platform Teams Manager, Northwestern Mutual. "We found ourselves running a configuration that very few other people ever tried." The client experience group was the first to use the new platform; today, a few hundred of the company’s 1,500 engineers are using it and more are eager to get on board.
66-
The results have been dramatic. Before, infrastructure deployments could take two weeks; now, it is done in a matter of minutes. Now with a focus on Infrastructure automation, and self-service, "You can take an app to production in that same day if you want to," says Pfremmer.
66+
The results have been dramatic. Before, infrastructure deployments could take two weeks; now, it is done in a matter of minutes. Now with a focus on Infrastructure automation, and self-service, "You can take an app to production in that same day if you want to," says Pfremmer.
6767

6868

6969
</div>
7070
</section>
71-
<div class="banner4" style="background-image: url('/images/CaseStudy_northwestern_banner4.jpg')">
71+
<div class="banner4" style="background-image: url('/images/case-studies/northwestern/banner4.jpg')">
7272
<div class="banner4text">
7373
"Now, developers have autonomy, they can use this whenever they want, however they want. It becomes more valuable the more instrumentation downstream that happens, as we mature in it."
7474
</div>

0 commit comments

Comments
 (0)