Loading...

XML

Word

Printable

Type: Bug
Resolution: Done-Errata
Priority: Undefined
Fix Version/s: 4.19.0
Affects Version/s: 4.19.0
Component/s: HyperShift
Labels:
- feature-team-cert

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

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None
Epic Link:
CI implementation: Create TLS artifacts registry

Target Backport Versions:
None
Target Version:

4.19.0
Release Blocker:
None
Sprint:
Feature Team Cert - Sprint 265
sprint_count:
1

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

Release Note Status:
In Progress
Release Note Type:
Release Note Not Required
Release Note Text:
None

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

Description of problem:

    In order to make TLS registry tests required we need to make sure all OpenShift variants are using the same metadata for kube-apiserver certs. Hypershift uses several certs stored in the secret without accompanying metadata (namely component ownership).

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

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

relates to

API-1853 CI implementation: Create TLS artifacts registry

In Progress

links to

openshift/hypershift#5355: OCPBUGS-48506: Set ownership annotations for TLS artifacts

RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update

Assignee:: Vadim Rutkovsky

Reporter:: Vadim Rutkovsky

Need Info From:: None

Contributors:: None

QA Contact:: Ke Wang

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2025/01/16 2:26 PM

Updated:: 2025/07/17 1:12 PM

Resolved:: 2025/06/17 4:52 PM