Skip to content

Conversation

@dkoshkin
Copy link
Contributor

What problem does this PR solve?:
Moving the handlers and docs around to make it clear when adding new providers and new handlers if they apply to all providers or only those that use kubeadm too bootstrap the Nodes.

This better aligns with the changes in #1297

Which issue(s) this PR fixes:
Fixes #

How Has This Been Tested?:

Special notes for your reviewer:

@dkoshkin dkoshkin requested review from faiq and jimmidyson September 25, 2025 23:42
Copy link
Member

@jimmidyson jimmidyson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it! Thanks!

@jimmidyson
Copy link
Member

@dkoshkin Needs a rebase.

@dkoshkin dkoshkin force-pushed the dkoshkin/refactor-handler-directories branch 2 times, most recently from 298dfd1 to 928037b Compare September 29, 2025 20:07
@dkoshkin dkoshkin requested a review from supershal September 29, 2025 20:43
@dkoshkin dkoshkin enabled auto-merge (squash) September 30, 2025 20:00
# Conflicts:
#	pkg/handlers/lifecycle/cni/cilium/handler.go
#	pkg/handlers/lifecycle/cni/cilium/handler_integration_test.go
#	pkg/handlers/lifecycle/cni/cilium/template_test.go
@dkoshkin dkoshkin force-pushed the dkoshkin/refactor-handler-directories branch from 928037b to 51d793e Compare October 3, 2025 17:48
Copy link
Contributor

@supershal supershal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much cleaner. Thank you.

@dkoshkin dkoshkin merged commit 1961ebf into main Oct 6, 2025
64 of 70 checks passed
@dkoshkin dkoshkin deleted the dkoshkin/refactor-handler-directories branch October 6, 2025 17:49
dlipovetsky added a commit that referenced this pull request Oct 7, 2025
🤖 I have created a release *beep* *boop*
---


## 0.35.1 (2025-10-07)

<!-- Release notes generated using configuration in .github/release.yaml
at main -->

## What's Changed
### Fixes 🔧
* fix: Remove Cilium chainingMode when kubeproxyreplacement is enabled
by @supershal in
#1340
* fix: Align validation with upstream Kubeadm Bootstrap Provider types
by @dlipovetsky in
#1342
### Other Changes
* refactor: move handler directories by @dkoshkin in
#1321


**Full Changelog**:
v0.35.0...v0.35.1

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
vijayaraghavanr31 pushed a commit that referenced this pull request Oct 8, 2025
**What problem does this PR solve?**:
Moving the handlers and docs around to make it clear when adding new
providers and new handlers if they apply to all providers or only those
that use kubeadm too bootstrap the Nodes.

This better aligns with the changes in
#1297

**Which issue(s) this PR fixes**:
Fixes #

**How Has This Been Tested?**:
<!--
Please describe the tests that you ran to verify your changes.
Provide output from the tests and any manual steps needed to replicate
the tests.
-->

**Special notes for your reviewer**:
<!--
Use this to provide any additional information to the reviewers.
This may include:
- Best way to review the PR.
- Where the author wants the most review attention on.
- etc.
-->
vijayaraghavanr31 pushed a commit that referenced this pull request Oct 8, 2025
🤖 I have created a release *beep* *boop*
---


## 0.35.1 (2025-10-07)

<!-- Release notes generated using configuration in .github/release.yaml
at main -->

## What's Changed
### Fixes 🔧
* fix: Remove Cilium chainingMode when kubeproxyreplacement is enabled
by @supershal in
#1340
* fix: Align validation with upstream Kubeadm Bootstrap Provider types
by @dlipovetsky in
#1342
### Other Changes
* refactor: move handler directories by @dkoshkin in
#1321


**Full Changelog**:
v0.35.0...v0.35.1

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants