Skip to content

chore: resolve lint errors in NetworkUtils #3210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

omerap12
Copy link
Member

What type of PR is this?
cleanup

Which issue does this PR fix?:

What does this PR do / Why do we need it?:
Fixes all lint issues in the networkutils package to improve code quality.

Testing done on this change:

Will this PR introduce any new dependencies?:

Will this break upgrades or downgrades? Has updating a running cluster been tested?:

Does this change require updates to the CNI daemonset config files to work?:

Does this PR introduce any user-facing change?:

NONE

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@omerap12 omerap12 requested a review from a team as a code owner February 21, 2025 11:27
mockIptables.Append("nat", "PREROUTING", "-i", "eni+", "-m", "comment", "--comment", "AWS, outbound connections", "-j", "AWS-CONNMARK-CHAIN-0")
mockIptables.Append("nat", "PREROUTING", "-m", "comment", "--comment", "AWS, CONNMARK", "-j", "CONNMARK", "--restore-mark", "--mask", "0x80")
var err error
err = mockIptables.NewChain("nat", "AWS-SNAT-CHAIN-0")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are mock file changes, while is tempting to fix the lint errors; keeping the status-quo with the rule in line, seems like a better choice right now.

We will close this PR as wont' do.

@orsenthil orsenthil closed this Feb 21, 2025
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.

2 participants