diff --git a/content/ko/_common-resources/index.md b/content/ko/_common-resources/index.md new file mode 100644 index 000000000..3d65eaa0f --- /dev/null +++ b/content/ko/_common-resources/index.md @@ -0,0 +1,3 @@ +--- +headless: true +--- \ No newline at end of file diff --git a/content/ko/_index.html b/content/ko/_index.html index 5d3b933f1..49d18a9b4 100644 --- a/content/ko/_index.html +++ b/content/ko/_index.html @@ -6,179 +6,57 @@ {{< deprecationwarning >}} - -
-
-
-
-

쿠버네티스는 컨테이너화된 애플리케이션을 자동으로 배포, 스케일링 및 관리해주는 오픈소스 시스템입니다.

-

It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds - upon 15 years of experience of running production workloads at Google, - combined with best-of-breed ideas and practices from the community.

-
-
-
-
-
-

행성 규모 확장성

-

Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team.

-
-
-
-
-
-

무한한 유연성

-

Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is.

-
-
-
-
-
-

어디서나 동작

-

Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.

-
-
-
- -
-
-

150+ 마이크로서비스를 쿠버네티스로 마이그레이션하는 도전

+{{< blocks/section id="oceanNodes" >}} +{{% blocks/feature image="flower" %}} +### [쿠버네티스]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}})는 컨테이너화된 애플리케이션을 자동으로 배포, 스케일링 및 관리해주는 오픈소스 시스템입니다. + +It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon [15 years of experience of running production workloads at Google](http://queue.acm.org/detail.cfm?id=2898444), combined with best-of-breed ideas and practices from the community. +{{% /blocks/feature %}} + +{{% blocks/feature image="scalable" %}} +#### 행성 규모 확장성 + +Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team. + +{{% /blocks/feature %}} + +{{% blocks/feature image="blocks" %}} +#### 무한한 유연성 + +Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is. + +{{% /blocks/feature %}} + +{{% blocks/feature image="suitcase" %}} +#### 어디서나 동작 + +Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you. + +{{% /blocks/feature %}} + +{{< /blocks/section >}} + +{{< blocks/section id="video" background-image="kub_video_banner_homepage" >}} +
+

150+ 마이크로서비스를 쿠버네티스로 마이그레이션하는 도전

By Sarah Wells, Technical Director for Operations and Reliability, Financial Times




- Attend KubeCon in Shanghai on Nov. 14-15, 2018 + Attend KubeCon in Shanghai on Nov. 13-15, 2018



- Attend KubeCon in Seattle on Dec. 11-13, 2018 -
- -
- -
-
-

쿠버네티스 특징

- -
-
-

스케줄링

-

Automatically places containers based on their resource requirements and other constraints, while not - sacrificing availability. Mix critical and best-effort workloads in order to drive up utilization and save even more resources.

-
-
-

자동 복구

-

Restarts containers that fail, replaces and reschedules containers when nodes die, kills containers - that don't respond to your user-defined health check, and doesn't advertise them to clients until they are ready to serve.

-
-
- -
-
-

수평적 확장

-

Scale your application up and down with a simple command, with a UI, or automatically based on CPU usage.

-
-
-

서비스 디스커버리 및 로드 밸런싱

-

No need to modify your application to use an unfamiliar service discovery mechanism. Kubernetes gives - containers their own IP addresses and a single DNS name for a set of containers, and can load-balance across them.

-
-
- -
-
-

배포 및 롤백 자동화

-

Kubernetes progressively rolls out changes to your application or its configuration, while monitoring - application health to ensure it doesn't kill all your instances at the same time. If something goes - wrong, Kubernetes will rollback the change for you. Take advantage of a growing ecosystem of deployment solutions.

-
-
-

시크릿 및 설정 관리

-

Deploy and update secrets and application configuration without rebuilding your image and without - exposing secrets in your stack configuration.

-
-
- -
-
-

스토리지 오케스트레이션

-

Automatically mount the storage system of your choice, whether from local storage, a public cloud provider - such as GCP or AWS, or a network storage system such as NFS, iSCSI, - Gluster, Ceph, Cinder, or Flocker.

-
-
-

배치 실행

-

In addition to services, Kubernetes can manage your batch and CI workloads, replacing containers that fail, if desired.

-
-
- -
-
- -
-
-

사례 연구

-
-
-

Pinning Its Past, Present, and Future on Cloud Native

- Read more -
-
-

Reinventing the World’s Largest Education Company With Kubernetes

- Read more -
- -
-

Supporting Fast Decisioning Applications with Kubernetes

