You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/docker-registries/cfcr-deprecation.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ The Codefresh Container registry which is the built-in Docker registry that come
37
37
##Who is affected from the removal of the Codefresh Container registry
38
38
39
39
* If you running the on-prem version of Codefresh, there is no requirement to take immediate action. Your Codefresh account manager will let you know how you will upgrade to the next version.
40
-
* If you running the hybrid version of Codefresh, you are affected andyou alsoneed todecide which external registryyou willuseas caching registry
40
+
* If you running the hybrid version of Codefresh, you are affected and need toselect an external registrytousein your account.
41
41
* If you are using the SAAS version of Codefresh, you are affected and need to select an external registry to use in your account.
42
42
43
43
In most cases migration is trivial, unless you are using solely the Codefresh Container registry for your artifact storage.
@@ -288,7 +288,6 @@ At that start of Phase B (1st April 2020) Codefresh will offer the following new
288
288
Once these features are available for customers, you need to inspect your pipelines and make sure you:
289
289
290
290
1. Set as default registry in your Codefresh account the external one
291
-
1. Set as default caching registry in your Codefresh account the external one (or in your Hybrid Codefresh runner)
292
291
1. If you have more than one external registries, override the default one in any build steps that you want to use another registry other than the default (if this scenario is useful to you)
293
292
1. Disable auto-push on pipelines that don't need it if they also have a push step or you only wish to use the image in the pipeline itself and don't need anywhere else.