Korean Localization for dev-1.27-ko.1 branch

[seokho-son]

In English

This is a Feature Request

Korean Localization for dev-1.27-ko.1 branch.

What would you like to be added

• [ ] #41631
• [ ] + Any localization contributions for Korean

Comments

• This issue is to notify the schedule of Korean localization to contributors.
• dev-1.27-ko.1 is the current work branch for Korean localization.

Important dates

• A Korean localization work branch is merged to main branch after we complete around 3~4 weeks job.
• Target-PR Freeze: 07/03 (PR opened after freeze will be requested to rebase to next work branch)
• Target-Branch Merge: 07/06 (merge to main branch)

In Korean

기능 추가 요청 이슈

dev-1.27-ko.1 브랜치에 대한 한글화 작업

추가 필요 사항

한글화에 관련된 모든 기여

코멘트

• 컨트리뷰터에게 쿠버네티스 문서 한글화에 대한 작업 스케줄 및 마일스톤을 공유하기 위한 이슈
• 현재 한글화 작업 브랜치는 dev-1.27-ko.1

주요 일정

• 한글화 작업 브랜치는 약 3~4 주간 작업 후, main 브랜치에 머지 됨.
• 목표-PR 프리즈: 07/03 (작업 브랜치에 포함되는 PR을 확정, 이후의 PR은 차기 작업 브랜치로 리베이스 필요)
• 목표-브랜치 머지: 07/06 (main 브랜치에 머지되며, k8s.io에 자동 반영)

/language ko /help

[seokho-son]

/milestone dev-1.27-ko.1

[sftim]

Not yet triaged as accepted /remove-help

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[jihoon-seo]

/triage accepted /remove-lifecycle rotten