Skip to content

[CNI Windows] Add support for L4WFPProxyPolicy #1002

@davinci26

Description

@davinci26

Component (Azure NPM or Azure CNI):

Azure CNI

Describe in detail the feature/behavior/change you'd like to see:

As discussed, offline I would like the azure cni plugin to be able to apply the HNS L4WFPProxyPolicy available on Windows Server 2022 to kubernetes pods.

This change is used as an interim solution for development purposes while we work on openservicemesh/osm#1610

A bit more context:
To orchestrate service mesh traffic redirection on Windows we need to apply the L4WFPProxyPolicy which tells the Windows networking stack to redirect all traffic from the pod to the sidecar proxy.

On Windows we can only apply this via a CNI plugin since the initcontainer can not work on Windows due core differences between HNS and iptables. While we work on a fully dynamic solution we would like to use the azure CNI plugin (which is included in AKS-engine) and a static cni config for development/testing purposes.

Orchestrator(e.g. Kubernetes, Docker):
Kubernetes

Operating System (Linux/Windows):
Windows

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions