-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Add e2e coverage of apiserver policy functionality #17829
Copy link
Copy link
Open
Labels
area/CI-improvementTopic or proposal to improve the Continuous Integration workflowTopic or proposal to improve the Continuous Integration workflowpinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.
Description
joestringer
opened on Nov 9, 2021
Issue body actions
- Policy match allows traffic from/towards apiserver when deployed within the cluster (eg kind): Add basic kube-apiserver policy matching e2e test #18333
- Policy match allows traffic from/towards apiserver when deployed outside the cluster (eg managed k8s): Add basic kube-apiserver policy matching e2e test #18333
- When new apiserver service endpoints are added, the same policy now allows the traffic.
- When an existing apiserver service endpoint is removed, the same policy now disallows the traffic.
- If you add two identical apiserver policies and then remove one, connectivity still works: Fix kube-apiserver policy matching feature with tunneling enabled #18527
- No impact on connectivity during upgrade
- Send traffic from the apiserver node towards a pod on another node and make sure it matches the policy we expect.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/CI-improvementTopic or proposal to improve the Continuous Integration workflowTopic or proposal to improve the Continuous Integration workflowpinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.