fix(workflow):oci install error

Author: duanhongyi

_scripts/install.sh

@@ -18,6 +18,7 @@ init_arch() {
 }
 
 init_registry() {
+  CHARTS_URL=oci://registry.drycc.cc/$([ $CHANNEL == "stable" ] && echo charts || echo charts-testing)
   if [[ -z "$DRYCC_REGISTRY" ]] ; then
     echo -e "\\033[32m---> Get the fastest drycc registry...\\033[0m"
     registrys=(quay.io ccr.ccs.tencentyun.com sgccr.ccs.tencentyun.com jpccr.ccs.tencentyun.com uswccr.ccs.tencentyun.com useccr.ccs.tencentyun.com deccr.ccs.tencentyun.com saoccr.ccs.tencentyun.com)
@@ -59,8 +60,6 @@ function install_helm {
   tar -zxvf "${tar_name}"
   mv "linux-${ARCH}/helm" /usr/local/bin/helm
   rm -rf "${tar_name}" "linux-${ARCH}"
-  helm repo add --force-update drycc oci://registry.drycc.cc/$([ $CHANNEL == "stable" ] && echo charts || echo charts-testing)
-  helm repo update
 }
 
 function configure_os {
@@ -180,7 +179,7 @@ function check_metallb {
 function install_network() {
   echo -e "\\033[32m--->Start installing network...\\033[0m"
   api_server_address=(`ip -o route get to 8.8.8.8 | sed -n 's/.*src \([0-9.]\+\).*/\1/p'`)
-  helm install cilium drycc/cilium \
+  helm install cilium $CHARTS_URL/cilium \
     --set tunnel=geneve \
     --set operator.replicas=1 \
     --set bandwidthManager=true \
@@ -197,7 +196,7 @@ function install_network() {
 function install_metallb() {
   check_metallb
   echo -e "\\033[32m--->Start installing metallb...\\033[0m"
-  helm install metallb drycc/metallb \
+  helm install metallb $CHARTS_URL/metallb \
     --set speaker.frr.enabled=true \
     --namespace metallb \
     --create-namespace
@@ -246,7 +245,7 @@ EOF
 
 function install_traefik() {
   echo -e "\\033[32m--->Start installing traefik...\\033[0m"
-  helm install traefik drycc/traefik \
+  helm install traefik $CHARTS_URL/traefik \
     --namespace traefik \
     --create-namespace --wait -f - <<EOF
 service:
@@ -270,7 +269,7 @@ EOF
 
 function install_cert_manager() {
   echo -e "\\033[32m--->Start installing cert-manager...\\033[0m"
-  helm install cert-manager drycc/cert-manager \
+  helm install cert-manager $CHARTS_URL/cert-manager \
     --namespace cert-manager \
     --create-namespace \
     --set clusterResourceNamespace=drycc \
@@ -280,7 +279,7 @@ function install_cert_manager() {
 
 function install_catalog() {
   echo -e "\\033[32m--->Start installing catalog...\\033[0m"
-  helm install catalog drycc/catalog \
+  helm install catalog $CHARTS_URL/catalog \
     --set asyncBindingOperationsEnabled=true \
     --set image=docker.io/drycc/service-catalog:canary \
     --namespace catalog \
@@ -477,7 +476,7 @@ imagebuilder:
 EOF
   fi
 
-  helm install drycc drycc/workflow \
+  helm install drycc $CHARTS_URL/workflow \
     --namespace drycc \
     --values /tmp/drycc-values.yaml \
     --values /tmp/drycc-mirror-values.yaml \
@@ -499,7 +498,7 @@ function install_helmbroker {
 
   echo -e "\\033[32m---> Start installing helmbroker...\\033[0m"
 
-  helm install helmbroker drycc/helmbroker \
+  helm install helmbroker $CHARTS_URL/helmbroker \
     --set ingressClass="traefik" \
     --set platformDomain="cluster.local" \
     --set persistence.size=${HELMBROKER_PERSISTENCE_SIZE:-5Gi} \

src/_includes/install-workflow.md

@@ -10,22 +10,12 @@ Server: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b
 
 Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster.
 
-## Add the Drycc Chart Repository
-
-The Drycc Chart Repository contains everything needed to install Drycc Workflow onto a Kubernetes cluster, with a single `helm install drycc/workflow --namespace drycc` command.
-
-Add this repository to Helm:
-
-```
-$ helm repo add drycc oci://registry.drycc.cc/charts
-```
-
 ## Install Drycc Workflow
 
 Now that Helm is installed and the repository has been added, install Workflow by running:
 
 ```
-$ helm install drycc/workflow --namespace drycc
+$ helm install drycc oci://registry.drycc.cc/charts/workflow --namespace drycc
 ```
 
 Helm will install a variety of Kubernetes resources in the `drycc` namespace.

src/installing-workflow/configuring-object-storage.md

@@ -27,27 +27,24 @@ If applicable, generate credentials that have create and write access to the sto
 
 If you are using AWS S3 and your Kubernetes nodes are configured with appropriate [IAM][aws-iam] API keys via InstanceRoles, you do not need to create API credentials. Do, however, validate that the InstanceRole has appropriate permissions to the configured buckets!
 
-### Step 3: Add Drycc Repo
-
-If you haven't already added the Helm repo, do so with `helm repo add drycc oci://registry.drycc.cc/charts`
-
-### Step 4: Configure Workflow Chart
+### Step 3: Configure Workflow Chart
 
 Operators should configure object storage by editing the Helm values file before running `helm install`. To do so:
 
-* Fetch the Helm values by running `helm inspect values drycc/workflow > values.yaml`
+* Fetch the Helm values by running `helm inspect values oci://registry.drycc.cc/charts/workflow > values.yaml`
 * Update the `global/storage` parameter to reference the platform you are using, e.g. `s3`, `azure`, `gcs`, or `swift`
 * Find the corresponding section for your storage type and provide appropriate values including region, bucket names, and access credentials.
 * Save your changes.
 
 !!! note
 	All values will be automatically (base64) encoded _except_ the `key_json` values under `gcs`/`gcr`.  These must be base64-encoded.  This is to support cleanly passing said encoded text via `helm --set` cli functionality rather than attempting to pass the raw JSON data.  For example:
 
-		$ helm install workflow --namespace drycc \
+		$ helm install drycc oci://registry.drycc.cc/charts/workflow \
+		    --namespace drycc \
 			--set global.platformDomain=youdomain.com
 			--set global.storage=gcs,gcs.key_json="$(cat /path/to/gcs_creds.json | base64 -w 0)"
 
-You are now ready to run `helm install drycc/workflow --namespace drycc -f values.yaml` using your desired object storage.
+You are now ready to run `helm install drycc oci://registry.drycc.cc/charts/workflow --namespace drycc -f values.yaml` using your desired object storage.
 
 
 [storage]: ../understanding-workflow/components.md#object-storage

src/installing-workflow/configuring-postgres.md

@@ -39,7 +39,7 @@ The Helm chart for Drycc Workflow can be easily configured to connect the Workfl
     * Save your changes.
     * Note: you do not need to (and must not) base64 encode any values, as the Helm chart will automatically handle encoding as necessary.
 
-You are now ready to `helm install drycc/workflow --namespace drycc -f values.yaml` [as usual][installing].
+You are now ready to `helm install drycc oci://registry.drycc.cc/charts/workflow --namespace drycc -f values.yaml` [as usual][installing].
 
 [database]: ../understanding-workflow/components.md#database
 [object storage]: configuring-object-storage.md

src/installing-workflow/configuring-registry.md

@@ -26,7 +26,7 @@ Drycc Workflow currently supports:
     * Update the `registryLocation` parameter to reference the registry location you are using: `off-cluster`, `ecr`, `gcr`
     * Update the values in the section which corresponds to your registry location type.
 
-You are now ready to `helm install drycc/workflow --namespace drycc -f values.yaml` using your desired registry.
+You are now ready to `helm install drycc oci://registry.drycc.cc/charts/workflow --namespace drycc -f values.yaml` using your desired registry.
 
 ## 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:

src/installing-workflow/index.md

@@ -37,16 +37,6 @@ More rigorous installations would benefit from using outside sources for the fol
 
 Now, workflow requires that ingress and cert-manager must be installed. Any compatible Kubernetes entry controller can be used, but only ingress-nginx and ingress-traefik currently support enforced HTTPS and allowlist. Enable entries in accordance with [this guide](./ingress.md).
 
-## Add the Drycc Chart Repository
-
-The Drycc Chart Repository contains everything needed to install Drycc Workflow onto a Kubernetes cluster, with a single `helm install drycc/workflow --namespace drycc --set global.platformDomain=yourdomain.com` command.
-
-Add this repository to Helm:
-
-```
-$ helm repo add drycc oci://registry.drycc.cc/charts
-```
-
 ## Install Drycc Workflow
 
 If the version of helm is 3.0 +; you need to create the namespace in advance:
@@ -58,9 +48,9 @@ kubectl create ns drycc
 Now that Helm is installed and the repository has been added, install Workflow by running:
 
 ```
-$ helm install --namespace drycc \
-    --set global.platformDomain=drycc.cc \
-    drycc/workflow
+$ helm install drycc oci://registry.drycc.cc/charts/workflow \
+    --namespace drycc \
+    --set global.platformDomain=drycc.cc
 ```
 
 By default, registry uses docker hub, at present, we support three registries. They are:
@@ -72,7 +62,8 @@ By default, registry uses docker hub, at present, we support three registries. T
 If you want to change it, set the variable when using helm.
 
 ```
-$ helm install --namespace drycc \
+$ helm install drycc oci://registry.drycc.cc/charts/workflow \
+    --namespace drycc \
     --set builder.imageRegistry=quay.io \
     --set imagebuilder.imageRegistry=quay.io \
     --set controller.imageRegistry=quay.io \
@@ -86,8 +77,7 @@ $ helm install --namespace drycc \
     --set monitor.imageRegistry=quay.io \
     --set registry.imageRegistry=quay.io \
     --set registry-proxy.imageRegistry=quay.io \
-    --set global.platformDomain=drycc.cc \
-    drycc/workflow
+    --set global.platformDomain=drycc.cc
 ```
 
 Helm will install a variety of Kubernetes resources in the `drycc` namespace.

src/installing-workflow/ingress.md

@@ -5,15 +5,17 @@
 Now that Helm is installed and the repository has been added, install Workflow with a native ingress by running:
 
 ```
-$ helm install drycc/workflow --namespace drycc \
+$ helm install drycc oci://registry.drycc.cc/charts/workflow \
+    --namespace drycc \
     --set global.ingressClass=nginx \
     --set global.platformDomain=drycc.cc \
     --set builder.service.type=LoadBalancer
 ```
 
 Of course, if you deploy it on a bare machine, you probably do not have Load Balancer. You need to use NodePort:
 ```
-$ helm install drycc/workflow --namespace drycc \
+$ helm install drycc oci://registry.drycc.cc/charts/workflow \
+    --namespace drycc \
     --set global.ingressClass=nginx \
     --set global.platformDomain=drycc.cc \
     --set builder.service.type=NodePort \
@@ -65,7 +67,10 @@ Now that Workflow has been deployed with the `global.ingressClass` , we will nee
 Here is an example of how to use [traefik](https://traefik.io/) as an ingress controller for Workflow. Of course, you are welcome to use any controller you wish.
 
 ```
-$ helm install stable/traefik --name ingress --namespace kube-system --set ssl.enabled=true
+$ helm install traefik oci://registry.drycc.cc/charts/traefik \
+    --name ingress \
+    --namespace kube-system \
+    --set ssl.enabled=true
 ```
 
 ## Configure DNS

src/managing-workflow/platform-logging.md

@@ -69,7 +69,8 @@ Error: There are currently no log messages. Please check the following things:
 By default the Fluentd pod can be configured to talk to numerous syslog endpoints. So for example it is possible to have Fluentd send log messages to both the Logger component and [Papertrail](https://papertrailapp.com/). This allows production deployments of Drycc to satisfy stringent logging requirements such as offsite backups of log data.
 
 Configuring Fluentd to talk to multiple syslog endpoints means modifying the Fluentd daemonset
-manifest. This means you will need to fetch the chart with `helm fetch drycc/workflow --untar`, then
+manifest.
+This means you will need to fetch the chart with `helm fetch oci://registry.drycc.cc/charts/workflow --untar`, then
 modify `workflow/charts/fluentd/templates/logger-fluentd-daemon.yaml` with the following:
 
 ```

src/managing-workflow/tuning-component-settings.md

@@ -11,8 +11,14 @@ There are a few ways to customize the respective component:
 
  - If the value is exposed in the `values.yaml` file as derived above, one may modify the section of the component to tune these settings.  The modified value(s) will then take effect at chart installation or release upgrade time via either of the two respective commands:
 
-        $ helm install drycc/workflow -n drycc --namespace drycc -f values.yaml
-        $ helm upgrade drycc -f values.yaml
+        $ helm install drycc oci://registry.drycc.cc/charts/workflow \
+            -n drycc \
+            --namespace drycc \
+            -f values.yaml
+        $ helm upgrade drycc oci://registry.drycc.cc/charts/workflow \
+            -n drycc \
+            --namespace drycc \
+            -f values.yaml
 
  - If the value hasn't yet been exposed in the `values.yaml` file, one may edit the component deployment with the tuned setting.  Here we edit the `drycc-controller` deployment:
 
@@ -22,7 +28,7 @@ There are a few ways to customize the respective component:
 
  - Lastly, one may also fetch and edit the chart as served by version control/the chart repository itself:
 
-        $ helm fetch drycc/workflow --untar
+        $ helm fetch oci://registry.drycc.cc/charts/workflow --untar
         $ $EDITOR workflow/charts/controller/templates/controller-deployment.yaml
 
     Then run `helm install ./workflow --namespace drycc --name drycc` to apply the changes, or `helm upgrade drycc ./workflow` if the cluster is already running.

src/managing-workflow/upgrading-workflow.md

@@ -21,8 +21,7 @@ period of downtime while the database recovers from backup.
 First, find the name of the release helm gave to your deployment with `helm ls`, then run
 
 ```
-$ helm repo update
-$ helm upgrade <release-name> drycc/workflow
+$ helm upgrade <release-name> oci://registry.drycc.cc/charts/workflow
 ```