Skip to content

Conversation

@jaer-tsun
Copy link
Contributor

@jaer-tsun jaer-tsun commented Nov 26, 2019

What this PR does / why we need it:

  • give precedence to drop rules (over allow)
  • remove telemetry buffer from NPM (removed sidecar as well)
  • write logs to stdout (and file) so that we may see logs using 'kubectl logs...'
  • remove kube-system chain
  • add drop entries in corresponding chain for specific policies (i.e. non ALLOW-ALL* entries)

@jaer-tsun jaer-tsun changed the title give precedence to drop rules (over allow) DROP Entry Precedence & Telemetry Buffer Removal Nov 27, 2019
@tamilmani1989
Copy link
Member

@jaer-tsun can you create separate PRs for telemetry change and drop entry precedence

@jaer-tsun jaer-tsun changed the title DROP Entry Precedence & Telemetry Buffer Removal [DO-NOT-MERGE] DROP Entry Precedence & Telemetry Buffer Removal Nov 27, 2019
- Add drop entry at the end of Ingress-From and Egress-To chains when there are non Allow-All* entries
@jaer-tsun jaer-tsun changed the title [DO-NOT-MERGE] DROP Entry Precedence & Telemetry Buffer Removal Fix NPM Regression & Remove TelemetryBuffer Sidecar Dec 4, 2019
@jaer-tsun jaer-tsun merged commit 61ccd6f into Azure:master Dec 5, 2019
@jaer-tsun jaer-tsun deleted the dropPrecedence branch December 5, 2019 21:58
ashutoshishere04 pushed a commit to ashutoshishere04/azure-container-networking that referenced this pull request Jan 23, 2020
* give precedence to drop rules (over allow)

* - Moving kube-system-chain above target-sets-chain
- Add drop entry at the end of Ingress-From and Egress-To chains when there are non Allow-All* entries

* write logs to stdout (and log file) so that we can see logs via kubectl

* removing kube-system chain and fixing tests

* removing telemetry buffer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants