-
Notifications
You must be signed in to change notification settings - Fork 276
feat(certs): use MeshConfig feature flag to enable MRC #5204
feat(certs): use MeshConfig feature flag to enable MRC #5204
Conversation
3b99920
to
40b2c33
Compare
bcccee7
to
a78c5c4
Compare
cd716f6
to
d772ecc
Compare
Codecov Report
@@ Coverage Diff @@
## main #5204 +/- ##
==========================================
- Coverage 70.33% 70.30% -0.04%
==========================================
Files 195 195
Lines 15694 15697 +3
==========================================
- Hits 11038 11035 -3
- Misses 4601 4607 +6
Partials 55 55
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
6ffa86a
to
dbe3021
Compare
1bde043
to
673d8b5
Compare
d39a3ac
to
2a867cb
Compare
// shouldCreateMeshRootCertificate gets the MeshConfig and returns the values of the enableMeshRootCertificate | ||
// feature flag | ||
func (b *bootstrap) shouldCreateMeshRootCertificate() bool { | ||
config, err := b.configClient.ConfigV1alpha2().MeshConfigs(b.namespace).Get(context.TODO(), meshConfigName, metav1.GetOptions{}) |
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.
can we have this also check if a meshRootCertificate already exists? If there are any we should not create a new one.
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.
Renamed method to shouldEnsureMeshRootCertificate
. The logic to check for an existing active MRCs is in ensureMeshRootCertificate
.
Replace binary flag with MeshConfig feature flag to enable the use of the MRC. If OSM has been installed with EnableMeshRootCertificate disabled, if the feature flag is then enabled in the MeshConfig the control plane components must be restarted in order to pick up on the enabled flag, and begin using the MRC for certificate management. Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
enableMeshRootCertificate feature flag Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
and restart bootstrap before controller and injector. Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
Signed-off-by: jaellio <[email protected]>
2a867cb
to
54136bd
Compare
Description:
Replace binary flag with MeshConfig feature flag to enable the use
of the MRC. If OSM has been installed with
EnableMeshRootCertificate disabled, if the feature flag is then
enabled in the MeshConfig the control plane components must be
restarted in order to pick up on the enabled flag, and begin using
the MRC for certificate management.
Adds an e2e to check enabling the MRC after osm install for each
cert provider.
Dependent on #5201
Resolves #5041
Part of #4835
Testing done:
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project? no
Is this a breaking change? no
Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)? no