chore(registry): remove ecr and gcr registry

Author: duanhongyi

charts/workflow/values.yaml

@@ -47,8 +47,6 @@ global:
   # Valid values are:
   # - on-cluster: Run registry within the Kubernetes cluster
   # - off-cluster: Use registry outside the Kubernetes cluster (example: dockerhub,quay.io,self-hosted)
-  # - ecr: Use Amazon's ECR
-  # - gcr: Use Google's GCR
   registry_location: "on-cluster"
   # The host port to which registry proxy binds to
   registry_service_port: 5555

src/installing-workflow/configuring-registry.md

@@ -17,8 +17,6 @@ When using a private registry the docker images are no longer pulled by Drycc Wo
 
 Drycc Workflow currently supports:
 
-  1. Google Container Registry([gcr][gcr]).
-  1. EC2 Container Registry([ecr][ecr]).
   1. off-cluster: Any provider which supports long-lived username/password authentication, such as [Azure Container Registry][acr], [Docker Hub][dockerhub], [quay.io][quay], or a self-hosted Docker registry.
 
 ## Configuration
@@ -33,50 +31,6 @@ You are now ready to `helm install drycc/workflow --namespace drycc -f values.ya
 ## Examples
 Here we show how the relevant parts of the fetched `values.yaml` file might look like after configuring for a particular off-cluster registry:
 
-### ECR
-
-```
-global:
-...
-  registry_location: "ecr"
-...
-registry-token-refresher:
-  # Time in minutes after which the token should be refreshed.
-  # Leave it empty to use the default provider time.
-  token_refresh_time: ""
-...
-  ecr:
-    # Your AWS access key. Leave it empty if you want to use IAM credentials.
-    accesskey: "ACCESS_KEY"
-    # Your AWS secret key. Leave it empty if you want to use IAM credentials.
-    secretkey: "SECRET_KEY"
-    # Any S3 region
-    region: "us-west-2"
-    registryid: ""
-    hostname: ""
-...
-```
-**Note:** `registryid` and `hostname` should _not_ be set.  See [this issue](https://github.com/drycc/registry-token-refresher/issues/2) for more info.
-
-### GCR
-
-```
-global:
-...
-  registry_location: "gcr"
-...
-registry-token-refresher:
-  # Time in minutes after which the token should be refreshed.
-  # Leave it empty to use the default provider time.
-  token_refresh_time: ""
-...
-  gcr:
-    key_json: <base64-encoded JSON data>
-    hostname: ""
-```
-
-**Note:** `hostname` should be left empty.
-
 ### [Azure Container Registry](https://azure.microsoft.com/en-us/services/container-registry/) (ACR)
 
 After following the [docs](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-azure-cli) and creating a registry, e.g. `myregistry`, with its corresponding login server of `myregistry.azurecr.io`, the following values should be supplied:
@@ -88,7 +42,7 @@ global:
 ...
 registry-token-refresher:
 ...
-  off_cluster_registry:
+  registry:
     hostname: "myregistry.azurecr.io"
     organization: "myorg"
     username: "myusername"
@@ -107,7 +61,7 @@ global:
 ...
 registry-token-refresher:
 ...
-  off_cluster_registry:
+  registry:
     hostname: "quay.io"
     organization: "myorg"
     username: "myusername"
@@ -117,12 +71,9 @@ registry-token-refresher:
 
 [registry]: ../understanding-workflow/components.md#registry
 [storage]: configuring-object-storage
-[ecr]: http://docs.aws.amazon.com/AmazonECR/latest/userguide/ECR_GetStarted.html
-[gcr]: https://cloud.google.com/container-registry/
 [acr]: https://docs.microsoft.com/en-us/azure/container-registry/
 [dockerhub]: https://hub.docker.com/
 [quay]: https://quay.io/
 [srvAccount]: https://support.google.com/cloud/answer/6158849#serviceaccounts
-[aws-iam]: https://aws.amazon.com/iam/
 [namespace]: https://docs.docker.com/registry/spec/api/#/overview
 [Kubernetes]: https://kubernetes.io