diff --git a/.github/workflows/cancel_workflows.yml b/.github/workflows/cancel_workflows.yml index 76f0289f273..ce676384035 100644 --- a/.github/workflows/cancel_workflows.yml +++ b/.github/workflows/cancel_workflows.yml @@ -10,7 +10,7 @@ jobs: runs-on: ubuntu-latest if: ${{ github.event.workflow_run.event == 'pull_request' }} steps: - - uses: styfle/cancel-workflow-action@0.10.0 + - uses: styfle/cancel-workflow-action@0.10.1 with: all_but_latest: true workflow_id: ${{ github.event.workflow.id }} diff --git a/.golangci.yml b/.golangci.yml index 311f761a78d..1a4d7c68195 100644 --- a/.golangci.yml +++ b/.golangci.yml @@ -13,13 +13,13 @@ linters-settings: ignore-generated-header: false severity: warning confidence: 0.8 - # errorf, var-declaration temporarily disabled because of https://github.com/golangci/golangci-lint/issues/2997 rules: - name: unreachable-code - # - name: errorf + - name: errorf - name: range - name: superfluous-else - # - name: var-declaration + - name: var-declaration + - name: duplicated-imports linters: disable-all: true diff --git a/Makefile b/Makefile index 62bfb1a4842..e2b3e21ef2c 100644 --- a/Makefile +++ b/Makefile @@ -261,7 +261,7 @@ fmt: .golangci-bin: @echo "===> Installing Golangci-lint <===" - @curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $@ v1.48.0 + @curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $@ v1.50.0 .PHONY: golangci golangci: .golangci-bin diff --git a/docs/antrea-network-policy.md b/docs/antrea-network-policy.md index e6d2f89f65d..5fbe7e3d733 100644 --- a/docs/antrea-network-policy.md +++ b/docs/antrea-network-policy.md @@ -636,7 +636,7 @@ to select Pods. More details can be found in the [ServiceAccountSelector](#servi **Note**: The order in which the egress rules are specified matters, i.e., rules will be enforced in the order in which they are written. -**enableLogging**: A ClusterNetworkPolicy ingress or egress rule can be +**enableLogging**: Antrea-native policy ingress or egress rules can be audited by enabling its logging field. When `enableLogging` field is set to true, the first packet of any connection that matches this rule will be logged to a separate file (`/var/log/antrea/networkpolicy/np.log`) on the Node on @@ -645,16 +645,19 @@ analysis. By default, rules are not logged. The example policy logs all traffic that matches the "DropToThirdParty" egress rule, while the rule "AllowFromFrontend" is not logged. Specifically for drop and reject rules, deduplication is applied to reduce duplicated logs, and duplication buffer -length is set to 1 second. The rules are logged in the following format: +length is set to 1 second. If a rule name is not provided, an identifiable +name will be generated for the rule and displayed in the log. +The rules are logged in the following format: ```text -