[ko] Translate Concepts/Workloads/Pods/Sidecar Containers into Korean

[NAMU1105]

from #44400

[netlify[bot]]

✅ Deploy Preview for k8s-dev-ko ready!

Name	Link
🔨 Latest commit	e133d6d03933a60484ea9be67f59a49303a88095
🔍 Latest deploy log	https://app.netlify.com/sites/k8s-dev-ko/deploys/671936a0b6381d0008d31c4d
😎 Deploy Preview	https://deploy-preview-45250--k8s-dev-ko.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jihoon-seo]

@NAMU1105 님 안녕하세요~ 기여에 감사드립니다. ㅎㅎ

문서의 내용을 보니, v1.29 의 상황을 담고 있는 것으로 보입니다. 하지만 한국어화 번역 작업 브랜치는 그에 따라가지 못하고 v1.27 에 머물고 있어.. 따라가지 못했네요.. ㅎㅎ

그간 이 repo에 code_sample 이라는 shortcode가 추가되었고, 번역하신 문서의 원문이 code_sample shortcode를 활용하고 있어서 이 PR에도 layouts/shortcodes/code_sample.html 파일을 추가하신 것으로 보이는데요

나중에 dev-1.27-ko.1 이 main에 merge될 때 (main에 layouts/shortcodes/code_sample.html 파일이 이미 있는 상황에서) git은 스마트하므로 아마 별 문제는 없을 것 같기는 합니다만.. 여튼 관련하여 나중에 이슈가 발생한다면 (저 또는) 누군가께서 '이 PR에서 이런 히스토리가 있었다' 라고 언급해 주시면 될 것 같습니다.. ㅎㅎ

/uncc @kbhawkey

[jihoon-seo]

/assign

[NAMU1105]

@jihoon-seo 꼼꼼한 피드백 감사합니다! 😭 피드백 반영하여 다시 커밋 올렸습니다. 수정 컨펌 받으면 커밋 스쿼시하겠습니다. 감사합니다!

[jihoon-seo]

@NAMU1105 감사합니다! squash도 부탁드리겠습니다. ㅎㅎ

[NAMU1105]

@NAMU1105 감사합니다! squash도 부탁드리겠습니다. ㅎㅎ

@jihoon-seo squash가 늦어져서 죄송합니다. 완료했습니다!

[netlify[bot]]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	e133d6d03933a60484ea9be67f59a49303a88095
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/671936a0b5ddb10008bda973
😎 Deploy Preview	https://deploy-preview-45250--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR 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 PRs.

This bot triages 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 PR is closed

You can:

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

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

/lifecycle rotten

[jihoon-seo]

@NAMU1105 시간 되실 때 @yoonian 님의 코멘트를 확인 부탁 드리겠습니다. ㅎㅎ

/remove-lifecycle rotten /assign @yoonian

[k8s-ci-robot]

@jihoon-seo: GitHub didn't allow me to assign the following users: yoonian.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide

In response to this:

@NAMU1105 시간 되실 때 @yoonian 님의 코멘트를 확인 부탁 드리겠습니다. ㅎㅎ

/remove-lifecycle rotten /assign @yoonian

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-sigs/prow repository.

[NAMU1105]

@jihoon-seo @yoonian 꼼꼼한 피드백 감사합니다! 👍🙇 피드백 반영하여 다시 커밋 올렸습니다. 수정 컨펌 받으면 커밋 스쿼시하겠습니다. 감사합니다! 🫡

[NAMU1105]

@jihoon-seo 스쿼시 완료하였습니다! 감사합니다 멘토님

[jihoon-seo]

@NAMU1105 @yoonian 정말 고생 많으셨습니다. 감사합니다! /lgtm /approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: fff57764ff44d56831d8976136cd0fa06432d6c8

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jihoon-seo Once this PR has been reviewed and has the lgtm label, please assign onlydole for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[jihoon-seo]

여기에 기재했던 대로, 이 PR이 content/ko/ 밖에 있는 layouts/shortcodes/code_sample.html 파일을 추가하고 있어서 (main에는 이미 있는 파일임) ko approver가 아닌 repo approver의 approve가 필요한 상황입니다.

개인적으로는, 이 PR은 dev-1.27-ko.1 에 있던 파일을 업데이트하는 PR이 아니라, 새로운 번역 파일을 추가하는 PR이므로, main에 바로 merge해도 될 것 같습니다.

따라서

1. repo approver의 approve를 받아서 이 PR을 dev-1.27-ko.1 에 merge하고
2. 추후 dev-1.27-ko.1 을 main에 merge (이 때에도 repo approver의 approve가 필요할 것임)

하는 것 보다는

1. 이 PR의 base (merge target) branch를 main으로 변경 및 올바르게 rebase하고 (이 과정에서, 이 PR이 layouts/shortcodes/code_sample.html 파일을 추가하던 변경사항이 삭제됩니다)
2. ko approver가 이 PR을 main에 merge (이 때에는 repo approver의 approve가 필요하지 않을 것임)

하는 것이 어떨까 싶은데요 @seokho-son 어떻게 생각하시나요.. ㅎㅎ

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR 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 PRs.

This bot triages 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 PR is closed

You can:

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

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

/lifecycle rotten

[ianychoi]

네 저도 지훈님 말씀에 동의합니다.

@NAMU1105: content/ko/ 밖에 있는 layouts/shortcodes/code_sample.html 파일을 추가하고 있어서 (main에는 이미 있는 파일임) 에 대해서는 별도 PR로 올려주시고, language:ko 를 포함한 다른 적절한 label을 함께 추가해주시면 좋겠습니다. 또한 작업하셨던 브랜치 이외에 main 등에도 작업주시면 감사하겠습니다.

저는 review & approve 권한이 없으나 이전에 활동하였었기에 의견을 공유합니다.

개인적 의견으로는 original PR post 기준으로, 1년이 넘었는데, 이는 Kubernetes release 주기와 비교해볼 때 closing을 위해 서로 노력해야하는 상황이 아닌가 싶습니다. 모두 바쁘시겠지만 좋은 PR에 대해 잘 마무리가 될 수 있으면 좋을 것 같습니다. 모두 파이팅입니다!

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages 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 PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/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-sigs/prow repository.