Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Enable the CNI:none option on Windows nodes #3866

Closed
knabben opened this issue Nov 8, 2022 · 0 comments · Fixed by #3867
Closed

Enable the CNI:none option on Windows nodes #3866

knabben opened this issue Nov 8, 2022 · 0 comments · Fixed by #3867
Labels
area/networking area/windows Related to windows kind/feature Categorizes issue or PR as related to a new feature

Comments

@knabben
Copy link
Member

knabben commented Nov 8, 2022

Describe the feature request
CNI: none is ignored for Windows nodes, it is required to work in order for custom CNI installations work in the cp/nodes.

Describe alternative(s) you've considered
None

Affected product area (please put an X in all that apply)

  • ( ) APIs
  • ( ) Addons
  • ( ) CLI
  • ( ) Docs
  • ( ) IAM
  • (x) Installation
  • ( ) Plugin
  • ( ) Security
  • ( ) Test and Release
  • (x) User Experience
  • ( ) Developer Experience

Additional context
@knabben knabben added kind/feature Categorizes issue or PR as related to a new feature needs-triage Indicates an issue or PR needs to be triaged labels Nov 8, 2022
@knabben knabben mentioned this issue Nov 8, 2022
Merged
@marckhouzam marckhouzam added area/networking area/windows Related to windows and removed needs-triage Indicates an issue or PR needs to be triaged labels Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/networking area/windows Related to windows kind/feature Categorizes issue or PR as related to a new feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Splitting jsonpatches on a conditional antrea installation for windows vmware-tanzu/tanzu-framework
2 participants
@marckhouzam @knabben