MAJOR windows fixes for secretgen and antrea-cleanup#990
Conversation
f2d9cf5 to
a9591c5
Compare
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
(deleting earlier comment about |
a9591c5 to
988ea3a
Compare
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
0c80479 to
2cdcdc5
Compare
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
2cdcdc5 to
65c8293
Compare
|
Cluster Generation A/B Results: |
|
before merging lets add the one liner to Lets also rename this to "Minor windows fixes for secretgen and antreacleanup" |
|
@hxietkg can you rename this to "two minor fixes to windows YTT" and add unit tests to the MR also (if its possible, I think it should be, I think we should be generating the secretgen in the yaml). |
65c8293 to
44698fa
Compare
|
Cluster Generation A/B Results: |
this is not a bug, we may just disable the secret-gen by adding "SECRETGEN_CONTROLLER_ENABLE: false" to config file. |
|
thats fair - but its still technically a bug on windows side since that SECRETGEN isnt a default disable ... can you add that as a DEFAULT to the windows ytt then ? |
44698fa to
150047a
Compare
|
Cluster Generation A/B Results: |
| filepath.Join(yamlRoot, "ytt", "02_addons", "cpi", "cpi_addon_data.lib.yaml"), | ||
| filepath.Join(yamlRoot, "ytt", "03_customizations", "02_avi", "ako-deployment.lib.yaml"), | ||
| //filepath.Join(YAML_ROOT, "provider-bundle", "providers", "ytt", "02_addons", "cpi", "cpi_addon_data.lib.yaml"), | ||
| filepath.Join(yamlRoot, "ytt", "03_customizations", "03_windows"), |
There was a problem hiding this comment.
ah yes ! thank you for adding this.
| #@ load("@ytt:data", "data") | ||
| #@ if data.values.IS_WINDOWS_WORKLOAD_CLUSTER: | ||
| #@overlay/match by=overlay.subset({"kind":"KubeadmConfigTemplate"}) | ||
| #@overlay/match by=overlay.subset({"kind":"KubeadmConfigTemplate", "metadata":{"name": str(data.values.CLUSTER_NAME) + "-md-0-windows-containerd"}}) |
There was a problem hiding this comment.
interesting . I assume this works, but am curious what changed that now requires us to start doing this?
There was a problem hiding this comment.
OH its because we have multiple kubeadmconfig templates ! duh.
db1e3aa to
aef7d20
Compare
|
Cluster Generation A/B Results: |
|
rebased on 15/Nov |
ac0fe9e to
ea38e56
Compare
| apiVersion: infrastructure.cluster.x-k8s.io/v1beta1 | ||
| kind: VSphereMachineTemplate | ||
| metadata: | ||
| name: '${ CLUSTER_NAME }-worker' |
There was a problem hiding this comment.
well need to potentially disable VSPHERE_AZ_1/2 stuff for now, just to get this merged and working for release
There was a problem hiding this comment.
possible solutions:
- disable VSPHERE_AZs
- enable AZ1/2 in our windows ytt
going w/ one bc...well... time :)
There was a problem hiding this comment.
@stuartpreston fYi were disabling this for expedeince
ea38e56 to
2f778ba
Compare
|
Cluster Generation A/B Results: |
2f778ba to
bc186cb
Compare
|
Cluster Generation A/B Results: |
bc186cb to
bf037c2
Compare
|
Cluster Generation A/B Results: |
bf037c2 to
5670be3
Compare
|
Cluster Generation A/B Results: |
5670be3 to
e249c88
Compare
|
Cluster Generation A/B Results: |
Antrea fails to start after Windows nodes reboot because OVS bridge and HnsNetwork previously created by Antrea is not cleaned, a cleanup script is provided in the new version of Antrea, this change registers the script as a callback on system's shutdown, the cleanup script will be invoked before Windows shutdown. secretgen does not support Windows cluster, just disable it. Disable vsphere-az1/2 on Windows cluster because this is not tested on Windows clusters.
e249c88 to
15f4cb2
Compare
|
Cluster Generation A/B Results: |
|
Please add an entry in the release notes section. |
|
Lgtm clustergen tests are correctly reporting removal of the old error “””Error: : unable to get template: Overlaying (in following order: overlay-windows.yaml, vsphere-overlay.yaml, 01_plans/prod.yaml,””” |
|
Hongsheng please add release note |
several fixes to windows
script as a callback on system's shutdown, the cleanup script will be invoked before Windows shutdown.
…
multiple-azs is supported by #1108, but the change breaks Windows cluster, and this feature was not estimated for Windows cluster, so just disable it for Windows .
What this PR does / why we need it
Antrea-agent fails to start after reboot, so the a Windows node will be re-created once it reboots, this is not expected, we need Windows node support reboot.
also, we fix the other issues mentioned above here for expedience
Which issue(s) this PR fixes
Fixes #988
Describe testing done for PR
Create a windows cluster, then reboot Windows node, and verify antrea-agent in the node after reboot.
Release note
PR Checklist
Additional information
Special notes for your reviewer