Skip to content

Conversation

nawazkh
Copy link
Member

@nawazkh nawazkh commented Apr 24, 2025

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5586

Special notes for your reviewer:

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests
  • cherry-pick candidate

Release note:

NONE

@k8s-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 24, 2025
Copy link

codecov bot commented Apr 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.27%. Comparing base (14311b2) to head (beb7569).
Report is 9 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5587   +/-   ##
=======================================
  Coverage   53.27%   53.27%           
=======================================
  Files         272      272           
  Lines       29533    29533           
=======================================
  Hits        15735    15735           
  Misses      12983    12983           
  Partials      815      815           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

- update resource deletion commands
- update docs
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 24, 2025
Comment on lines +776 to +779
flavors_needing_vnet_peering = [
"apiserver-ilb",
"windows-apiserver-ilb",
]
Copy link
Member Author

Choose a reason for hiding this comment

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

We probably want to get this exported or updated so that 1P users can add their own flavors that need vnet peerings.
I will open up a good-first-issue to add this.

@nawazkh
Copy link
Member Author

nawazkh commented Apr 24, 2025

/label tide/merge-method-squash

@k8s-ci-robot k8s-ci-robot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Apr 24, 2025
@nawazkh nawazkh marked this pull request as ready for review April 24, 2025 20:10
@nawazkh nawazkh changed the title [WIP] Update Tiltfile Update Tiltfile and APIServer ILB docs Apr 24, 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 Apr 24, 2025
@nawazkh nawazkh moved this from Todo to Needs Review in CAPZ Planning Apr 24, 2025
@nawazkh
Copy link
Member Author

nawazkh commented Apr 24, 2025

/assign @willie-yao @alimaazamat

@k8s-ci-robot
Copy link
Contributor

@nawazkh: GitHub didn't allow me to assign the following users: alimaazamat.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @willie-yao @alimaazamat

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.

@alimaazamat
Copy link
Contributor

/lgtm works locally for me

@nawazkh
Copy link
Member Author

nawazkh commented Apr 24, 2025

@alimaazamat Thank you for checking this Alima! Just to confirm, did you also try clicking "delete-all-workload-clusters" tab ? Did that work as expected too ?

@nawazkh nawazkh added this to the v1.20 milestone Apr 25, 2025
@nawazkh nawazkh changed the title Update Tiltfile and APIServer ILB docs [Tilt] Drop SUBSCRIPTION_TYPE, do not peer vnets for all flavors and update vnet peering logic Apr 28, 2025
@alimaazamat
Copy link
Contributor

@alimaazamat Thank you for checking this Alima! Just to confirm, did you also try clicking "delete-all-workload-clusters" tab ? Did that work as expected too ?

Yes works beautifully!

Copy link
Contributor

@willie-yao willie-yao left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 2, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: eef44b235220e91149db7d5cd3afca1b491beecf

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: willie-yao

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 2, 2025
@k8s-ci-robot k8s-ci-robot merged commit 17a7399 into kubernetes-sigs:main May 2, 2025
25 checks passed
@github-project-automation github-project-automation bot moved this from Needs Review to Done in CAPZ Planning May 2, 2025
jsturtevant pushed a commit to jsturtevant/cluster-api-provider-azure that referenced this pull request May 13, 2025
…update vnet peering logic (kubernetes-sigs#5587)

* remove setting SUBSCRIPTION_TYPE

- update resource deletion commands
- update docs

* update docs
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. 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. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Workload cluster creation/deletion with default flavor via Tilt fails on 1P subscription due to unexpected VNet peering
4 participants