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.

Sign up for GitHub

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

Jump to bottom

Antctl support-bundle command doesn't verify server certificate #758

Closed
weiqiangt opened this issue May 29, 2020 · 5 comments
Closed

Antctl support-bundle command doesn't verify server certificate #758

weiqiangt opened this issue May 29, 2020 · 5 comments
Labels
enhancement New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@weiqiangt
Copy link
Contributor

Describe the problem/challenge you have
Antctl client should verify the server when it is running in remote mode.

Describe the solution you'd like
TODO

Anything else you would like to add?
@weiqiangt weiqiangt added the enhancement New feature or request label May 29, 2020
@weiqiangt weiqiangt mentioned this issue May 29, 2020
Merged
@antoninbas
Copy link
Contributor

I think that only applies when we connect directly to the antrea-agent / antrea-controller, as opposed to when we connect to the k8s apiserver and requests are proxied by kube-aggregator.

@tnqn
Copy link
Member

tnqn commented May 29, 2020

Yes, please clarify the scope of the issue. For now, I think in our documented usage we only connect to antrea components directly for support-bundle subcommand so the issue should be "antctl support-bundle command doesn't verify server certificate"

@weiqiangt weiqiangt changed the title Enable server verification of Antctl Antctl support-bundle command doesn't verify server certificate May 29, 2020
@antoninbas antoninbas mentioned this issue Aug 22, 2020
Closed
@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 26, 2020
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 1, 2020
@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 31, 2021
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 1, 2021
@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 29, 2021
@github-actions github-actions bot closed this as completed Mar 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@antoninbas @tnqn @weiqiangt