Skip to content
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

v1.11 Backports 2023-03-20 #24458

Merged
merged 5 commits into from
Mar 23, 2023
Merged

v1.11 Backports 2023-03-20 #24458

merged 5 commits into from
Mar 23, 2023

Conversation

NikAleksandrov
Copy link

@NikAleksandrov NikAleksandrov commented Mar 20, 2023

Once this PR is merged, you can update the PR labels via:

for pr in 24171 24164 24373 24400 24413; do contrib/backporting/set-labels.py $pr done 1.11; done

or with

make add-labels BRANCH=v1.11 ISSUES=24171,24164,24373,24400,24413

@NikAleksandrov NikAleksandrov requested a review from a team as a code owner March 20, 2023 10:00
@maintainer-s-little-helper maintainer-s-little-helper bot added backport/1.11 This PR represents a backport for Cilium 1.11.x of a PR that was merged to main. kind/backports This PR provides functionality previously merged into master. labels Mar 20, 2023
@NikAleksandrov
Copy link
Author

I had to fix up vp -> viper in the last commit 0557a2f ("Fix for disabled cloud provider rate limiting")

@NikAleksandrov
Copy link
Author

Also noticed a typo in commit 93ebeb3 ("docs: Update the documentation for the conntrack-gc-interval flag")
I'll be sending a pr to fix it up (contrack -> conntrack)

@NikAleksandrov
Copy link
Author

/test

@NikAleksandrov
Copy link
Author

/ci-multicluster

Copy link
Member

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

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

My PR looks good. Thanks!

(How come you're doing backports?)

@NikAleksandrov
Copy link
Author

My PR looks good. Thanks!

(How come you're doing backports?)

I'm first time tophat specifically for backports this week. :)

@hemanthmalla
Copy link
Member

My PR looks good. Thanks for backporting this.

romanspb80 and others added 5 commits March 23, 2023 10:15
[ upstream commit 853ec10 ]

This patch avoide duplicated info in the test-output.log

Fixes: #18515

Signed-off-by: Roman Ptitcyn <romanspb@yahoo.com>
Signed-off-by: Nikolay Aleksandrov <nikolay@isovalent.com>
[ upstream commit 7dbc63a ]

Discovered in community slack that k8s node ExternalIP isn't used by clustermesh even if configured.  Let's be explicit about InternalIP in the documented reqs, until such time as use of node ExternalIP is supported.

Signed-off-by: Jef Spaleta <jspaleta@gmail.com>
[ upstream commit 9ac5b53 ]

When using checker.ExportedEqual(), it was using the standard Equals
checker under-the-hood, but this is incorrect. Fix it to use the correct
checker.

In the commit introducing the bug, there was no direct usage of
checker.ExportedEqual(), but rather checker.ExportedEqual (note the
plural). Subtle!

Discovered while working on improving policy unit tests.

Fixes: f4407e7 ("checker: Add ExportedEquals checker")

Signed-off-by: Chris Tarazi <chris@isovalent.com>
Signed-off-by: Nikolay Aleksandrov <nikolay@isovalent.com>
[ upstream commit 93ebeb3 ]

The current documentation is incorrect as the default value is 0 and not
5 minutes. 0 implies a dynamic interval value, which this commit now
documents.

Signed-off-by: Paul Chaignon <paul@cilium.io>
Signed-off-by: Nikolay Aleksandrov <nikolay@isovalent.com>
[ upstream commit 0557a2f ]

Earlier versions of these flags had a prefix of ENI and were later
renamed with a prefix of IPAM to be consistent across cloud providers.
While removing the deprecated old flags, #12676 also removed lines
needed for setting OperatorConfig struct fields from the values read in.
This resulted in fields having golang defaults, which caused the rate
limiter to be completely bypassed.

Signed-off-by: Hemanth Malla <hemanth.malla@datadoghq.com>
Signed-off-by: Nikolay Aleksandrov <nikolay@isovalent.com>
@youngnick youngnick merged commit d6cd392 into v1.11 Mar 23, 2023
@youngnick youngnick deleted the pr/v1.11-backport-2023-03-20 branch March 23, 2023 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.11 This PR represents a backport for Cilium 1.11.x of a PR that was merged to main. kind/backports This PR provides functionality previously merged into master.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants