kubernetes
[hi] Localize /en/docs/reference/glossary/admission-controller.md
Prerequisites:
- If this is your first contribution, visit Contribute to K8s docs for information on how to get started.
- Review a few examples of localized glossary entries to see which content you change and which you live unchanged.
Procedure:
- Check out
dev-1.22-hi.1and create a working branch calledlocalize-admission-controller.md. - Create a file called
content/hi/docs/reference/glossary/admission-controller.md. - Copy the content of https://raw.githubusercontent.com/kubernetes/website/main/content/en/docs/reference/glossary/admission-controller.md to the file you created.
- Localize the content.
- Push your change and create a pull request.
Completing this feature issue fixes part of https://github.com/kubernetes/website/issues/35600
@rolfedh: This request has been marked as suitable for new contributors.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
/language hi /good-first-issue
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.
Hey @rolfedh, I would like to work on this issue
Thank you, @khannakshat7. I will update the instructions telling volunteers to use /assign <github_id> when they want to claim an issue like this one. This is a proof of concept run. We will create plenty of new issues like this one soon. I look forward to working with you!
Absolutely, Looking forward working with you. Thank You @rolfedh for the info and helping me out with this.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
Hi @GitBatra. Please connect with @bishal7679 about this. Looking above, I see what looks like an open PR waiting to be merged. I also recommend connecting with the team leads on #kubernetes-docs-hi Slack channel, here: https://kubernetes.slack.com/archives/CJ14B9BDJ
Is the isssue still open @rolfedh ? I want to contribute to it as a fresh contributors
Hi @Shubhdeep02, if you review the PR history, it looks like @amolmote has an open PR for this issue. I recommend connecting with Amol and others on Kubernetes Slack to coordinate your contributions.
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
Removing assignees so as to signpost this is accepting new contributors.
