Skip to content

chore: update scaleway cloudprovider OWNERS - #10185

Open
pablo-ruth wants to merge 1 commit into
kubernetes:masterfrom
pablo-ruth:pruth-scaleway-owners
Open

chore: update scaleway cloudprovider OWNERS#10185
pablo-ruth wants to merge 1 commit into
kubernetes:masterfrom
pablo-ruth:pruth-scaleway-owners

Conversation

@pablo-ruth

@pablo-ruth pablo-ruth commented Aug 24, 2026

Copy link
Copy Markdown
Member

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Add @damsien @Tomy2e and me as OWNERS of the scaleway provider. We are working on the Kubernetes/Kapsule team and we are members of the Kubernetes org.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


Summary by CodeRabbit

  • Chores
    • Updated project maintenance and review responsibilities to keep contributions routed to the appropriate maintainers.
    • Refreshed the list of designated approvers and reviewers for ongoing project governance.

@kubernetes-prow

Copy link
Copy Markdown
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 24, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

This issue is currently awaiting triage.

If SIG Autoscaling contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. do-not-merge/needs-area Indicates that a PR should not merge because it lacks an area label. labels Aug 24, 2026
@kubernetes-prow
kubernetes-prow Bot requested review from elmiko and remyleone August 24, 2026 13:39
@kubernetes-prow kubernetes-prow Bot added area/cluster-autoscaler Issues or PRs related to the Cluster Autoscaler component and removed do-not-merge/needs-area Indicates that a PR should not merge because it lacks an area label. labels Aug 24, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pablo-ruth
Once this PR has been reviewed and has the lgtm label, please assign x13n for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 24, 2026
@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7a912e4c-97ab-4006-8623-8edb5f898a61

📥 Commits

Reviewing files that changed from the base of the PR and between 2211590 and 4c31104.

📒 Files selected for processing (1)
  • cluster-autoscaler/cloudprovider/scaleway/OWNERS

Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review.


📝 Walkthrough

Walkthrough

The Scaleway ownership configuration now lists three new approvers and reviewers, removes outdated entries, and retains remyleone as a reviewer.

Changes

Scaleway ownership

Layer / File(s) Summary
Update Scaleway ownership configuration
cluster-autoscaler/cloudprovider/scaleway/OWNERS
Adds damsien, pablo-ruth, and Tomy2e as approvers and reviewers. Removes commented former approvers and Sh4d1. Retains remyleone as a reviewer.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 4c311

This change only updates repository ownership metadata and does not alter product behavior or runtime code; no actionable merge-blocking risk remains after normal checks.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating the Scaleway cloudprovider OWNERS file.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@kubernetes-prow

Copy link
Copy Markdown
Contributor

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes org. You can then trigger verification by writing /verify-owners in a comment.

  • Tomy2e
    • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
    • cluster-autoscaler/cloudprovider/scaleway/OWNERS

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Aug 24, 2026
@remyleone

Copy link
Copy Markdown

/lgtm

@kubernetes-prow kubernetes-prow Bot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cluster-autoscaler Issues or PRs related to the Cluster Autoscaler component cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants