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

merge upstream 0.0.34 #12

Open
wants to merge 39 commits into
base: master
Choose a base branch
from
Open

Conversation

ncopa
Copy link

@ncopa ncopa commented Dec 27, 2022

No description provided.

cheftako and others added 30 commits September 29, 2022 12:28
Add in the missing license files.

Added requested comment on bakward compatability.
Adding tests for Agent options and validation.
Signed-off-by: Andrew Sy Kim <[email protected]>
Adjust server log verbosity to improve signal:noise
Add rudimentary data transfer benchmark tests
See discussion at
kubernetes-sigs#381

What I did:

- match requirements with k/k release-1.24 branch
- for k8s.io/api and friends, take latest 1.24 tag (v0.24.8)
- delete indirect require section (to generate from scratch)
- go mod tidy
Made sure we properly constructed the admin listener.
Make sure we honored the bind address for the Konn Server.
Added a bind address option for the Konn Agent.
Update go.mod to be more conservative.
Verify if pkt is nil before logging the type.
konnectivity-client: lower goleak version in release-0.0 branch.
Replace deprecated `golint` with `revive`.

Upgrade linter to latest version. Apply lint fixes found.
jkh52 and others added 8 commits December 22, 2022 08:56
v0.0.34: Pick up several new metrics and logging improvements.
Rename variable to make linter happy.

Fixes commit 5d769c1 (Extend agent to support traffic from cluster
to master network.)
We don't need to listen on all interfaces during testing.

Fixes commit 3c39121 (handle data package to agent in the same
goroutine)
Ignore the linter error:
G404: Use of weak random number generator (math/rand instead of crypto/rand) (gosec)

Fix the linter error:
receiver-naming: receiver name t should be consistent with previous receiver name f for testStream (revive)
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.

8 participants