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

helm-chart-4.5.0 TLS Issue - SSL peer certificate or SSH remote key was not OK #9621

Closed
guy-microsoft opened this issue Feb 14, 2023 · 6 comments
Closed

helm-chart-4.5.0 TLS Issue - SSL peer certificate or SSH remote key was not OK #9621

guy-microsoft opened this issue Feb 14, 2023 · 6 comments
Assignees
@strongjz
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@guy-microsoft
Copy link

After upgrading chart from 4.4.2 to 4.5.0, we started getting the following error when making requests to our AKS cluster:
SSL peer certificate or SSH remote key was not OK

K8S version: 1.24.9

Reverting to 4.4.2 fixed the issue.
@guy-microsoft guy-microsoft added the kind/bug Categorizes issue or PR as related to a bug. label Feb 14, 2023
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Feb 14, 2023
@gecube
Copy link

gecube commented Feb 14, 2023

Hi! I also was hit by upgrading to 4.5.0 but for another reason

Could you provide more information about what Ingress manifests are you using? Maybe some examples of non-working configuration? I may guess that you are using the SSL client certificate feature, right?

@strongjz strongjz self-assigned this Feb 14, 2023
@strongjz
Copy link
Member

/triage accepted
/priority critical-urgent
/kind bug
/assign @strongjz

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Feb 14, 2023
This was referenced Feb 14, 2023
Merged
Merged
Merged
Closed
@gecube
Copy link

gecube commented Feb 15, 2023

@guy-microsoft Did update to 4.5.2 help?

@strongjz
Copy link
Member

1.6.4 was released with helm 4.5.2; please test with use those; if the issue still persists, reopen this issue with more details

Thank you,
James

/close

@k8s-ci-robot
Copy link
Contributor

@strongjz: Closing this issue.

In response to this:

1.6.4 was released with helm 4.5.2; please test with use those; if the issue still persists, reopen this issue with more details

Thank you,
James

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@guy-microsoft
Copy link
Author

@gecube I'm staying with 4.4.2 for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@strongjz strongjz

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
[SIG Network] Ingress NGINX
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@strongjz @gecube @k8s-ci-robot @guy-microsoft