aws: support custom trust bundle for c2s regions #4335
Conversation
openshift-ci-robot
added
the
do-not-merge/work-in-progress
staebler
force-pushed
the
c2s_custom_trust
branch
2 times, most recently
from
b059c65
to
0f2009f
Compare
staebler
changed the title
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
staebler
force-pushed
the
c2s_custom_trust
branch
from
0f2009f
to
8c957c8
Compare
When installing to an AWS C2S region, the user needs to be able to specify additional trust bundles to be used when using the AWS API. These trust bundles need to be made available to the operators in the cluster that use the AWS API. With these changes, the additional trust bundle specified in the install config will be included in the "ca-bundle.pem" key of the cloud-provider-config ConfigMap for AWS C2S installs. Also, the additional trust bundle will be made available to the machine-config-operator running on the bootstrap node in the /opt/openshift/tls/cloud-ca-cert.pem file. https://issues.redhat.com/browse/CORS-1584
staebler
force-pushed
the
c2s_custom_trust
branch
from
8c957c8
to
bcb34f6
Compare
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mtnbikenc, staebler The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/retest Please review the full test history for this PR and help us cut down flakes. |
13 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@staebler: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
When installing to an AWS C2S region, the user needs to be able to specify additional trust bundles to be used when using the AWS API. These trust bundles need to be made available to the operators in the cluster that use the AWS API.
With these changes, the additional trust bundle specified in the install config will be included in the "ca-bundle.pem" key of the cloud-provider-config ConfigMap for AWS C2S installs.
Also, the additional trust bundle will be made available to the machine-config-operator running on the bootstrap node in the /opt/openshift/tls/cloud-ca-cert.pem file.
https://issues.redhat.com/browse/CORS-1584