(dev-v2.6-archive) moving dev-charts to charts and fixing logo path

(partially cherry picked from commit a224a87038)

packages/canal/charts/Chart.yaml

@@ -7,7 +7,7 @@ home: https://www.projectcalico.org/
 keywords:
   - canal
 sources:
-  - https://github.com/rancher/dev-charts
+  - https://github.com/rancher/charts
 maintainers:
   - name: Rancher Labs
     email: charts@rancher.com

packages/kube-proxy/charts/Chart.yaml

@@ -6,7 +6,7 @@ appVersion: v1.18.4
 keywords:
   - kube-proxy
 sources:
-  - https://github.com/rancher/dev-charts
+  - https://github.com/rancher/charts
 maintainers:
   - name: Rancher Labs
     email: charts@rancher.com

packages/rancher-gatekeeper/rancher-gatekeeper.patch

@@ -14,7 +14,7 @@ diff -x '*.tgz' -x '*.lock' -uNr packages/rancher-gatekeeper/charts-original/Cha
  sources:
    - https://github.com/open-policy-agent/gatekeeper.git
  appVersion: v3.1.0-beta.7
-+icon: https://dev-charts.rancher.io/logos/gatekeeper.svg
++icon: https://charts.rancher.io/assets/logos/gatekeeper.svg
 +annotations:
 +  catalog.cattle.io/certified: rancher
 +  catalog.cattle.io/experimental: true

packages/rancher-istio/charts/Chart.yaml

@@ -3,7 +3,7 @@ appVersion: 1.6.6
 description: Helm chart for installing istio components with the istioctl
 name: rancher-istio-installer
 version: 1.6.600
-icon: https://dev-charts.rancher.io/logos/istio.svg
+icon: https://charts.rancher.io/assets/logos/istio.svg
 annotations:
   catalog.cattle.io/certified: rancher
   catalog.cattle.io/namespace: istio-system

packages/rancher-logging/rancher-logging.patch

@@ -9,7 +9,7 @@ diff -x '*.tgz' -x '*.lock' -uNr packages/rancher-logging/charts-original/Chart.
 +description: A Helm chart to install Banzai Cloud logging-operator and a cluster logging pipeline.
 +name: rancher-logging
  version: 3.4.0
-+icon: https://dev-charts.rancher.io/logos/logging.svg
++icon: https://charts.rancher.io/assets/logos/logging.svg
 +annotations:
 +  catalog.cattle.io/certified: rancher
 +  catalog.cattle.io/namespace: logging-system

packages/rancher-monitoring/rancher-monitoring.patch

@@ -1060,7 +1060,7 @@ diff -x '*.tgz' -x '*.lock' -uNr packages/rancher-monitoring/charts-original/val
 +    port: 9090
 +
 +## RKE PushProx Monitoring
-+## ref: https://github.com/rancher/dev-charts/tree/master/packages/rancher-pushprox
++## ref: https://github.com/rancher/charts/tree/master/packages/rancher-pushprox
 +##
 +rkeControllerManager:
 +  enabled: false
@@ -1116,7 +1116,7 @@ diff -x '*.tgz' -x '*.lock' -uNr packages/rancher-monitoring/charts-original/val
 +      operator: "Exists"
 +
 +## k3s PushProx Monitoring
-+## ref: https://github.com/rancher/dev-charts/tree/master/packages/rancher-pushprox
++## ref: https://github.com/rancher/charts/tree/master/packages/rancher-pushprox
 +##
 +k3sControllerManager:
 +  enabled: false
@@ -1145,7 +1145,7 @@ diff -x '*.tgz' -x '*.lock' -uNr packages/rancher-monitoring/charts-original/val
 +    useLocalhost: true
 +
 +## KubeADM PushProx Monitoring
-+## ref: https://github.com/rancher/dev-charts/tree/master/packages/rancher-pushprox
++## ref: https://github.com/rancher/charts/tree/master/packages/rancher-pushprox
 +##
 +kubeAdmControllerManager:
 +  enabled: false

packages/rancher-pushprox/charts/README.md

@@ -2,7 +2,7 @@
 
 A Rancher chart based on Rancher [PushProx](https://github.com/rancher/PushProx) that sets up a Deployment of a PushProx proxy and a DaemonSet of PushProx clients on a Kubernetes cluster.
 
-Installs [rancher-pushprox](https://github.com/rancher/dev-charts/tree/master/packages/rancher-pushprox) to create PushProx clients that can access their host's network and register with a PushProx proxy. A [Prometheus Operator](https://github.com/coreos/prometheus-operator) ServiceMonitor CR is also included that is configured to scrape the metrics from each of the clients through the proxy.
+Installs [rancher-pushprox](https://github.com/rancher/charts/tree/gh-pages/packages/rancher-pushprox) to create PushProx clients that can access their host's network and register with a PushProx proxy. A [Prometheus Operator](https://github.com/coreos/prometheus-operator) ServiceMonitor CR is also included that is configured to scrape the metrics from each of the clients through the proxy.
 
 Using an instance of this chart is suitable for the following scenarios:
 - You need to scrape metrics from a port that should not be accessible outside of the host (e.g. scraping `etcd` metrics in a hardened cluster)
@@ -51,4 +51,4 @@ The following tables list the configurable parameters of the rancher-pushprox ch
 
 *Tip: The filepaths set in `clients.https.<cert|key|caCert>File` can include wildcard characters*. 
 
-See [rancher-monitoring](https://github.com/rancher/dev-charts/tree/master/packages/rancher-monitoring) for examples of how this chart can be used.
+See [rancher-monitoring](https://github.com/rancher/charts/tree/gh-pages/packages/rancher-monitoring) for examples of how this chart can be used.

packages/rio/charts/Chart.yaml

@@ -4,7 +4,7 @@ version: 0.1.0
 appVersion: 0.8.0-rc1
 description: The application deployment engine for Kubernetes
 home: https://rio.io
-icon: https://dev-charts.rancher.io/logos/rio.svg
+icon: https://charts.rancher.io/assets/logos/rio.svg
 annotations:
   catalog.cattle.io/certified: rancher
   catalog.cattle.io/namespace: rio-system