Tracking Indonesian translation for glossary

[habibrosyad]

This is a tracking issue for Indonesian translation of https://k8s.io/docs/reference/glossary. Below is the list of what has been and need to be translated:

Overal Page:

• Menu, heading and intro of glossary Translate Standardized Glossary page into Bahasa #24180

Terms (by glossary id):

• addons
• admission-controller
• aggregation-layer
• annotation Completing glossary translation for Bahasa pt. 1 #24377
• api-group Completing glossary translation for Bahasa pt. 1 #24377
• app-container
• application-architect
• application-developer
• applications Completing glossary translation for Bahasa pt. 2 #24378
• approver
• certificate
• cgroup Completing glossary translation for Bahasa pt. 2 #24378
• cidr
• cla
• cloud-controller-manager
• cloud-provider
• cluster-architect
• cluster-infrastructure
• cluster-operations
• cluster-operator Completing glossary translation for Bahasa pt. 3 #24379
• cluster Completing glossary translation for Bahasa pt. 3 #24379
• cncf
• cni
• code-contributor
• configmap Completing glossary translation for Bahasa pt. 4 #24391
• container-env-variables Completing glossary translation for Bahasa pt. 4 #24391
• container-lifecycle-hooks
• container-runtime Completing glossary translation for Bahasa pt. 4 #24391
• container Completing glossary translation for Bahasa pt. 4 #24391
• containerd
• contributor
• control-plane Completing glossary translation for Bahasa pt. 4 #24391
• controller Completing glossary translation for Bahasa pt. 5 #24392
• cri-o
• cri Completing glossary translation for Bahasa pt. 5 #24392
• cronjob
• csi
• customresourcedefinition Completing glossary translation for Bahasa pt. 5 #24392
• daemonset Completing glossary translation for Bahasa pt. 5 #24392
• data-plane Completing glossary translation for Bahasa pt. 5 #24392
• deployment Completing glossary translation for Bahasa pt. 6 #24427
• developer
• device-plugin Completing glossary translation for Bahasa pt. 6 #24427
• disruption Completing glossary translation for Bahasa pt. 6 #24427
• docker Completing glossary translation for Bahasa pt. 6 #24427
• downstream
• dynamic-volume-provisioning
• endpoint-slice
• endpoint
• ephemeral-container Completing glossary translation for Bahasa pt. 6 #24427
• etcd
• extensions Completing glossary translation for Bahasa pt. 7 #24428
• flexvolume
• helm-chart
• horizontal-pod-autoscaler
• host-aliases
• image Completing glossary translation for Bahasa pt. 7 #24428
• ingress
• init-container Completing glossary translation for Bahasa pt. 7 #24428
• istio
• job Completing glossary translation for Bahasa pt. 7 #24428
• kops
• kube-apiserver Completing glossary translation for Bahasa pt. 7 #24428
• kube-controller-manager Completing glossary translation for Bahasa pt. 8 #26090
• kube-proxy Completing glossary translation for Bahasa pt. 8 #26090
• kube-scheduler Completing glossary translation for Bahasa pt. 8 #26090
• kubeadm
• kubectl Completing glossary translation for Bahasa pt. 8 #26090
• kubelet Completing glossary translation for Bahasa pt. 8 #26090
• kubernetes-api Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• label Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• limitrange Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• logging Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• managed-service
• manifest Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• master Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• member
• minikube Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• mirror-pod Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• name Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• namespace Translate glossary for Namespace into Bahasa #24111
• network-policy
• node Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• operator-pattern
• persistent-volume-claim Translate glossary for PersistentVolumeClaim into Bahasa #24094 Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• persistent-volume Translate glossary for PersistentVolume into Bahasa #24088 Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• platform-developer
• pod-disruption-budget
• pod-lifecycle Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• pod-priority
• pod-security-policy Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• pod Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• podpreset
• preemption
• proxy
• qos-class Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• quantity Completing glossary translation for Bahasa pt. 8 #26090
• rbac Translate glossary for RBAC into Bahasa #24211 Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• replica-set Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• replication-controller
• resource-quota Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• reviewer
• rkt
• secret
• security-context
• selector Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• service-account Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• service-broker
• service-catalog
• service Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• shuffle-sharding Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• sig
• statefulset Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• static-pod Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• storage-class
• sysctl
• taint Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• toleration Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• uid Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• upstream
• volume-plugin
• volume Translate glossaries tagged as fundamental into Bahasa #24347 [revise]
• wg
• workload Translate glossaries tagged as fundamental into Bahasa #24347 [revise]

Note:
[review] - PR exists, under review
[revise] - Exclusive label PR #24347 which is closed due to the huge size, and need to be split into smaller PRs

• - Translation exists
• - No translation (or PR exists but not merged yet)

/assign
/language id
/cc @kubernetes/sig-docs-id-reviews

[habibrosyad]

fyi @irvifa @ariscahyadi @girikuncoro

[girikuncoro]

This is great, thanks for this initiative @habibrosyad !

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

/remove-lifecycle stale

[irvifa]

@habibrosyad do we still track this issue here? Any expected timeline?

[habibrosyad]

@irvifa Yep, just for the glossary. I still could not find a time to continue working on this issue. So I'm just keeping it alive just in case. What do you think?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[habibrosyad]

Let me close this issue for the time being, reducing the open issue on the website, and reopen it later when we have the bandwidth to tackle it.

/close

[k8s-ci-robot]

@habibrosyad: Closing this issue.

In response to this:

Let me close this issue for the time being, reducing the open issue on the website, and reopen it later when we have the bandwidth to tackle it.

/close

Instructions 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.