Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update SIG Cloud Provider 2024 annual report #8323

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

elmiko
Copy link
Contributor

@elmiko elmiko commented Feb 11, 2025

adding more content to the initial report.

Which issue(s) this PR fixes:

Fixes #8259

@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 11, 2025
@k8s-ci-robot k8s-ci-robot added area/annual-reports Issues or PRs related to the annual reports cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 11, 2025
@elmiko
Copy link
Contributor Author

elmiko commented Feb 11, 2025

we will discuss this at the next upcoming SIG meeting scheduled for 12 February.

@cprivitere
Copy link
Member

+1 from me

@elmiko
Copy link
Contributor Author

elmiko commented Feb 12, 2025

we are discussing this during the sig office hours, couple points to follow up on:

  • apiserver-network-proxy has added a feature for leader election to detect server count
  • we might have a talk that was given about apiserver-network-proxy, need to double check

@bridgetkromhout
Copy link
Member

Good start!
I suggest adding links to these two blogs posts from 2024:

https://kubernetes.io/blog/2024/03/01/sig-cloud-provider-spotlight-2024/
https://kubernetes.io/blog/2024/05/20/completing-cloud-provider-migration/

adding more content to the initial report.
@elmiko elmiko force-pushed the sig-cloud-provider-2024 branch from 730d024 to 5b470ff Compare February 13, 2025 16:38
@elmiko
Copy link
Contributor Author

elmiko commented Feb 13, 2025

added links and fixed some spelling errors

@elmiko elmiko changed the title WIP update SIG Cloud Provider 2024 annual report update SIG Cloud Provider 2024 annual report Feb 13, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 13, 2025
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/approve
from steering liaison

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elmiko, soltysh

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

The pull request process is described here

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/annual-reports Issues or PRs related to the annual reports cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2024 Annual Report: SIG Cloud Provider
5 participants