all: Use last [email protected] and bump chart version to push new OCI format

cern-eos · Apr 27, 2023 · 9a0a606 · 9a0a606
1 parent f8e7f9c
commit 9a0a606
Show file tree

Hide file tree

Showing 13 changed files with 45 additions and 44 deletions.
diff --git a/fst/Chart.yaml b/fst/Chart.yaml
@@ -2,12 +2,12 @@ apiVersion: v2
 #
 name: fst
 type: application
-version: 0.1.4
+version: 0.1.5
 appVersion: 4.8.78
 #
 description: An EOS FST chart
 icon: https://eos-web.web.cern.ch/eos-web/assets/images/eos-icon-white-713x824.png
 dependencies:
 - name: utils
-  version: 0.1.6
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"
diff --git a/fst/README.md b/fst/README.md
@@ -2,22 +2,23 @@
 
 An EOS FST chart
 
-![Version: 0.1.4](https://img.shields.io/badge/Version-0.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
+![Version: 0.1.5](https://img.shields.io/badge/Version-0.1.5-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
 
 Helm Chart to deploy EOS FSTs.
 
 ## Requirements
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.6 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ## Values
 
 | Key | Type | Default | Description |
 |-----|------|---------|-------------|
 | customLabels | object | `{"component":"eos-fst","service":"eos"}` | Custom labels to identify eos fst pods.    They are used by node selection, if enabled (see above).   Label nodes accordingly to avoid scheduling problems.  |
 | dnsPolicy | string | `"ClusterFirst"` | dnsPolicy regulates how the pod resolves hostnames with DNS servers.    In case hostNetwork is set to true, dnsPolicy must be ClusterFirstWithHostNet    Documentation: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/    Available options: Default, ClusterFirst, ClusterFirstWithHostNet, None    Default: ClusterFirst |
+| externalService | object | `{"annotations":null,"enabled":false,"loadBalancerIPs":[],"template":{"type":"LoadBalancer"}}` | External services for FSTs, so each one can be individually reached from outside the cluster (requires a LBaaS).    They will be created based on the template if enabled is 'true'. Probably only makes sense for LoadBalancer-type services.    If you want to specify the LB IP addresses of each service, fill the loadBalancerIPs list (must be the same length as the FST replicaCount). |
 | extraEnv | object | `{}` |  |
 | geotag | string | `""` | EOS GeoTag    Tag storage node with their geographical location   Docs: https://eos-docs.web.cern.ch/configuration/geotags.html    Defaults to "docker::k8s"   GeoTag can be overriden with:    - .Values.geotag    - Global .Values.global.hostname.eos.geotag in a parent chart.    Global takes precedence over local values. |
 | global.clusterDomain | string | `"cluster.local"` | Set this to the domain name of your cluster if it does not use the kubernetes default. |
@@ -31,7 +32,7 @@ Helm Chart to deploy EOS FSTs.
 | image.repository | string | `"gitlab-registry.cern.ch/dss/eos/eos-all"` | image repository for fst image |
 | image.tag | string | `"4.8.78"` | FST image tag |
 | minFsSizeGb | int | `5` | EOS minimum size of filesystem on FST to allow writes    See EOS_FS_FULL_SIZE_IN_GB in    https://gitlab.cern.ch/dss/eos/-/blob/master/fst/storage/Storage.cc |
-| persistence | object | `{"accessModes":["ReadWriteOnce"],"annotations":{},"enabled":false,"size":"1Ti","storageClass":""}` | Manage persistence of data stored by FSTs, namely the actual bytes of files stored in EOS.     If persistence is not enabled, data stored in FSTs will not survive the restart of pods.    It is recommended to configure persistence according to the hosting infrastrcuture.     The persistency can be configured by setting the `enabled` flag:     - false:       No persistence provided. Data is stored in emptyDir volumes.     - true:       Persistence provided by mounting a PersistentVolume via a claim. Requires either:       - a dynamic provisioner (for example, on Openstack, Cinder CSI or Manila CSI), or       - statically provisioned PersistentVolumes pre-created by an administrator      Note that each FST requires its own separate and independent storage location.     When using a shared filesystem as persistent backend, each PV must live in a separate directory.     This is handed automatically in the case of a dynamic provisioner,     and must be configured manually (by use of 'path' and 'claimRef') in the case of static PVs.       Docs: https://kubernetes.io/docs/concepts/storage/persistent-volumes/      Additional parameters:     - storageClass: If set to "-", disable dynamic provisioning.                     If undefined or null, the default provisioner is chosen.     - accessModes: How to access the pvc (ReadWriteOnce, ReadOnlyMany, ReadWriteMany)     - size: Size of the pvs (example, 10Gi)     - annotations: Custom annotations on the pvc, in key:value format  The persistence type can be overriden via .Values.global.persistence.enabled.  |
+| persistence | object | `{"accessModes":["ReadWriteOnce"],"annotations":{},"enabled":false,"size":"1Ti","storageClass":""}` | Manage persistence of data stored by FSTs, namely the actual bytes of files stored in EOS.     If persistence is not enabled, data stored in FSTs will not survive the restart of pods.    It is recommended to configure persistence according to the hosting infrastructure.     The persistency can be configured by setting the `enabled` flag:     - false:       No persistence provided. Data is stored in emptyDir volumes.     - true:       Persistence provided by mounting a PersistentVolume via a claim. Requires either:       - a dynamic provisioner (for example, on Openstack, Cinder CSI or Manila CSI), or       - statically provisioned PersistentVolumes pre-created by an administrator      Note that each FST requires its own separate and independent storage location.     When using a shared filesystem as persistent backend, each PV must live in a separate directory.     This is handed automatically in the case of a dynamic provisioner,     and must be configured manually (by use of 'path' and 'claimRef') in the case of static PVs.       Docs: https://kubernetes.io/docs/concepts/storage/persistent-volumes/      Additional parameters:     - storageClass: If set to "-", disable dynamic provisioning.                     If undefined or null, the default provisioner is chosen.     - accessModes: How to access the pvc (ReadWriteOnce, ReadOnlyMany, ReadWriteMany)     - size: Size of the pvs (example, 10Gi)     - annotations: Custom annotations on the pvc, in key:value format  The persistence type can be overriden via .Values.global.persistence.enabled.  |
 | podAssignment | object | `{"enableNodeSelector":false,"enablePodAntiAffinity":true}` | Assign fst pods to a node with a specific label    and distribute them on different nodes to avoid single points of failure.  |
 | podAssignment.enableNodeSelector | bool | `false` | If true, requires a node labeled as per customLabels. |
 | podAssignment.enablePodAntiAffinity | bool | `true` | If true, shard the stateful set on as many nodes as possible.    Highly recommended for production scenarios. |

diff --git a/fusex/Chart.yaml b/fusex/Chart.yaml
@@ -2,7 +2,7 @@ apiVersion: v2
 #
 name: fusex
 type: application
-version: 0.1.3
+version: 0.1.4
 appVersion: 4.8.86
 #
 description: An EOS FuseX chart
@@ -11,5 +11,5 @@ annotations:
   documentation: https://github.com/cern-eos/eos/blob/master/fusex/README.md
 dependencies:
 - name: utils
-  version: 0.1.4
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"
diff --git a/fusex/README.md b/fusex/README.md
@@ -4,13 +4,13 @@
 
 -----
 
-![Version: 0.1.3](https://img.shields.io/badge/Version-0.1.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.86](https://img.shields.io/badge/AppVersion-4.8.86-informational?style=flat-square)
+![Version: 0.1.4](https://img.shields.io/badge/Version-0.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.86](https://img.shields.io/badge/AppVersion-4.8.86-informational?style=flat-square)
 
 ## Requirements
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.4 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ### What for
 This chart provides the ability to run an EOS Fusex mount in a pod.

diff --git a/mgm/Chart.yaml b/mgm/Chart.yaml
@@ -2,12 +2,12 @@ apiVersion: v2
 #
 name: mgm
 type: application
-version: 0.1.6 
+version: 0.1.7 
 appVersion: 4.8.80
 #
 description: An EOS MGM + MQ chart
 icon: https://eos-web.web.cern.ch/eos-web/assets/images/eos-icon-white-713x824.png
 dependencies:
 - name: utils
-  version: 0.1.6
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"
diff --git a/mgm/README.md b/mgm/README.md
@@ -11,7 +11,7 @@ Helm Chart to deploy EOS MGM.
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.6 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ## Values
 

diff --git a/mq/Chart.yaml b/mq/Chart.yaml
@@ -12,12 +12,12 @@ apiVersion: v2
 #
 name: mq
 type: application
-version: 0.1.2
+version: 0.1.3
 appVersion: 4.8.78
 #
 description: An EOS MQ chart
 icon: https://eos-web.web.cern.ch/eos-web/assets/images/eos-icon-white-713x824.png
 dependencies:
 - name: utils
-  version: 0.1.5
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"
diff --git a/mq/README.md b/mq/README.md
@@ -2,15 +2,15 @@
 
 An EOS MQ chart
 
-![Version: 0.1.2](https://img.shields.io/badge/Version-0.1.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
+![Version: 0.1.3](https://img.shields.io/badge/Version-0.1.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
 
 Helm Chart to deploy EOS MQ.
 
 ## Requirements
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.5 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ## Values
 

diff --git a/qdb/Chart.yaml b/qdb/Chart.yaml
@@ -2,12 +2,12 @@ apiVersion: v2
 #
 name: qdb
 type: application
-version: 0.1.2
+version: 0.1.3
 appVersion: 4.8.78
 #
 description: An EOS QDB chart
 icon: https://eos-web.web.cern.ch/eos-web/assets/images/eos-icon-white-713x824.png
 dependencies:
 - name: utils
-  version: 0.1.5
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"
diff --git a/qdb/README.md b/qdb/README.md
@@ -2,15 +2,15 @@
 
 An EOS QDB chart
 
-![Version: 0.1.2](https://img.shields.io/badge/Version-0.1.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
+![Version: 0.1.3](https://img.shields.io/badge/Version-0.1.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.8.78](https://img.shields.io/badge/AppVersion-4.8.78-informational?style=flat-square)
 
 Helm Chart to deploy Quark DB.
 
 ## Requirements
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.5 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ## Values
 

diff --git a/server/Chart.yaml b/server/Chart.yaml
@@ -10,18 +10,18 @@ icon: https://eos-web.web.cern.ch/eos-web/assets/images/eos-icon-white-713x824.p
 #
 dependencies:
   - name: qdb
-    version: 0.1.2
-    repository: "https://registry.cern.ch/chartrepo/eos"
+    version: 0.1.3
+    repository: "oci://registry.cern.ch/eos/charts"
   - name: mgm
-    version: 0.1.6
-    repository: "https://registry.cern.ch/chartrepo/eos"
+    version: 0.1.7
+    repository: "oci://registry.cern.ch/eos/charts"
   - name: mq
-    version: 0.1.2
-    repository: "https://registry.cern.ch/chartrepo/eos"
+    version: 0.1.3
+    repository: "oci://registry.cern.ch/eos/charts"
     condition: global.splitMgmMq
   - name: fst
-    version: 0.1.3
-    repository: "https://registry.cern.ch/chartrepo/eos"
-  - name: utils
     version: 0.1.5
-    repository: "https://registry.cern.ch/chartrepo/eos"
+    repository: "oci://registry.cern.ch/eos/charts"
+  - name: utils
+    version: 0.1.7
+    repository: "oci://registry.cern.ch/eos/charts"
diff --git a/server/README.md b/server/README.md
@@ -1,19 +1,19 @@
 
 # server
 
-A fully-fledge EOS server instance with qdb, mgm, mq, and fst
+A fully-fledged EOS server instance with qdb, mgm, mq, and fst
 
-![Version: 0.1.7](https://img.shields.io/badge/Version-0.1.7-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 5.0.31](https://img.shields.io/badge/AppVersion-5.0.31-informational?style=flat-square)
+![Version: 0.1.8](https://img.shields.io/badge/Version-0.1.8-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 5.0.31](https://img.shields.io/badge/AppVersion-5.0.31-informational?style=flat-square)
 
 ## Requirements
 
 | Repository | Name | Version |
 |------------|------|---------|
-| file://../fst | fst | 0.1.4 |
-| file://../mgm | mgm | 0.1.7 |
-| https://registry.cern.ch/chartrepo/eos | mq | 0.1.2 |
-| https://registry.cern.ch/chartrepo/eos | qdb | 0.1.2 |
-| https://registry.cern.ch/chartrepo/eos | utils | 0.1.5 |
+| oci://registry.cern.ch/eos/charts | fst | 0.1.5 |
+| oci://registry.cern.ch/eos/charts | mgm | 0.1.7 |
+| oci://registry.cern.ch/eos/charts | mq | 0.1.3 |
+| oci://registry.cern.ch/eos/charts | qdb | 0.1.3 |
+| oci://registry.cern.ch/eos/charts | utils | 0.1.7 |
 
 ----------------------------------------------
 Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0)
diff --git a/sps/Chart.yaml b/sps/Chart.yaml
@@ -9,5 +9,5 @@ description: An XRootD Standard Proxy Service chart
 icon: https://xrootd.slac.stanford.edu/doc/dev51/pss_config_files/image001.gif
 dependencies:
 - name: utils
-  version: 0.1.5
-  repository: "https://registry.cern.ch/chartrepo/eos"
+  version: 0.1.7
+  repository: "oci://registry.cern.ch/eos/charts"