cluster-api-provider-azure
cluster-api-provider-azure copied to clipboard
Enable Azure CNI v1 for windows node.
/kind feature
Describe the solution you'd like [A clear and concise description of what you want to happen.]
- Enable Azure CNI v1 for Windows worker nodes.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- cluster-api-provider-azure version:
- Kubernetes version: (use
kubectl version
): - OS (e.g. from
/etc/os-release
):
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Any update on this? We're looking at transitioning from AKS but use Windows nodes & Azure CNI v1 for routable pods.
Is there much involved in getting it working? Alternatively is there another CNI provider we could use, or are we limited to Azure CNI if we want tight Azure VNET integration?
@rcm-steve-horne - I'd like to know more about your use case. Can you please DM me on the kubernetes slack?
@dtzar Sorry for delayed response I missed your reply - no access to Slack internally at the moment unfortunately. Is there another way I can reach you? We're running a large number of .NET Windows containers and with our AKS setup these are routable from on-prem which is helpful for diagnostics etc. It'd be good to understand if this is just a "it might work but we haven't tested it" or "there's no way this will work without significant effort from us, which isn't in the pipeline atm".
LinkedIn and/or my work email are other ways to conact me
Hi @dtzar I attempted to connect on LinkedIn & send an email (to what I guessed was your address) a week ago - did you get either of my messages?