-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
Important
-
No
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
This is a clone of issue OCPBUGS-23082. The following is the description of the original issue:
—
Description of problem:
From our initial investigation, it seems like the network-node-identity component does not need management cluster access in Hypershift We were looking at: https://github.com/openshift/cluster-network-operator/blob/release-4.14/bindata/network/node-identity/managed/node-identity.yaml For the webhook and approver container: https://github.com/openshift/ovn-kubernetes/blob/release-4.14/go-controller/cmd/ovnkube-identity/ovnkubeidentity.go For the token minter container: https://github.com/openshift/hypershift/blob/release-4.14/token-minter/tokenminter.go We also tested by disabling the automountserviceaccounttoken and things still seemed to be functioning
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Deploy a 4.14 hosted cluster 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-23082 Set automountServiceAccountToken to false for network-node-identity deployment in Hypershift
- Closed
- is blocked by
-
OCPBUGS-23082 Set automountServiceAccountToken to false for network-node-identity deployment in Hypershift
- Closed
- links to
-
RHBA-2023:7470 OpenShift Container Platform 4.14.z bug fix update