Bug 1809005
Summary: | No "nodeSelector=kubernetes.io/os: linux" label for image registry and image registry operator | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
Component: | Image Registry | Assignee: | Ricardo Maraschini <rmarasch> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.z | CC: | aos-bugs, rmarasch |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Operator is not setting nodeSelector label on image registry created resources.
Consequence:
This could have affected us in the future as we were not specifying in what nodes our resources can run, we could end up running the registry over unsupported platforms.
Fix:
Added the missing label to created resources.
Result:
It is possible to see the label on the created resources.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-04 18:02:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wenjing Zheng
2020-03-02 09:13:46 UTC
I can see below nodeselector in image-registry deployment, but cannot see it in cluster-image-registry-operator deployment: nodeSelector: kubernetes.io/os: linux Is it by design? Yes, it is by design as per https://github.com/openshift/cluster-image-registry-operator/pull/518#discussion_r408918009 Verified on 4.5.0-0.nightly-2020-05-13-221558: nodeSelector: kubernetes.io/os: linux Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |