Translate Connecting Applications with Services in Bahasa Indonesia#14079
Merged
k8s-ci-robot merged 6 commits intokubernetes:masterfrom May 1, 2019
zufardhiyaulhaq:master
Merged
Translate Connecting Applications with Services in Bahasa Indonesia#14079k8s-ci-robot merged 6 commits intokubernetes:masterfrom zufardhiyaulhaq:master
k8s-ci-robot merged 6 commits intokubernetes:masterfrom
zufardhiyaulhaq:master
Conversation
Contributor
Author
|
/assign @irvifa |
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 3336381 https://deploy-preview-14079--kubernetes-io-master-staging.netlify.com |
80 tasks
Contributor
|
/assign |
Contributor
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
irvifa
reviewed
Apr 30, 2019
|
|
||
| ## Model Kubernetes untuk menghubungkan kontainer | ||
|
|
||
| Sekarang kamu memiliki aplikasi yang telah direplikasi, kamu dapat mengeksposnya di jaringan. Sebelum membahas pendekatan jaringan di Kubernetes, akan lebih baik jika kamu paham bagaimana jaringan bekerja didalam *Docker*. |
Member
There was a problem hiding this comment.
I wonder if we have another wording choice for replicated here hmm
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
|
|
||
| Secara *default*, *Docker* menggunakan jaringan *host*, jadi kontainer dapat berkomunikasi dengan kontainer lainnya jika mereka berada didalam *node* yang sama. Agar kontainer *Docker* dapat berkomunikasi antar *node*, masing-masing kontainer tersebut harus diberikan *port* yang berbeda di alamat *IP node* tersebut, yang akan diteruskan atau di*proxy*kan kedalam kontainer. Artinya adalah para kontainer didalam sebuah *node* harus berkoordinasi *port* mana yang akan digunakan atau dialokasikan secara otomatis. | ||
|
|
||
| Akan sulit untuk mengkoordinasikan *port* yang digunakan oleh banyak pengembang. Kubernetes mengansumsikan bahwa *Pod* dapat berkomunikasi dengan *Pod* lain, terlepas di *Node* mana *Pod* tersebut di *deploy*. Kubernetes memberikan setiap *Pod* alamat *Cluster IP* sehingga kamu tidak perlu secara explisit membuat jalur antara *Pod* ataupun memetakan *port* kontainer kedalam *port* didalam *Node* tersebut. Ini berarti kontainer didalam sebuah *Pod* dapat berkomunikasi dengan *localhost* via *port*, dan setiap *Pod* didalam kluster dapat berkomunikasi tanpa *NAT*. Panduan ini akan membahas bagaimana kamu dapat menjalankan sebuah layanan atau aplikasi didalam model jaringan diatas. |
Member
There was a problem hiding this comment.
should we use developer or pengembang here?
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
irvifa
suggested changes
Apr 30, 2019
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
|
|
||
| IP address pada kolom `EXTERNAL-IP` menujukan *IP* yang tersedia di internet. Sedangkan kolom `CLUSTER-IP* merupakan *IP* yang hanya tersedia didalam kluster kamu (*IP private*). | ||
|
|
||
| Perhatikan pada *AWS*, tipe `LoadBalancer` membuat sebuah *ELB*, yang menggunakan *hostname* yang panjang, bukan *IP*. Karena tidak semua keluar pada standar keluaran `kubectl get svc`. Jadi kamu harus menggunakan `kubectl describe service my-nginx` untuk melihatnya. Kamu akan melihat seperti ini: |
Member
There was a problem hiding this comment.
Any other suggestions on how we translate *hostname* yang panjang
Contributor
Author
There was a problem hiding this comment.
nama objek yang panjang?
irvifa
reviewed
Apr 30, 2019
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
girikuncoro
requested changes
May 1, 2019
Contributor
girikuncoro
left a comment
There was a problem hiding this comment.
Looking great, good job on translating this! Most of my comments are minor fixes on typos and formatting.
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
|
|
||
| Secara *default*, *Docker* menggunakan jaringan *host*, jadi kontainer dapat berkomunikasi dengan kontainer lainnya jika mereka berada didalam *node* yang sama. Agar kontainer *Docker* dapat berkomunikasi antar *node*, masing-masing kontainer tersebut harus diberikan *port* yang berbeda di alamat *IP node* tersebut, yang akan diteruskan atau di*proxy*kan kedalam kontainer. Artinya adalah para kontainer didalam sebuah *node* harus berkoordinasi *port* mana yang akan digunakan atau dialokasikan secara otomatis. | ||
|
|
||
| Akan sulit untuk mengkoordinasikan *port* yang digunakan oleh banyak pengembang. Kubernetes mengansumsikan bahwa *Pod* dapat berkomunikasi dengan *Pod* lain, terlepas di *Node* mana *Pod* tersebut di *deploy*. Kubernetes memberikan setiap *Pod* alamat *Cluster IP* sehingga kamu tidak perlu secara explisit membuat jalur antara *Pod* ataupun memetakan *port* kontainer kedalam *port* didalam *Node* tersebut. Ini berarti kontainer didalam sebuah *Pod* dapat berkomunikasi dengan *localhost* via *port*, dan setiap *Pod* didalam kluster dapat berkomunikasi tanpa *NAT*. Panduan ini akan membahas bagaimana kamu dapat menjalankan sebuah layanan atau aplikasi didalam model jaringan diatas. |
Contributor
| <h1>Welcome to nginx!</h1> | ||
| ``` | ||
|
|
||
| Perlu dicatat bahwa kita menggunakan parameter `-k` saat menggunakan *curl*, ini karena kita tidak tau apapun tentang *Pod* yang menjalankan *nginx* saat pembuatan seritifikat, jadi kita harus memberitahu *curl* untuk mengabaikan ketidakcocokan *CName*. Dengan membuat *Service*, kita menghubungkan *CName* yang digunakan pada sertifikat dengan nama pada *DNS* yang digunakan *Pod*. Lakukan pengujian dari sebuah *Pod* (*secret* yang sama digunakan untuk agar mudah, *Pod* tersebut hanya membutuhkan *nginx.crt* untuk mengakses *Service*) |
Contributor
There was a problem hiding this comment.
(secret yang sama digunakan untuk agar mudah, Pod tersebut hanya membutuhkan nginx.crt untuk mengakses Service)
this sentence doesn't make sense, probably missing translation?
Contributor
Author
There was a problem hiding this comment.
I am translating from the same secret is being reused for simplicity, the pod only needs nginx.crt to access the Service.
Contributor
There was a problem hiding this comment.
let's translate this into:
*secret* yang sama digunakan kembali untuk penyederhanaan, ...
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
content/id/docs/concepts/services-networking/connect-applications-service.md
Outdated
Show resolved
Hide resolved
Contributor
|
we can do follow up PR later for the rest (as it's on going discussion and style still being standardized), I'm going to merge this for now /lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: girikuncoro The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses #13929