From e457f2a7fc24c1dc499960fa1e0493fdc4d8ff36 Mon Sep 17 00:00:00 2001 From: Oleg Butuzov Date: Tue, 1 Oct 2019 12:07:37 +0300 Subject: [PATCH] Broken links This fix resolve - broken links in documentation (Indonesian and Korean) - misplaced markdown braces (that was generated web errors) - fix a few links in blog (english) --- ...07-16-kubernetes-1-11-release-interview.md | 2 +- ...ernetes-edge-control-plane-for-envoy-v2.md | 2 +- ...tore-For-Kubernetes-Contributor-Summits.md | 24 +++++++++---------- .../docs/concepts/overview/kubernetes-api.md | 6 ++--- .../reference/glossary/platform-developer.md | 2 +- .../workloads/controllers/replicaset.md | 4 ++-- 6 files changed, 20 insertions(+), 20 deletions(-) diff --git a/content/en/blog/_posts/2018-07-16-kubernetes-1-11-release-interview.md b/content/en/blog/_posts/2018-07-16-kubernetes-1-11-release-interview.md index da146e6b6c99f..4326924029e3f 100644 --- a/content/en/blog/_posts/2018-07-16-kubernetes-1-11-release-interview.md +++ b/content/en/blog/_posts/2018-07-16-kubernetes-1-11-release-interview.md @@ -267,7 +267,7 @@ TIM PEPPER: Also, I would maybe argue in a way that a portion of that wasn't jus Thanks to Josh Berkus and Tim Pepper for talking to the Kubernetes Podcast from Google. -[Josh Berkus](https://github.com/jberkus) hangs out in #sig-release on the [Kubernetes Slack](slack.k8s.io). He maintains a newsletter called "[Last Week in Kubernetes Development](http://lwkd.info/)", with Noah Kantrowitz. You can read him on Twitter at [@fuzzychef](https://twitter.com/fuzzychef), but he does warn you that there's a lot of politics there as well. +[Josh Berkus](https://github.com/jberkus) hangs out in #sig-release on the [Kubernetes Slack](https://slack.k8s.io). He maintains a newsletter called "[Last Week in Kubernetes Development](http://lwkd.info/)", with Noah Kantrowitz. You can read him on Twitter at [@fuzzychef](https://twitter.com/fuzzychef), but he does warn you that there's a lot of politics there as well. [Tim Pepper](https://github.com/tpepper) is also on Slack - he's always open to folks reaching out with a question, looking for help or advice. On Twitter you'll find him at [@pythomit](https://twitter.com/pythomit), which is "Timothy P" backwards. Tim is an avid soccer fan and season ticket holder for the [Portland Timbers](https://portlandtimbers.com/) and the [Portland Thorns](https://portlandthorns.com/), so you'll get all sorts of opinions on soccer in addition to technology! diff --git a/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md b/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md index 2beb0ee5cbc17..2749a56a89133 100644 --- a/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md +++ b/content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md @@ -59,7 +59,7 @@ More crucially, though, the first implementation of the IR allowed rapid prototy ## Ambassador >= v0.50: Envoy v2 APIs (ADS), Testing with KAT, and Golang -In consultation with the [Ambassador community](http://d6e.co/slack), the [Datawire](www.datawire.io) team undertook a redesign of the internals of Ambassador in 2018. This was driven by two key goals. First, we wanted to integrate Envoy's v2 configuration format, which would enable the support of features such as [SNI](https://www.getambassador.io/user-guide/sni/), [rate limiting](https://www.getambassador.io/user-guide/rate-limiting) and [gRPC authentication APIs](https://www.getambassador.io/user-guide/auth-tutorial). Second, we also wanted to do much more robust semantic validation of Envoy configuration due to its increasing complexity (particularly when operating with large-scale application deployments). +In consultation with the [Ambassador community](http://d6e.co/slack), the [Datawire](https://www.datawire.io) team undertook a redesign of the internals of Ambassador in 2018. This was driven by two key goals. First, we wanted to integrate Envoy's v2 configuration format, which would enable the support of features such as [SNI](https://www.getambassador.io/user-guide/sni/), [rate limiting](https://www.getambassador.io/user-guide/rate-limiting) and [gRPC authentication APIs](https://www.getambassador.io/user-guide/auth-tutorial). Second, we also wanted to do much more robust semantic validation of Envoy configuration due to its increasing complexity (particularly when operating with large-scale application deployments). ### Initial stages diff --git a/content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md b/content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md index 741fbd176ee6c..4c3d651dffa51 100644 --- a/content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md +++ b/content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md @@ -19,7 +19,7 @@ We build the contributor summits around you: * docs * code * community management -* [Subproject OWNERs] (aka maintainers in other OSS circles) +* Subproject OWNERs (aka maintainers in other OSS circles) * Special Interest Group (SIG) / Working Group (WG) [Chair or Tech Lead] * Active Contributors * Casual Contributors @@ -57,17 +57,17 @@ Jonas Rosland, Josh Berkus, Paris Pittman, Jorge Castro, Bob Killen, Deb Giles, ## Relive Seattle Contributor Summit -πŸ“ˆ 80% growth rate since the Austin 2017 December event -πŸ“œ Event waiting list: 103 -πŸŽ“ 76 contributors were on-boarded through the New Contributor Workshop -πŸŽ‰ 92% of the current contributors RSVPs attended and of those: -πŸ‘©πŸ»β€πŸš’ 25% were [Special Interest Group] or Working Group Chairs or Tech Leads -πŸ—³ 70% were eligible to vote in the last [steering committee election] (more than 50 contributions in 2018) -πŸ“Ή 20+ [Sessions] -πŸ‘€ Most watched to date: Technical Vision, Security, API Code Base Tour -🌟 Top 3 according to survey: Live API Code Review, Deflaking Unconference, Technical Vision -🎱 🎳 160 attendees for the social at [Garage] on Sunday night where we sunk eight balls and recorded strikes (out in some cases) -πŸ† Special recognition: SIG Storage, @dims, and @jordan +πŸ“ˆ 80% growth rate since the Austin 2017 December event +πŸ“œ Event waiting list: 103 +πŸŽ“ 76 contributors were on-boarded through the New Contributor Workshop +πŸŽ‰ 92% of the current contributors RSVPs attended and of those: +πŸ‘©πŸ»β€πŸš’ 25% were [Special Interest Group] or Working Group Chairs or Tech Leads +πŸ—³ 70% were eligible to vote in the last steering committee election (more than 50 contributions in 2018) +πŸ“Ή 20+ [Sessions] +πŸ‘€ Most watched to date: Technical Vision, Security, API Code Base Tour +🌟 Top 3 according to survey: Live API Code Review, Deflaking Unconference, Technical Vision +🎱 🎳 160 attendees for the social at [Garage] on Sunday night where we sunk eight balls and recorded strikes (out in some cases) +πŸ† Special recognition: SIG Storage, @dims, and @jordan πŸ“Έ Pictures (special thanks to [rdodev]) Garage Pic Reg Desk diff --git a/content/id/docs/concepts/overview/kubernetes-api.md b/content/id/docs/concepts/overview/kubernetes-api.md index 0a8256e7b3508..e997b0c59aaf3 100644 --- a/content/id/docs/concepts/overview/kubernetes-api.md +++ b/content/id/docs/concepts/overview/kubernetes-api.md @@ -11,11 +11,11 @@ card: Secara keseluruhan standar yang digunakan untuk API dijelaskan di dalam [dokumentasi API standar](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md). -Endpoints API, resource types serta contoh penggunaan dijelaskan di dalam [API Reference](/en/docs/reference). +Endpoints API, resource types serta contoh penggunaan dijelaskan di dalam [API Reference](/docs/reference). -Akses remote penggunaan API dijelaskan di dalam [dokumentasi akses API](/en/docs/reference/access-authn-authz/controlling-access/). +Akses remote penggunaan API dijelaskan di dalam [dokumentasi akses API](/docs/reference/access-authn-authz/controlling-access/). -API Kubernetes juga berperan sebagai skema konfigurasi yang deklaratif di dalam sistem.. Sementara itu, [kubectl](/en/docs/reference/kubectl/overview/) merupakan command-line yang dapat digunakan untuk membuat, menmperbaharui, menghapus, dan mendapatkan obyek API. +API Kubernetes juga berperan sebagai skema konfigurasi yang deklaratif di dalam sistem.. Sementara itu, [kubectl](/docs/reference/kubectl/overview/) merupakan command-line yang dapat digunakan untuk membuat, menmperbaharui, menghapus, dan mendapatkan obyek API. Kubernetes menyimpan bentuk terserialisasi dari obyek API yang dimilikinya di dalam [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/). diff --git a/content/id/docs/reference/glossary/platform-developer.md b/content/id/docs/reference/glossary/platform-developer.md index 6256cb6cb582b..96fecad63335e 100644 --- a/content/id/docs/reference/glossary/platform-developer.md +++ b/content/id/docs/reference/glossary/platform-developer.md @@ -14,4 +14,4 @@ tags: -Pengembang platform dapat, misalnya, menggunakan [Sumber Daya Kustom](/docs/concept/api-extension/custom-resources/) atau [Memperluas API Kubernetes dengan lapisan agregasi](/docs/concept/api-extension/apiserver-aggregation/) untuk menambahkan fungsionalitas ke instansi Kubernetes mereka, khususnya untuk aplikasi mereka. Beberapa Pengembang Platform juga {{}} dan mengembangkan perluasan yang berkontribusi pada komunitas Kubernetes. Lainnya mengembangkan sumber tertutup komersial atau perluasan spesifik situs. +Pengembang platform dapat, misalnya, menggunakan [Sumber Daya Kustom](/docs/concept/extend-kubernetes/api-extension/custom-resources/) atau [Memperluas API Kubernetes dengan lapisan agregasi](/docs/concept/extend-kubernetes/api-extension/apiserver-aggregation/) untuk menambahkan fungsionalitas ke instansi Kubernetes mereka, khususnya untuk aplikasi mereka. Beberapa Pengembang Platform juga {{}} dan mengembangkan perluasan yang berkontribusi pada komunitas Kubernetes. Lainnya mengembangkan sumber tertutup komersial atau perluasan spesifik situs. diff --git a/content/ko/docs/concepts/workloads/controllers/replicaset.md b/content/ko/docs/concepts/workloads/controllers/replicaset.md index 545d4a2a11640..1b8c0b8c501fc 100644 --- a/content/ko/docs/concepts/workloads/controllers/replicaset.md +++ b/content/ko/docs/concepts/workloads/controllers/replicaset.md @@ -219,12 +219,12 @@ API 버전에 λŒ€ν•΄μ„œλŠ” `frontend.yaml` 예제의 첫 번째 쀄을 μ°Έκ³ ν•œ μš°λ¦¬λŠ” `frontend.yaml` μ˜ˆμ œμ—μ„œ `tier: frontend`μ΄λΌλŠ” λ ˆμ΄λΈ”μ„ ν•˜λ‚˜ 가지고 μžˆλ‹€. 이 νŒŒλ“œλ₯Ό λ‹€λ₯Έ μ»¨νŠΈλ‘€λŸ¬κ°€ μ·¨ν•˜μ§€ μ•Šλ„λ‘ λ‹€λ₯Έ 컨트둀러의 셀렉터와 κ²ΉμΉ˜μ§€ μ•Šλ„λ‘ μ£Όμ˜ν•΄μ•Ό ν•œλ‹€. -ν…œν”Œλ¦Ώμ˜ [μž¬μ‹œμž‘ μ •μ±…](ko/docs/concepts/workloads/Pods/pod-lifecycle/#restart-policy) ν•„λ“œμΈ +ν…œν”Œλ¦Ώμ˜ [μž¬μ‹œμž‘ μ •μ±…](/ko/docs/concepts/workloads/Pods/pod-lifecycle/#restart-policy) ν•„λ“œμΈ `.spec.template.spec.restartPolicy`λŠ” 기본값인 `Always`만 ν—ˆμš©λœλ‹€. ### νŒŒλ“œ μ…€λ ‰ν„° -`.spec.selector` ν•„λ“œλŠ” [λ ˆμ΄λΈ” μ…€λ ‰ν„°](ko/docs/concepts/overview/working-with-objects/labels/)이닀. +`.spec.selector` ν•„λ“œλŠ” [λ ˆμ΄λΈ” μ…€λ ‰ν„°](/ko/docs/concepts/overview/working-with-objects/labels/)이닀. [μ•žμ„œ](#λ ˆν”Œλ¦¬μΉ΄-μ…‹μ˜-μž‘λ™-방식) λ…Όμ˜ν•œ κ²ƒμ²˜λŸΌ 이 λ ˆμ΄λΈ”μ€ μ†Œμœ λ  κ°€λŠ₯성이 μžˆλŠ” νŒŒλ“œλ₯Ό μ‹λ³„ν•˜λŠ”λ° μ‚¬μš©λœλ‹€. 우리 `frontend.yaml` μ˜ˆμ œμ—μ„œμ˜ μ…€λ ‰ν„°λŠ” λ‹€μŒκ³Ό κ°™λ‹€. ```shell