-
Notifications
You must be signed in to change notification settings - Fork 423
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 tiltfile to support azure cni dev #3609
Conversation
/hold |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #3609 +/- ##
==========================================
- Coverage 53.96% 53.24% -0.73%
==========================================
Files 186 185 -1
Lines 18819 18432 -387
==========================================
- Hits 10156 9814 -342
+ Misses 8118 8076 -42
+ Partials 545 542 -3 ☔ View full report in Codecov by Sentry. |
3828d0a
to
4c9f49e
Compare
@nawazkh I tried deploying a cluster with the "azure-cni-v1" flavor on tilt, everything came up successfully and nodes are Ready but when I list the pods I can see the coredns pods aren't ready:
Looking at the pod describe I see
|
Was able to get this working with k8s v1.27.2. The above repro uses k8s v1.26.1. |
- also update min K8s versions being used - specify CIDR for cloud-controller-manager - fetch CIDR values from the kind: Cluster
I dont see this behavior using K8s
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
LGTM label has been added. Git tree hash: 779c084c95f8d092ec67192f84dfdd202a863d56
|
What type of PR is this?
/kind feature
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):Part of #3610
Special notes for your reviewer:
TODOs:
Release note: