-
Notifications
You must be signed in to change notification settings - Fork 242
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
Remove Kubernetes PodInfoProvider and default to CNI initialization #2087
Conversation
shall we wait to merge this until podsubnet CNI is installed with dropgz? my fear is that someone will forget that it's not ready to release until after that, and we'll break some clusters edit: oh nvm this is a draft, my bad |
@thatmattlong yep, that's why it's still a draft. that's mentioned in the description:notes |
+do-no-merge +work-in-progress to be more clear that this shouldn't be merged until cni installer is default everywhere |
depends on #2075 |
obsoletes/removes changes introduced in #2078 |
Signed-off-by: Evan Baker <[email protected]>
…iant Signed-off-by: Evan Baker <[email protected]>
Signed-off-by: Evan Baker <[email protected]>
Signed-off-by: Evan Baker <[email protected]>
8da36a8
to
19d1bde
Compare
This pull request is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
Pull request closed due to inactivity. |
Reason for Change:
Removes the (long deprecated) Kubernetes reconcile branch from the CNS PodInfo initialization flow. The default is now the CNI reconcile flow, with the preference to restore from CNS own managed endpoint state if that is enabled.
Slightly repackages these components to be clearer:
both are now in pkg
podprovider
instead ofcnireconciler
CNI Pod info provider ->
podprovider/cni
CNS endpoint state pod infor provider moved from cnireconciler ->
podprovider/cns
Since CNI reconciliation is becoming the default, the version check can be dropped as there is no longer another option to fall back to. We simply attempt it, and verbosely error.
Issue Fixed:
Requirements:
Notes:
Because we don't always install the CNI with CNS yet, this is not safe to release until all AKS variants are using the CNI installer init container.