Merge branch 'main' into piraeus-2.8.1

Author: vishwanaths

.github/workflows/bulwark-gitleaks-pr-validation.yaml

@@ -28,7 +28,7 @@ jobs:
         if: github.event.pull_request.head.repo.full_name != github.repository
         shell: sh
         run: |
-          git clone https://github.com/${{ github.event.pull_request.head.repo.full_name }}.git -b ${BRANCH}
+          git clone https://github.com/${{ github.event.pull_request.head.repo.full_name }}.git -b ${BRANCH} ${REPO}
           cd ${REPO}
           git remote add scRepo https://github.com/${{ github.repository }}.git
           git fetch scRepo
@@ -45,4 +45,4 @@ jobs:
             exit 1
           else 
             echo "GitLeaks validation check passed"
-          fi
+          fi

packs/cloudcasa-3.1.0/README.md

@@ -0,0 +1,53 @@
+# CloudCasa Kubernetes Agent
+
+[CloudCasa](https://cloudcasa.io) - Leader in Kubernetes Data Protection and Application Mobility
+
+CloudCasa is a SaaS data protection, disaster recovery, migration, and replication solution for Kubernetes and cloud-native applications.
+Configuration is quick and easy, and basic service is free.
+
+This pack installs and configures the CloudCasa agent on a Kubernetes cluster.
+
+## Prerequisites
+
+- Kubernetes 1.20 or above
+- A CloudCasa account. You can [sign up](https://signup.cloudcasa.io/) for free.
+- A CloudCasa **Cluster ID** (see below)
+
+## Parameters
+
+To deploy the CloudCasa agent, you **must** set the `clusterID` parameter to the Cluster ID provided by CloudCasa.
+All other parameters are optional or can be left at their default values.
+
+| Key                              | Type   | Default                                     | Required |
+|---                               |---     |---                                          |---       |
+| clusterID                        | string | `""`                                        | Yes      |
+| image.repository                 | string | `"docker.io/catalogicsoftware/amds-kagent"` | Yes      |
+| image.tag                        | string | `"3.1.0-prod"`                              | Yes      |
+| imagePullSecret                  | string | `null`                                      | No       |
+
+## Usage
+
+1. Log in to https://home.cloudcasa.io and add your Kubernetes cluster under Clusters/Overview. Note the returned cluster ID.
+2. Install the pack, setting the `clusterID` parameter to the returned ID.
+
+This will install the CloudCasa agent and complete registration of the cluster with the CloudCasa service.
+
+### Using an alternate image repository
+
+The agent manager container can be installed from an alternate repository by setting values for image.repository and image.tag.
+Note that the alternate repository will also need to be set for the cluster in CloudCasa so that all agent containers will be loaded from it.
+See the [CloudCasa User Guide](https://docs.cloudcasa.io/help/cluster-add.html) for more information.
+
+If the registry you are using requires authentication, you can define a Kubernetes secret with the authentication information
+and reference it by setting a value for imagePullSecret.
+See the [Kubernetes Docs](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for more information.
+Note that the secret name will also need to be set for the cluster in CloudCasa so that it will be used for all agent containers.
+See the [CloudCasa User Guide](https://docs.cloudcasa.io/help/cluster-add.html) for more information.
+
+## References
+
+- The CloudCasa Website: [https://cloudcasa.io](https://cloudcasa.io/)
+- The CloudCasa [User Guide](https://docs.cloudcasa.io/help/)
+- The CloudCasa [Getting Started Guide](https://cloudcasa.io/get-started)
+
+*CloudCasa is a trademark of Catalogic Software, Inc.*

packs/cloudcasa-3.1.0/charts/cloudcasa-3.4.4.tgz

@@ -0,0 +1,13 @@
+{
+  "name": "cloudcasa",
+  "version": "3.1.0",
+  "displayName": "CloudCasa Kubernetes Agent",
+  "annotations": {
+    "source": "community",
+    "contributor" : "catalogic"
+  },
+  "layer": "addon",
+  "addonType": "system app",
+  "cloudTypes": [ "all" ],
+  "charts": [ "charts/cloudcasa-3.4.4.tgz" ]
+}

packs/cloudcasa-3.1.0/logo.png

@@ -0,0 +1,21 @@
+pack:
+  # The namespace (on the target cluster) in which the pack will be deployed.
+  # When the namespace is not found, a new namespace will be created with the name specified.
+  # Note this namespace MUST NOT BE CHANGED from "cloudcasa-io".
+  namespace: "cloudcasa-io"
+  content:
+    images:
+      - image: docker.io/catalogicsoftware/amds-kagent:3.1.0-prod
+
+charts:
+  cloudcasa:
+    # clusterID is the CloudCasa Cluster ID. To be provided by the user.
+    clusterID: ""
+
+    # image is the container repository and tag for the agent manager
+    image:
+      repository: "docker.io/catalogicsoftware/amds-kagent"
+      tag: "3.1.0-prod"
+
+    # imagePullSecret is the name of the secret to use for image registry credentials (optional)
+    imagePullSecret:

packs/cloudcasa-3.1.0/pack.json

@@ -0,0 +1,85 @@
+# Hitachi Storage Plug-in for Containers
+
+Hitachi Storage Plug-in for Containers lets you create containers and run stateful applications
+inside those containers by using the Hitachi storage volumes as dynamically provisioned
+persistent volumes.
+
+
+## Prerequisites
+
+- A Hitachi Virtual Storage Platform (VSP) array.
+
+
+## Parameters
+
+To deploy the Hitachi HSPC pack, you need to set, at minimum, the following parameters in the pack's YAML.
+
+| Name | Description | Type | Default Value | Required |
+| --- | --- | --- | --- | --- |
+| `hspc.vsp.url` | The URL of your Hitachi VSP management endpoint. | String  | - | Yes |
+| `hspc.vsp.user` | The username of a Hitachi VSP account with appropriate permissions. | String  | - | Yes |
+| `hspc.vsp.password` | The password of a Hitachi VSP account with appropriate permissions. | String  | - | Yes |
+| `hspc.storageClass.parameters.serialNumber` | The serial number of the VSP storage chassis. | String  | - | Yes |
+| `hspc.storageClass.parameters.poolID` | The HDP Pool ID (omit for VSP One SDS Block). | String  | - | Yes |
+| `hspc.storageClass.parameters.portID` | The port ID (omit for VSP One SDS Block). Use a comma separator for multipath. If an NVMe over FC is used, don't set this option. | String  | - | Yes |
+| `hspc.storageClass.parameters.connectionType` | Storage connection type. fc, iscsi, and nvme-fc are supported. Defaults to fc if not set. | String  | fc | No |
+| `hspc.storageClass.parameters.storageEfficiency` | Adaptive data reduction. "Compression", "CompressionDeduplication", and "Disabled" are supported. | String  | - | Yes |
+| `hspc.storageClass.parameters.storageEfficiencyMode` | Compression execution mode. "Inline" and "PostProcess" are supported. | String  | - | No |
+| `hspc.storageClass.parameters.storageType` | For VSP One SDS Block, set the "storagetype" parameter to "vsp-one-sds-block". | String  | - | No |
+| `hspc.storageClass.parameters.csi.storage.k8s.io/fstype` | Filesystem type, ext4 and xfs are supported. Defaults to ext4 if not set. | String  | ext4 | No |
+
+
+Review the [Hitachi Storage Plug-in for Containers Quick Reference Guide](https://docs.hitachivantara.com/v/u/en-us/adapters-and-drivers/3.15.x/mk-92adptr142) for more details on parameters. 
+
+## Upgrade
+
+This pack deploys an operator, which takes care of phased upgrades
+
+
+## Usage
+
+To use the Hitachi Storage Plug-in for Containers pack, first create a new [infrastructure cluster profile](https://docs.spectrocloud.com/profiles/cluster-profiles/create-cluster-profiles/create-infrastructure-profile/), select MAAS for the Infrastructure Provider and when you get to the Storage pack, search for the **Hitachi Storage Plug-in for Containers** pack in the Palete Community Registry. Then configure the `hspc.vsp` and `hspc.storageClass` sections in the pack YAML:
+
+```yaml
+charts:  
+  hspc:
+    ...
+    vsp:
+      url: http://172.16.1.1
+      user: "User01"
+      password: "*******"
+    storageClass:
+      name: spectro-storage-class
+      isDefaultStorageClass: true
+      allowVolumeExpansion: true
+      reclaimPolicy: Delete
+      volumeBindingMode: Immediate
+      parameters:
+        serialNumber: "54321"
+        poolID: "1"
+        portID : CL1-A,CL2-A
+        connectionType: fc
+        storageEfficiency: "CompressionDeduplication"
+        storageEfficiencyMode: "Inline"
+```
+
+Once you have confiogured the pack, you can deploy a cluster with it.
+
+In order to use this CSI for snapshots, the following `VolumeSnapshotClass` can be created (manually, not part of this pack):
+```
+apiVersion: snapshot.storage.k8s.io/v1
+kind: VolumeSnapshotClass
+metadata:
+  name: hspc-snapshotclass
+driver: hspc.csi.hitachi.com
+deletionPolicy: Delete
+parameters:
+  poolID: "1"
+  csi.storage.k8s.io/snapshotter-secret-name: "hspc-secret"
+  csi.storage.k8s.io/snapshotter-secret-namespace: "hspc-system"
+```
+
+## References
+
+- [Hitachi Vantara website](https://www.hitachivantara.com/)
+- [Hitachi HSPC Quick Reference Guide](https://docs.hitachivantara.com/v/u/en-us/adapters-and-drivers/3.15.x/mk-92adptr142)

packs/cloudcasa-3.1.0/values.yaml

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

packs/hitachi-hspc-3.15.0/README.md

@@ -0,0 +1,23 @@
+apiVersion: v2
+name: hspc
+description: Installs Hitachi Storage Plug-in for Containers
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 3.15.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: "3.15.0"