- Read more -
-
-

Driving Banking Innovation with Cloud Native

- Read more -
- -
- - - - - - - - - - - - - - - - - - - - - - - -
사례 연구 전체 보기
-
-
-
-
-
-

We are a CNCF graduated project

-
-
-
- - - - - + Attend KubeCon in Seattle on Dec. 11-13, 2018 +
+{{< /blocks/section >}} + +{{< blocks/kubernetes-features >}} + +{{< blocks/case-studies >}} diff --git a/content/ko/case-studies/_index.html b/content/ko/case-studies/_index.html new file mode 100644 index 000000000..28bdab44a --- /dev/null +++ b/content/ko/case-studies/_index.html @@ -0,0 +1,10 @@ +--- +title: Case Studies +linkTitle: Case Studies +bigheader: Kubernetes User Case Studies +abstract: A collection of users running Kubernetes in production. +layout: basic +class: gridPage +cid: caseStudies +--- + diff --git a/content/ko/docs/concepts/overview/what-is-kubernetes.md b/content/ko/docs/concepts/overview/what-is-kubernetes.md new file mode 100644 index 000000000..f086ab21f --- /dev/null +++ b/content/ko/docs/concepts/overview/what-is-kubernetes.md @@ -0,0 +1,207 @@ +--- +reviewers: +- bgrant0607 +- mikedanese +title: What is Kubernetes? +content_template: templates/concept +weight: 10 +--- + +{{% capture overview %}} +This page is an overview of Kubernetes. +{{% /capture %}} + +{{% capture body %}} +Kubernetes is a portable, extensible open-source platform for managing +containerized workloads and services, that facilitates both +declarative configuration and automation. It has a large, rapidly +growing ecosystem. Kubernetes services, support, and tools are widely available. + +Google open-sourced the Kubernetes project in 2014. Kubernetes builds upon +a [decade and a half of experience that Google has with running +production workloads at +scale](https://research.google.com/pubs/pub43438.html), combined with +best-of-breed ideas and practices from the community. + +## Why do I need Kubernetes and what can it do? + +Kubernetes has a number of features. It can be thought of as: + +- a container platform +- a microservices platform +- a portable cloud platform +and a lot more. + +Kubernetes provides a **container-centric** management environment. It +orchestrates computing, networking, and storage infrastructure on +behalf of user workloads. This provides much of the simplicity of +Platform as a Service (PaaS) with the flexibility of Infrastructure as +a Service (IaaS), and enables portability across infrastructure +providers. + +## How is Kubernetes a platform? + +Even though Kubernetes provides a lot of functionality, there are +always new scenarios that would benefit from new +features. Application-specific workflows can be streamlined to +accelerate developer velocity. Ad hoc orchestration that is acceptable +initially often requires robust automation at scale. This is why +Kubernetes was also designed to serve as a platform for building an +ecosystem of components and tools to make it easier to deploy, scale, +and manage applications. + +[Labels](/docs/concepts/overview/working-with-objects/labels/) empower +users to organize their resources however they +please. [Annotations](/docs/concepts/overview/working-with-objects/annotations/) +enable users to decorate resources with custom information to +facilitate their workflows and provide an easy way for management +tools to checkpoint state. + +Additionally, the [Kubernetes control +plane](/docs/concepts/overview/components/) is built upon the same +[APIs](/docs/reference/using-api/api-overview/) that are available to developers +and users. Users can write their own controllers, such as +[schedulers](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/devel/scheduler.md), +with [their own +APIs](/docs/concepts/api-extension/custom-resources/) +that can be targeted by a general-purpose [command-line +tool](/docs/user-guide/kubectl-overview/). + +This +[design](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) +has enabled a number of other systems to build atop Kubernetes. + +## What Kubernetes is not + +Kubernetes is not a traditional, all-inclusive PaaS (Platform as a +Service) system. Since Kubernetes operates at the container level +rather than at the hardware level, it provides some generally +applicable features common to PaaS offerings, such as deployment, +scaling, load balancing, logging, and monitoring. However, Kubernetes +is not monolithic, and these default solutions are optional and +pluggable. Kubernetes provides the building blocks for building developer +platforms, but preserves user choice and flexibility where it is +important. + +Kubernetes: + +* Does not limit the types of applications supported. Kubernetes aims + to support an extremely diverse variety of workloads, including + stateless, stateful, and data-processing workloads. If an + application can run in a container, it should run great on + Kubernetes. +* Does not deploy source code and does not build your + application. Continuous Integration, Delivery, and Deployment + (CI/CD) workflows are determined by organization cultures and preferences + as well as technical requirements. +* Does not provide application-level services, such as middleware + (e.g., message buses), data-processing frameworks (for example, + Spark), databases (e.g., mysql), caches, nor cluster storage systems (e.g., + Ceph) as built-in services. Such components can run on Kubernetes, and/or + can be accessed by applications running on Kubernetes through portable + mechanisms, such as the Open Service Broker. +* Does not dictate logging, monitoring, or alerting solutions. It provides + some integrations as proof of concept, and mechanisms to collect and + export metrics. +* Does not provide nor mandate a configuration language/system (e.g., + [jsonnet](https://github.com/google/jsonnet)). It provides a declarative + API that may be targeted by arbitrary forms of declarative specifications. +* Does not provide nor adopt any comprehensive machine configuration, + maintenance, management, or self-healing systems. + +Additionally, Kubernetes is not a mere *orchestration system*. In +fact, it eliminates the need for orchestration. The technical +definition of *orchestration* is execution of a defined workflow: +first do A, then B, then C. In contrast, Kubernetes is comprised of a +set of independent, composable control processes that continuously +drive the current state towards the provided desired state. It +shouldn't matter how you get from A to C. Centralized control is also +not required. This results in a system that is easier to use and more +powerful, robust, resilient, and extensible. + +## Why containers? + +Looking for reasons why you should be using containers? + +![Why Containers?](/images/docs/why_containers.svg) + +The *Old Way* to deploy applications was to install the applications +on a host using the operating-system package manager. This had the +disadvantage of entangling the applications' executables, +configuration, libraries, and lifecycles with each other and with the +host OS. One could build immutable virtual-machine images in order to +achieve predictable rollouts and rollbacks, but VMs are heavyweight +and non-portable. + +The *New Way* is to deploy containers based on operating-system-level +virtualization rather than hardware virtualization. These containers +are isolated from each other and from the host: they have their own +filesystems, they can't see each others' processes, and their +computational resource usage can be bounded. They are easier to build +than VMs, and because they are decoupled from the underlying +infrastructure and from the host filesystem, they are portable across +clouds and OS distributions. + +Because containers are small and fast, one application can be packed +in each container image. This one-to-one application-to-image +relationship unlocks the full benefits of containers. With containers, +immutable container images can be created at build/release time rather +than deployment time, since each application doesn't need to be +composed with the rest of the application stack, nor married to the +production infrastructure environment. Generating container images at +build/release time enables a consistent environment to be carried from +development into production. Similarly, containers are vastly more +transparent than VMs, which facilitates monitoring and +management. This is especially true when the containers' process +lifecycles are managed by the infrastructure rather than hidden by a +process supervisor inside the container. Finally, with a single +application per container, managing the containers becomes tantamount +to managing deployment of the application. + +Summary of container benefits: + +* **Agile application creation and deployment**: + Increased ease and efficiency of container image creation compared to VM image use. +* **Continuous development, integration, and deployment**: + Provides for reliable and frequent container image build and + deployment with quick and easy rollbacks (due to image + immutability). +* **Dev and Ops separation of concerns**: + Create application container images at build/release time rather + than deployment time, thereby decoupling applications from + infrastructure. +* **Observability** + Not only surfaces OS-level information and metrics, but also application + health and other signals. +* **Environmental consistency across development, testing, and production**: + Runs the same on a laptop as it does in the cloud. +* **Cloud and OS distribution portability**: + Runs on Ubuntu, RHEL, CoreOS, on-prem, Google Kubernetes Engine, and anywhere else. +* **Application-centric management**: + Raises the level of abstraction from running an OS on virtual + hardware to running an application on an OS using logical resources. +* **Loosely coupled, distributed, elastic, liberated [micro-services](https://martinfowler.com/articles/microservices.html)**: + Applications are broken into smaller, independent pieces and can + be deployed and managed dynamically -- not a fat monolithic stack + running on one big single-purpose machine. +* **Resource isolation**: + Predictable application performance. +* **Resource utilization**: + High efficiency and density. + +## What does Kubernetes mean? K8s? + +The name **Kubernetes** originates from Greek, meaning *helmsman* or +*pilot*, and is the root of *governor* and +[cybernetic](http://www.etymonline.com/index.php?term=cybernetics). *K8s* +is an abbreviation derived by replacing the 8 letters "ubernete" with +"8". + +{{% /capture %}} + +{{% capture whatsnext %}} +* Ready to [Get Started](/docs/setup/)? +* For more details, see the [Kubernetes Documentation](/docs/home/). +{{% /capture %}} + +