-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
In Progress
-
Bug Fix
-
Previously. after the installation was complete. the kubeconfig file generated by the Agent-Based Installer did not contain the ingress router CA. With this change the kubeconfig contains the ingress router CA upon cluster installation completion.
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-45256. The following is the description of the original issue:
—
Description of problem:
The kubeconfig generate via the openshift-install agent create command does not contain the router CA from the default-ingress-cert
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. openshift-install agent create image
2. Check the content of the generated kubeconfig
Actual results:
conformance parallel test [sig-auth][Feature:LDAP] LDAP IDP should authenticate against an ldap server [apigroup:user.openshift.io][apigroup:route.openshift.io] [Suite:openshift/conformance/parallel] fails
Expected results:
conformance parallel test [sig-auth][Feature:LDAP] LDAP IDP should authenticate against an ldap server [apigroup:user.openshift.io][apigroup:route.openshift.io] [Suite:openshift/conformance/parallel] must pass
Additional info:
The non-ABI installation modifies the generated kubeconfig via the addRouterCAToClusterCA() method, which is always included in the create command (but not as an asset). The same does not happen for the ABI create command
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to