chore(deps): update dependency kubernetes to v36.0.2

[Varashi]

This PR contains the following updates:

Package	Change	Age	Confidence
kubernetes	36.0.1 → 36.0.2

---

Release Notes

kubernetes-client/python (kubernetes)

v36.0.2: Kubernetes Python Client v36.0.2 Stable Release

Compare Source

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v36.0.2.zip
cd client-python-v36.0.2
python setup-release.py install

Then follow examples in https://github.com/kubernetes-client/python/tree/release-36.0/examples

Changelog: https://github.com/kubernetes-client/python/blob/release-36.0/CHANGELOG.md

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[coderabbitai]

📝 Walkthrough

Walkthrough

Single-line Dockerfile update pins the kubernetes Python package to version 36.0.2, up from 36.0.1. No other build steps, artifacts, or entrypoint configuration change.

Changes

Kubernetes dependency update

Layer / File(s)	Summary
Kubernetes version pin update Dockerfile	Dockerfile pip install bumps kubernetes from 36.0.1 to 36.0.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Varashi/gpu-node-vsphere-maintenance-controller#4: Modifies the same kubernetes dependency pin in Dockerfile.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	Title accurately reflects the main change: updating kubernetes dependency from 36.0.1 to 36.0.2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

Dockerfile (1)

1-1: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Pin base image by digest.

python:3.13-slim is mutable. Build reproducibility and supply-chain guarantees are weaker without a digest pin.

Suggested fix

-FROM python:3.13-slim
+FROM python:3.13-slim@sha256:<resolved_digest>

As per coding guidelines, "Pin base image digest if floating. Multi-stage acceptable."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Dockerfile` at line 1, Replace the floating base image in the Dockerfile (the
FROM python:3.13-slim line) with a digest-pinned reference so builds are
reproducible; obtain the canonical sha256 digest for the exact python:3.13-slim
image you want (via registry/manifest inspection) and update the FROM to use the
tag plus `@sha256`:<digest> (or the registry image@sha256 form) so the Dockerfile
references that specific immutable image.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@Dockerfile`:
- Line 1: Replace the floating base image in the Dockerfile (the FROM
python:3.13-slim line) with a digest-pinned reference so builds are
reproducible; obtain the canonical sha256 digest for the exact python:3.13-slim
image you want (via registry/manifest inspection) and update the FROM to use the
tag plus `@sha256`:<digest> (or the registry image@sha256 form) so the Dockerfile
references that specific immutable image.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 567d7c3f-508a-4c55-a77d-6e46f97db58f

📥 Commits

Reviewing files that changed from the base of the PR and between d69ef1d and 5b78ec4.

📒 Files selected for processing (1)

• Dockerfile