Bug 2023813
| Summary: | kube-rbac-proxy image reference is not getting replaced by ART | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Node Feature Discovery Operator | Assignee: | Carlos Eduardo Arango Gutierrez <carangog> |
| Status: | CLOSED ERRATA | QA Contact: | liqcui |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.9 | CC: | aos-bugs, reazz7044, sejug |
| Target Milestone: | --- | ||
| Target Release: | 4.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-22 21:34:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2023810 | ||
| Bug Blocks: | 2023812 | ||
|
Description
OpenShift BugZilla Robot
2021-11-16 15:58:00 UTC
Verified Result
[ocpadmin@ec2-18-217-45-133 nto]$ oc describe pod nfd-controller-manager-6f6b9465d8-dx8n9 -n openshift-nfd
Name: nfd-controller-manager-6f6b9465d8-dx8n9
Namespace: openshift-nfd
Priority: 0
Node: ip-10-0-163-44.us-east-2.compute.internal/10.0.163.44
Start Time: Fri, 19 Nov 2021 03:09:52 +0000
Labels: control-plane=controller-manager
pod-template-hash=6f6b9465d8
Annotations: alm-examples:
[
{
"apiVersion": "nfd.openshift.io/v1",
"kind": "NodeFeatureDiscovery",
"metadata": {
"name": "nfd-instance",
"namespace": "openshift-nfd"
},
"spec": {
"customConfig": {
"configData": "# - name: \"more.kernel.features\"\n# matchOn:\n# - loadedKMod: [\"example_kmod3\"]\n# - name: \"mo...
},
"operand": {
"image": "registry.redhat.io/openshift4/ose-node-feature-discovery@sha256:db53ba3cec56c091946a4521047a9e72deddb1e807286ed788f08710...
"imagePullPolicy": "Always",
"namespace": "openshift-nfd",
"servicePort": 12000
},
"workerConfig": {
"configData": "core:\n# labelWhiteList:\n# noPublish: false\n sleepInterval: 60s\n# sources: [all]\n# klog:\n# addDirHeade...
}
}
}
]
capabilities: Deep Insights
categories: Integration & Delivery,OpenShift Optional
containerImage:
registry.redhat.io/openshift4/ose-cluster-nfd-operator@sha256:a9d92b98c5c746b1d646dbaa2e23496b840a2cce0a3e80969a98b97459bf36ee
description:
The NFD operator creates and maintains the Node Feature Discovery (NFD) on Kubernetes. It detects hardware features available on each nod...
NFD consists of two software components:
## NFD-Master
NFD-Master is the daemon responsible for communication towards the Kubernetes
API. That is, it receives labeling requests from the worker and modifies node
objects accordingly.
## NFD-Worker
NFD-Worker is a daemon responsible for feature detection. It then communicates
the information to nfd-master which does the actual node labeling. One
instance of nfd-worker is supposed to be running on each node of the cluster,
### Feature discovery
Feature discovery is divided into domain-specific feature sources:
- CPU
- IOMMU
- Kernel
- Memory
- Network
- PCI
- Storage
- System
- USB
- Custom (rule-based custom features)
- Local (hooks for user-specific features)
Each feature source is responsible for detecting a set of features which. in
turn, are turned into node feature labels. Feature labels are prefixed with
`feature.node.kubernetes.io/` and also contain the name of the feature source.
Non-standard user-specific feature labels can be created with the local and
custom feature sources.
k8s.v1.cni.cncf.io/network-status:
[{
"name": "openshift-sdn",
"interface": "eth0",
"ips": [
"10.128.2.34"
],
"default": true,
"dns": {}
}]
k8s.v1.cni.cncf.io/networks-status:
[{
"name": "openshift-sdn",
"interface": "eth0",
"ips": [
"10.128.2.34"
],
"default": true,
"dns": {}
}]
olm.operatorGroup: openshift-nfd-mfrpt
olm.operatorNamespace: openshift-nfd
olm.skipRange: >=4.7.0 <4.10.0
olm.targetNamespaces:
openshift.io/scc: anyuid
operatorframework.io/cluster-monitoring: true
operatorframework.io/properties:
{"properties":[{"type":"olm.gvk","value":{"group":"nfd.openshift.io","kind":"NodeFeatureDiscovery","version":"v1"}},{"type":"olm.package",...
operatorframework.io/suggested-namespace: openshift-nfd
operators.openshift.io/infrastructure-features: ["disconnected"]
operators.operatorframework.io/builder: operator-sdk-v1.4.0+git
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
provider: Red Hat
repository: https://github.com/openshift/cluster-nfd-operator
support: Red Hat
Status: Running
IP: 10.128.2.34
IPs:
IP: 10.128.2.34
Controlled By: ReplicaSet/nfd-controller-manager-6f6b9465d8
Containers:
kube-rbac-proxy:
Container ID: cri-o://cde5b6d528d5b92952115247c7b21a8fae328c43029b7b96f11315c07833f9e9
Image: registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:74d95bf1f11829bcaa2619587ec1763d1fd0d559473ff7f623fec96339b8be21
Image ID: registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:74d95bf1f11829bcaa2619587ec1763d1fd0d559473ff7f623fec96339b8be21
Port: 8443/TCP
Host Port: 0/TCP
Args:
--secure-listen-address=0.0.0.0:8443
--upstream=http://127.0.0.1:8080/
--logtostderr=true
--v=10
--tls-cert-file=/etc/secrets/tls.crt
--tls-private-key-file=/etc/secrets/tls.key
--tls-cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
State: Running
Started: Fri, 19 Nov 2021 03:10:01 +0000
Ready: True
Restart Count: 0
Limits:
cpu: 500m
memory: 128Mi
Requests:
cpu: 250m
memory: 64Mi
Environment:
OPERATOR_CONDITION_NAME: nfd.4.10.0-202111170619
Mounts:
/etc/secrets from node-feature-discovery-operator-tls (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mntqs (ro)
manager:
Container ID: cri-o://a79d4aafab3e5628fd12b8519e641b4d7d805c06468767f940f466f9110bd621
Image: registry.redhat.io/openshift4/ose-cluster-nfd-operator@sha256:a9d92b98c5c746b1d646dbaa2e23496b840a2cce0a3e80969a98b97459bf36ee
Image ID: registry.redhat.io/openshift4/ose-cluster-nfd-operator@sha256:a9d92b98c5c746b1d646dbaa2e23496b840a2cce0a3e80969a98b97459bf36ee
Port: 8080/TCP
Host Port: 0/TCP
Command:
/node-feature-discovery-operator
Args:
--metrics-bind-address=127.0.0.1:8080
--leader-elect
State: Running
Started: Fri, 19 Nov 2021 03:10:07 +0000
Ready: True
Restart Count: 0
Liveness: http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
Readiness: http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
Environment:
SSL_CERT_DIR: /etc/pki/tls/certs
WATCH_NAMESPACE: (v1:metadata.annotations['olm.targetNamespaces'])
POD_NAME: nfd-controller-manager-6f6b9465d8-dx8n9 (v1:metadata.name)
OPERATOR_NAME: cluster-nfd-operator
NODE_FEATURE_DISCOVERY_IMAGE: registry.redhat.io/openshift4/ose-node-feature-discovery@sha256:db53ba3cec56c091946a4521047a9e72deddb1e807286ed788f08710086b4202
OPERATOR_CONDITION_NAME: nfd.4.10.0-202111170619
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mntqs (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
node-feature-discovery-operator-tls:
Type: Secret (a volume populated by a Secret)
SecretName: node-feature-discovery-operator-tls
Optional: false
kube-api-access-mntqs:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
ConfigMapName: openshift-service-ca.crt
ConfigMapOptional: <nil>
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/memory-pressure:NoSchedule op=Exists
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 119s default-scheduler Successfully assigned openshift-nfd/nfd-controller-manager-6f6b9465d8-dx8n9 to ip-10-0-163-44.us-east-2.compute.internal
Normal AddedInterface 118s multus Add eth0 [10.128.2.34/23] from openshift-sdn
Normal Pulling 118s kubelet Pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:74d95bf1f11829bcaa2619587ec1763d1fd0d559473ff7f623fec96339b8be21"
Normal Pulled 110s kubelet Successfully pulled image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:74d95bf1f11829bcaa2619587ec1763d1fd0d559473ff7f623fec96339b8be21" in 7.223983835s
Normal Created 110s kubelet Created container kube-rbac-proxy
Normal Started 110s kubelet Started container kube-rbac-proxy
Normal Pulling 110s kubelet Pulling image "registry.redhat.io/openshift4/ose-cluster-nfd-operator@sha256:a9d92b98c5c746b1d646dbaa2e23496b840a2cce0a3e80969a98b97459bf36ee"
Normal Pulled 104s kubelet Successfully pulled image "registry.redhat.io/openshift4/ose-cluster-nfd-operator@sha256:a9d92b98c5c746b1d646dbaa2e23496b840a2cce0a3e80969a98b97459bf36ee" in 5.861083339s
Normal Created 104s kubelet Created container manager
Normal Started 104s kubelet Started container manager
[ocpadmin@ec2-18-217-45-133 nto]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.9.0-0.nightly-2021-11-18-235852 True False 29m Cluster version is 4.9.0-0.nightly-2021-11-18-235852
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.9.8 extras update), 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-2021:4713 As technology continues to transform our world, we want to provide our readers the tools they need to welcome change, seize new opportunities, and stay ahead of the curve. https://reactivem.com/ |