Fix relative links issue in ko content (#13308)
* `http://kubernetes.io/docs/` -> `/docs/` * `https://kubernetes.io/docs/` -> `/docs/`pull/13330/head
chenrui
Kubernetes Prow Robot
parent
4737c170ec
commit
ac60d8a0bb
|
|
@ -69,7 +69,7 @@ css: /css/style_blackrock.css
|
|||
Made up of managers from technology, infrastructure, production operations, development and information security, Francis’s team was able to look at the problem holistically and come up with a solution that made sense for BlackRock. "Our initial straw man was that we were going to build everything using <a href="https://www.ansible.com">Ansible</a> and run it all using some completely different distributed environment," says Francis. "That would have been absolutely the wrong thing to do. Had we gone off on our own as the dev team and developed this solution, it would have been a very different product. And it would have been very expensive. We would not have gone down the route of running under our existing orchestration system. Because we don’t understand it. These guys [in operations and infrastructure] understand it. Having the multidisciplinary team allowed us to get to the right solutions and that actually meant we didn’t build anywhere near the amount we thought we were going to end up building."<br><br>
|
||||
In search of a solution in which they could manage usage on a user-by-user level, Francis’s team gravitated to Red Hat’s <a href="https://www.openshift.com">OpenShift</a> Kubernetes offering. The company had already experimented with other cloud-native environments, but the team liked that Kubernetes was open source, and "we felt the winds were blowing in the direction of Kubernetes long term," says Francis. "Typically we make technology choices that we believe are going to be here in 5-10 years’ time, in some form. And right now, in this space, Kubernetes feels like the one that’s going to be there." Adds Uri Morris, Vice President of Production Operations: "When you see that the non-Google committers to Kubernetes overtook the Google committers, that’s an indicator of the momentum."<br><br>
|
||||
Once that decision was made, the major challenge was figuring out how to make Kubernetes work within BlackRock’s existing framework. "It’s about understanding how we can operate, manage and support a platform like this, in addition to tacking it onto our existing technology platform," says Project Manager Michael Maskallis. "All the controls we have in place, the change management process, the software development lifecycle, onboarding processes we go through—how can we do all these things?"<br><br>
|
||||
The first (anticipated) speed bump was working around issues behind BlackRock’s corporate firewalls. "One of our challenges is there are no firewalls in most open source software," says Francis. "So almost all install scripts fail in some bizarre way, and pulling down packages doesn’t necessarily work." The team ran into these types of problems using <a href="https://kubernetes.io/docs/getting-started-guides/minikube/">Minikube</a> and did a few small pushes back to the open source project.
|
||||
The first (anticipated) speed bump was working around issues behind BlackRock’s corporate firewalls. "One of our challenges is there are no firewalls in most open source software," says Francis. "So almost all install scripts fail in some bizarre way, and pulling down packages doesn’t necessarily work." The team ran into these types of problems using <a href="/docs/getting-started-guides/minikube/">Minikube</a> and did a few small pushes back to the open source project.
|
||||
|
||||
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ weight: 80
|
|||
|
||||
쿠버네티스 클러스터의 페더레이션은 다른 클라우드 제공자(예를 들어, Google 클라우드, AWS),
|
||||
그리고 온-프레미스(예를 들어, OpenStack)에서 동작 중인 클러스터를 포함할 수
|
||||
있다. [Kubefed](https://kubernetes.io/docs/tasks/federation/set-up-cluster-federation-kubefed/)는 연합된 클러스터 배치에 권장되는 방법이다.
|
||||
있다. [Kubefed](/docs/tasks/federation/set-up-cluster-federation-kubefed/)는 연합된 클러스터 배치에 권장되는 방법이다.
|
||||
|
||||
그 후에, [API 리소스](#api-리소스)는 서로 다른 클러스터와 클라우드
|
||||
제공자에 걸쳐 확장될 수 있다.
|
||||
|
|
@ -182,6 +182,3 @@ zone)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availabi
|
|||
* [Kubecon2018 유럽 Federation-v2 프로토타입 발표](https://youtu.be/q27rbaX5Jis?t=7m20s) 보기
|
||||
* [Federation-v2 사용자 가이드](https://github.com/kubernetes-sigs/federation-v2/blob/master/docs/userguide.md) 보기
|
||||
{{% /capture %}}
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ spec:
|
|||
{{< note >}}
|
||||
런타임 클래스 쓰기 작업(create/update/patch/delete)은
|
||||
클러스터 관리자로 제한할 것을 권장한다. 이것은 일반적으로 기본 설정이다. 더 자세한 정보는 [권한
|
||||
개요](https://kubernetes.io/docs/reference/access-authn-authz/authorization/)를 참고한다.
|
||||
개요](/docs/reference/access-authn-authz/authorization/)를 참고한다.
|
||||
{{< /note >}}
|
||||
|
||||
### 사용
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ Horizontal Pod Autoscaler는 컨트롤러
|
|||
HorizontalPodAutoscaler는 보통 일련의 API 집합(`metrics.k8s.io`,
|
||||
`custom.metrics.k8s.io`, `external.metrics.k8s.io`)에서 메트릭을 가져온다. `metrics.k8s.io` API는 대개 별도로
|
||||
시작해야 하는 메트릭-서버에 의해 제공된다. 가이드는
|
||||
[메트릭-서버](https://kubernetes.io/docs/tasks/debug-application-cluster/core-metrics-pipeline/#metrics-server)를
|
||||
[메트릭-서버](/docs/tasks/debug-application-cluster/core-metrics-pipeline/#metrics-server)를
|
||||
참조한다. HorizontalPodAutoscaler는 힙스터(Heapster)에서 직접 메트릭을 가져올 수도 있다.
|
||||
|
||||
{{< note >}}
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@ weight: 10
|
|||
<h3>애플리케이션을 스케일하기</h3>
|
||||
|
||||
<p>지난 모듈에서 <a
|
||||
href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/"> 디플로이먼트</a>,
|
||||
를 만들고 <a href="https://kubernetes.io/docs/concepts/services-networking/service/">서비스</a>를
|
||||
href="/docs/concepts/workloads/controllers/deployment/"> 디플로이먼트</a>,
|
||||
를 만들고 <a href="/docs/concepts/services-networking/service/">서비스</a>를
|
||||
통해서 디플로이먼트를 외부에 노출시켜 봤다. 해당 디플로이먼트는 애플리케이션을 구동하기 위해 단
|
||||
하나의 파드(Pod)만을 생성했었다. 트래픽이 증가하면, 사용자 요청에 맞추어 애플리케이션의 규모를
|
||||
조정할 필요가 있다.</p>
|
||||
|
|
@ -94,7 +94,7 @@ weight: 10
|
|||
|
||||
<p>디플로이먼트를 스케일 아웃하면 신규 파드가 생성되어서 가용한 자원이 있는 노드에 스케줄된다.
|
||||
스케일링 기능은 새로 의도한 상태(desired state)까지 파드의 수를 늘린다. 쿠버네티스는
|
||||
파드의 <a href="http://kubernetes.io/docs/user-guide/horizontal-pod-autoscaling/">오토스케일링</a>
|
||||
파드의 <a href="/docs/user-guide/horizontal-pod-autoscaling/">오토스케일링</a>
|
||||
도 지원하지만 본 튜토리얼에서는 다루지 않는다. 0까지 스케일링하는 것도 가능하다. 이 경우 해당
|
||||
디플로이먼트의 모든 파드가 종료된다.</p>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue