* [ja] Translated content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md
This commit contains several experimental translation for following words:
Validating Admission Controller: (Pod)検証型のアドミッションコントローラー
Mutating Admission Controller: (Pod)改変型のアドミッションコントローラー
Admission controller is mutating: アドミッションコントローラーがPodを改変する
Pod Security Standard: Podセキュリティ基準 (a modification proposal for 「Podセキュリティの標準」)
Note: These words are not officially authorized by any active committers and localization team members.
If these proposal should not be accepted, these words may be simply rewritten in alphabet or カタカナ語 (IMO).
Further discussion needed.
* Update content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md
remove reviewer fields
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Fixed typo on content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md
* Updated content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md
To meet the newline rule on translation style guide (https://kubernetes.io/ja/docs/contribute/localization/#style-guide).
For exception, markdown list or numbered list begining with `-` or `N.` are ignored to apply the newline rule.
* [ja] Removed experimental translation for admission controler terms in migrate-from-psp.md, fixed format.
Updated content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md:
* to replace `(改変型|検証型)アドミッションコントローラー` with `(Validating|Mutating) Admission Controller`.
* to replace the word `改変` with `変更` to naturally follow the changes above.
* to fix the markdown format to suite the translation style guide.
The removed trial translations of Admission Controller-related terms may be discussed again.
So these proposals are not required for the purpose of the PR, they are removed.
* [ja] fixed translation variation in notion in migrate-from-psp.md: Pod Security level
The variaty of translation for `Pod Security level` is eliminated and it is unified to
`Podセキュリティの水準`.
* Apply suggestions from code review
Co-authored-by: Junya Okabe <86868255+Okabe-Junya@users.noreply.github.com>
Co-authored-by: nasa9084 <nasa9084@users.noreply.github.com>
* Eliminate the style guide violation suggested on the review
* Rewrite `Podセキュリティ基準` with `Podセキュリティ標準`
* Update content/ja/docs/tasks/configure-pod-container/migrate-from-psp.md
Replace `PodSecurityアドミッションコントローラー` with `Podセキュリティ...`
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update migrate-from-psp.md: Replace `WebHook` with `Webhook`
* Update migrate-from-psp.md: add missing `。` to obey the translation style guide
* Update migrate-from-psp.md: Replace `PodSecurityアドミッションコントローラー` with `Podセキュリティアドミッションコントローラー`
---------
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Junya Okabe <86868255+Okabe-Junya@users.noreply.github.com>
Co-authored-by: nasa9084 <nasa9084@users.noreply.github.com>
Translate the card front-matter in the
tasks/access-application-cluster/configure-access-multiple-clusters page
so the correct version shows up in the documentation initial page.
- Align closely to Docsy theme
- Remove duplicated Twitter and Open Graph metadata
- Render the Open Graph image through Hugo Pipes
- Move the theme color to the head-end hook
[CloudCoil](https://github.com/cloudcoil/cloudcoil) - Production-ready Python client for Kubernetes with async support
I've been working on improving the Python development experience for Kubernetes, and I'm excited to share CloudCoil - a modern K8s client that brings features like async/await, type safety, and integrated testing to the Python ecosystem.
Why another Kubernetes client?
In the Python ecosystem, we've been missing features that Go developers take for granted - things like robust client implementations, proper type safety, and integrated testing tools. CloudCoil aims to fix this by providing:
1) Production-focused features:
* 🔥 Elegant, Pythonic API - Feels natural to Python developers
* ⚡ Async First - Native async/await support for high performance
* 🛡️ Type Safe - Full mypy support and runtime validation
* 🧪 Testing Ready - Built-in pytest fixtures for K8s integration tests
* 📦 Zero Config - Works with your existing kubeconfig
* 🪶 Minimal Dependencies - Only requires httpx, pydantic, and pyyaml
2) First-class operator support:
- [cert-manager](https://github.com/cloudcoil/models-cert-manager)
- [FluxCD](https://github.com/cloudcoil/models-fluxcd)
- [Kyverno](https://github.com/cloudcoil/models-kyverno)
(More coming soon - let me know what you'd like to see!)
3) Rich features for production use:
Resource watching with async support:
async for event_type, pod in await core.v1.Pod.async_watch(
field_selector="metadata.name=mypod"
):
if event_type == "DELETED":
break
Smart wait conditions:
pod = core.v1.Pod.get("test-pod")
status = await pod.async_wait_for({
"succeeded": lambda _, pod: pod.status.phase == "Succeeded",
"failed": lambda _, pod: pod.status.phase == "Failed"
}, timeout=300)
Dynamic CRD support:
DynamicCRD = resources.get_dynamic_resource(
"MyCustomResource",
"example.com/v1"
)
resource = DynamicCRD(
metadata={"name": "example"},
spec={"someField": "value"}
).create()
4) Installation:
Choose your K8s version:
# Latest version
pip install cloudcoil[kubernetes]
# Specific K8s version
pip install cloudcoil[kubernetes-1-32]
The project is Apache 2.0 licensed and ready for production use. We'd especially love feedback from:
- Teams using Python for K8s automation
- Anyone building operators/controllers in Python
- DevOps engineers managing multiple clusters
Links:
* GitHub: https://github.com/cloudcoil/cloudcoil
* Docs: https://cloudcoil.github.io/cloudcoil
* PyPI: https://pypi.org/project/cloudcoil
Looking forward to your feedback, especially on what operators you'd like to see supported next!
Kubernetes Prow Robot
OneSazae
Mauren Berti
Arhell
dkarczmarski
Omar kamoun
Adam In Tae Gerard
Daniel Vega-Myhre
Tim Bannister
windsonsea
Yoshiya Maki
Everton Seiei Arakaki
Sayak Mukhopadhyay
xin.li
David Xia
Thomas Gosteli
iheartNathan
Sambhav Kothari
Ruchi1499
Thomas Gosteli