Installing csi-proxy in some windows clusters#2012
Conversation
|
private cluster timed out. |
jsturtevant
left a comment
There was a problem hiding this comment.
Is the plan to follow up with a test config after?
I am not 100% sure as I haven't tried this yet but I think it needs to be supported in a few different templates including this one:
Yep |
Thanks, I wasn't sure which all clusters this needed to be enabled for. Hopefully it will be clearer once I start the test-infra/config changes. |
|
/label tide/merge-method-squash |
|
/test pull-kubernetes-e2e-capz-azure-disk-windows It looks like some test jobs for windows + capz + azure-disk were added with kubernetes/test-infra#24065 |
|
@marosset: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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/test-infra repository. |
Nevermind, wrong repo :)
Nevermind, wrong repo :) |
|
/wip |
|
/hold |
| resources: | ||
| - ../default | ||
| - machine-deployment-windows.yaml | ||
| - ../../addons/windows/csi-proxy/csi-proxy-resource-set.yaml |
There was a problem hiding this comment.
We have not been installing Cluster Resource Sets for the default templates, only for the E2E tests. This is mostly because cluster api doesn't include those definitions in what is considered a cluster.
We shouldn't include this in the default template as all addon and other components (such as cni) needs to be managed by the user after the base cluster is up and running.
Since CAPI doesn't deploy CNI's if a customer used this template with a CRS I think they would get errors since they clusterctl generate cluster <template> doesn't include a CNI. I think CRS are also an experimental feature?
The way we are handling this as of today with tilt is to deploy during tilt initialization like:
cluster-api-provider-azure/Tiltfile
Lines 223 to 225 in e2abea2
There was a problem hiding this comment.
Thanks, I was able to get things working this way for dev clusters!
f078607 to
ea16de1
Compare
|
I was able to manually validate that the |
|
/hold cancel |
|
We aren't running the tests against the csi proxy but they are modifying the templates to add them into the CI cluster templates so we should those tests to make sure it doesn't cause any issues /test pull-cluster-api-provider-azure-windows-containerd-upstream-with-ci-artifacts |
5ddbbb5 to
fda29a8
Compare
|
/test pull-cluster-api-provider-azure-windows-containerd-upstream-with-ci-artifacts |
|
It looks like the azure-disk/azure-file csi jobs are targeting Create workload Cluster./home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/envsubst-v2.0.0-20210730161058-179042472c46 < /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/templates/test/ci/cluster-template-prow.yaml Let me update this PR so csi-proxy is installed for those cluster templates |
I made these updates |
|
/test pull-cluster-api-provider-azure-ci-entrypoint |
| @@ -218,6 +218,8 @@ def create_crs(): | |||
| local(kubectl_cmd + " delete configmaps calico-ipv6-addon --ignore-not-found=true") | |||
| local(kubectl_cmd + " create configmap calico-ipv6-addon --from-file=templates/addons/calico-ipv6.yaml") | |||
| local(kubectl_cmd + " delete configmaps flannel-windows-addon --ignore-not-found=true") | |||
There was a problem hiding this comment.
unrelated to this PR but @jsturtevant do you know why we are deleting the flannel-windows-addon cm but not creating it?
There was a problem hiding this comment.
it's created on line https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/2012/files#diff-c2ee8653e1d6b85f0aadf87cd438a9250806c052877248442be4d434cbc52425R226
though it doesn't look like we delete calico-windows-addon which is added the line after. Not sure if deletion is required... Seems to be working, even on reboots of tilt
There was a problem hiding this comment.
I was going to open another PR to fix that
393debc to
f839338
Compare
|
I rebased after #2043 merged and we can now see that csi-proxy container is running on the windows nodes @jsturtevant @mboersma can you all take another look at this PR? Thanks! |
|
@marosset could you squash the commits? lgtm but I would also like to run the conformance tests since those templates are modified though I don't expect anything. |
I added the label to have tide squash the commits for me. Is that sufficient? |
|
This has come up in past. PR release notes don't show up in the release notes with this label. |
Ah ok. |
Adding csi-proxy to windows-containerd dev template Moving csi-proxy addon to cluster-template-prow.yaml since that is what azure-disk/file tests use in CI Signed-off-by: Mark Rossetti <marosset@microsoft.com>
f839338 to
52f8f9d
Compare
|
/remove-label tide/merge-method-squash |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: devigned The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Mark Rossetti marosset@microsoft.com
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):Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: