Support additional image registries with self-signed CA certificates#4467
Conversation
|
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #4467 +/- ##
==========================================
- Coverage 49.67% 48.82% -0.86%
==========================================
Files 452 482 +30
Lines 45105 47272 +2167
==========================================
+ Hits 22406 23079 +673
- Misses 20577 22018 +1441
- Partials 2122 2175 +53 see 37 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
919e0b3 to
fbe4494
Compare
|
Cluster Generation A/B Results: |
Users could have application images in private registries with self-signed CA certificates, this patch configure containerd TLS settings for them. For image registries with a public CA certificates, no additional configurations are required for containerd. Legacy config file exposes 3 registries given it can not hold a list object. To add more registries, edit generated Cluster variable.
fbe4494 to
62f7840
Compare
|
Cluster Generation A/B Results: |
…4467) Users could have application images in private registries with self-signed CA certificates, this patch configure containerd TLS settings for them. For image registries with a public CA certificates, no additional configurations are required for containerd. Legacy config file exposes 3 registries given it can not hold a list object. To add more registries, edit generated Cluster variable.
|
Created cherry-pick PR #4479 |
…4467) Users could have application images in private registries with self-signed CA certificates, this patch configure containerd TLS settings for them. For image registries with a public CA certificates, no additional configurations are required for containerd. Legacy config file exposes 3 registries given it can not hold a list object. To add more registries, edit generated Cluster variable.
Users could have application images in private registries with self-signed CA certificates, this patch configure containerd TLS settings for them.
For image registries with a public CA certificates, no additional configurations are required for containerd.
What this PR does / why we need it
Which issue(s) this PR fixes
Fixes #
Describe testing done for PR
Tested with the following legacy configurations:
Tanzu cli generated variable in the cluster manifest
After cluster is ready, launch Pods whose images are from above 2 registries:
Log into a node to do validation:
Release note
Additional information
Special notes for your reviewer