-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[ko] update Korean translation: ingress.md #53829
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/assign |
developowl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ianychoi Thank you for contribution.🥝
I have left some minor reviews. Please take a look and ping me when you're done!
| [플래그](https://kubernetes.github.io/ingress-nginx/#what-is-the-flag-watch-ingress-without-class)를 이용하여 구성될 수 있다. | ||
| 하지만 [아래](#default-ingress-class)에 나와 있는 것과 같이 기본 `IngressClass`를 명시하는 것을 | ||
| [권장](https://kubernetes.github.io/ingress-nginx/#i-have-only-one-instance-of-the-ingresss-nginx-controller-in-my-cluster-what-should-i-do)한다. | ||
| 몇몇 인그레스 컨트롤러는 기본 `IngressClass`가 정의되어 있지 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 몇몇 인그레스 컨트롤러는 기본 `IngressClass`가 정의되어 있지 | |
| 몇몇 인그레스 컨트롤러는 기본 IngressClass가 정의되어 있지 |
| IngressClass의 `.spec.parameters` 필드를 사용하여 | ||
| 해당 IngressClass와 연관있는 환경 설정을 제공하는 다른 리소스를 참조할 수 있다. | ||
|
|
||
| 사용 가능한 파라미터의 상세한 타입은 | ||
| 인그레스클래스의 `.spec.parameters` 필드에 명시한 인그레스 컨트롤러의 종류에 따라 다르다. | ||
| IngressClass의 `.spec.parameters` 필드에 명시한 인그레스 컨트롤러의 종류에 따라 다르다. | ||
|
|
||
| ### 인그레스클래스 범위 | ||
| ### IngressClass 범위 | ||
|
|
||
| 인그레스 컨트롤러의 종류에 따라, 클러스터 범위로 설정한 파라미터의 사용이 가능할 수도 있고, | ||
| 또는 한 네임스페이스에서만 사용 가능할 수도 있다. | ||
|
|
||
| {{< tabs name="tabs_ingressclass_parameter_scope" >}} | ||
| {{% tab name="클러스터" %}} | ||
| 인그레스클래스 파라미터의 기본 범위는 클러스터 범위이다. | ||
| IngressClass 파라미터의 기본 범위는 클러스터 범위이다. | ||
|
|
||
| `.spec.parameters` 필드만 설정하고 `.spec.parameters.scope` 필드는 지정하지 않거나, | ||
| `.spec.parameters.scope` 필드를 `Cluster`로 지정하면, | ||
| 인그레스클래스는 클러스터 범위의 리소스를 참조한다. | ||
| IngressClass는 클러스터 범위의 리소스를 참조한다. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In line 252, it is written as 인그레스 클래스, but you noticed IngressClass is used below. I think it would be better to use consistent terminology throughout the document. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@developowl It is because the original string on L252 is "Ingress class", not "IngressClass". Note that I translated from "Ingress class" to "인그레스 클래스", and from "IngressClass" to "IngressClass" not to be confused. You can also double-check by seeing between L252 and L267.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry to confused between by "IngressClass" and "Ingress Class". Thank you for noted for me.
|
@developowl I have reflected all the comments except one - please take a look. Thank you. |
|
/lgtm /cc @jongwooo I think this PR's looks good to me. Please check this PR. Thank you! 🥝 |
|
LGTM label has been added. DetailsGit tree hash: 897b567090821da7aeed0f1edffe41ed06c7c7f1 |
Description
Update Korean translation on ingress.md
Issue
Closes: #53828