Skip to content
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

[ja] Localization inconsistencies of contents of "Running in multiple zones" #41865

Closed
tuibeovince opened this issue Jul 4, 2023 · 5 comments · Fixed by #46240
Closed

[ja] Localization inconsistencies of contents of "Running in multiple zones" #41865

tuibeovince opened this issue Jul 4, 2023 · 5 comments · Fixed by #46240
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tuibeovince
Copy link
Contributor

This is a Bug Report

Problem:
Inconsitencies of the contents of:

Proposed Solution:
Complete rework of subsections.

Page to Update:
https://kubernetes.io/ja/docs/setup/best-practices/multiple-zones/

Additional Information:
/language ja
/assign

@tuibeovince tuibeovince added the kind/bug Categorizes issue or PR as related to a bug. label Jul 4, 2023
@k8s-ci-robot k8s-ci-robot added language/ja Issues or PRs related to Japanese language needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 4, 2023
@atoato88
Copy link
Contributor

atoato88 commented Sep 1, 2023

/unassign @tuibeovince
It looks no change on this issue for several weeks, so I remove the assignee.
Feel free to re-assign to you, if you have the time to resolve this issue.

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2024
@atoato88
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2024
@atoato88
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 29, 2024
@EigoOda
Copy link
Contributor

EigoOda commented Apr 24, 2024

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants