Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Critical
Fix Version/s: None
Affects Version/s: 4.12
Component/s: kube-apiserver
Labels:
- cee.neXT
- kube-apiserver

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Critical
Regression:
No

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Priority Data:
PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

openshift-kube-apiserver-operator pod report error: x509 certificate signed by unknown authority

2023-05-16T20:52:27.974006652Z E0516 20:52:27.971789       1 degraded_webhook.go:128] x509: certificate signed by unknown authority
2023-05-16T20:52:28.975440349Z E0516 20:52:28.975411       1 degraded_webhook.go:128] x509: certificate signed by unknown authority
2023-05-16T20:52:31.621076033Z E0516 20:52:31.621043       1 degraded_webhook.go:128] x509: certificate signed by unknown authority

Version-Release number of selected component (if applicable):

$ omc get co
NAME             VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE
kube-apiserver   4.12.15   True        False         False      2d

How reproducible:

Configuring admission webhooks with custom certificates

Assignee:: Unassigned

Reporter:: Ashish Prajapati (Inactive)

Need Info From:: None

Contributors:: None

QA Contact:: Ke Wang

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2023/05/22 2:14 AM

Updated:: 2025/09/13 2:13 PM

Resolved:: 2023/06/15 6:22 PM