-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propagate custom public certificate to env variable #171
Conversation
Can one of the admins verify this patch? |
Signed-off-by: Igor Vinokur <ivinokur@redhat.com>
Docs PR: eclipse-che/che-docs#1078 |
@vinokurig
|
/cc @mmorhun |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is no any specific reason to merge it before 7.9.0 I would like to postpone it.
Fixed |
Done |
a888fc5
to
036955d
Compare
@@ -158,6 +179,9 @@ func NewCheDeployment(cr *orgv1.CheCluster, cheImageAndTag string, cmRevision st | |||
}, | |||
}, | |||
}, | |||
VolumeMounts: []corev1.VolumeMount{ | |||
customPublicCertsVolumeMount, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to be wrong formatted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed the formatting
@vinokurig cd olm
./update-nightly-olm-files.sh And include the generated files into PR |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mainly OK with the changes, but let one comment about automatic rolling update of the Che server deployment when the custom certs are changed.
effectiveGitSelfSignedCert := r.GetDeploymentEnvVarSource(effectiveCheDeployment, "CHE_GIT_SELF__SIGNED__CERT") != nil | ||
if desiredMemRequest.Cmp(effectiveMemRequest) != 0 || | ||
desiredMemLimit.Cmp(effectiveMemLimit) != 0 || | ||
effectiveImagePullPolicy != desiredImagePullPolicy || | ||
effectiveSelfSignedCert != desiredSelfSignedCert || | ||
effectiveCustomPublicCerts != desiredCustomPublicCerts || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that a change in the content of the config map will not trigger a redeploy of the impacted components (mainly the Che server).
You might want to also support this case by doing the same way as what is done for the che
config map (with the current config map resource version being added as a metadata in the Che deployment itself).
@tolusha Do we want to support automatic rolling update of the Che server when the custom public certs config map content is changed ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. it make sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea how to check the certificates config-map changed state. In case of the che config-map
there is a predefined list of values which is compared with the actual values, but the certificates config map hasn't any predefined values. @tolusha @AndrienkoAleksandr @mmorhun @davidfestal WDYT?
[ci-test] |
[test] |
Add a property to configure propagation of custom public certificate from config-map to environment variable
eclipse-che/che#16002