From 93f8360966875fe7c02768b5aaf5906980be4859 Mon Sep 17 00:00:00 2001 From: Sean Pomeroy Date: Fri, 4 Oct 2024 15:23:09 -0400 Subject: [PATCH 1/3] ARM updates Signed-off-by: Sean Pomeroy --- .../long-term-storage-configuration/long-term-storage-azure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md index c2397a397..1e372a5b4 100644 --- a/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md +++ b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md @@ -4,7 +4,7 @@ Usage of a Federated Storage Bucket is only supported for Kubecost Enterprise plans. {% endhint %} -To use Azure Storage as Thanos object store, you need to precreate a storage account from Azure portal or using Azure CLI. Follow the instructions from the [Azure Storage Documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-quickstart-create-account). +To use Azure Storage as an ETL object store, you need to pre-create a storage account from Azure the portal or using the Azure CLI. Follow the instructions from the [Azure Storage Documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-quickstart-create-account). Now create a .YAML file named `federated-store.yaml` with the following format: From cd51d3e7341b3fdc4c7d1f79a9fc31eff666d399 Mon Sep 17 00:00:00 2001 From: Sean Pomeroy Date: Fri, 4 Oct 2024 15:26:53 -0400 Subject: [PATCH 2/3] add back hitachi storage Signed-off-by: Sean Pomeroy --- SUMMARY.md | 1 + .../long-term-storage-hitachi.md | 30 +++++++++++++++++++ 2 files changed, 31 insertions(+) create mode 100644 install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md diff --git a/SUMMARY.md b/SUMMARY.md index 03f888459..9a74739b6 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -45,6 +45,7 @@ * [AWS Multi-Cluster Storage Configuration](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-aws.md) * [Azure Long-Term Storage](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md) * [GCP Long-Term Storage](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-gcp.md) + * [Hitachi Content Platform (HCP) Storage Configuration](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md) * [Secondary Clusters Guide](install-and-configure/install/multi-cluster/secondary-clusters.md) * [Multi-Cluster Diagnostics](install-and-configure/install/multi-cluster/multi-cluster-diagnostics.md) * [Additional Configuration](install-and-configure/advanced-configuration/README.md) diff --git a/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md new file mode 100644 index 000000000..5113a4ef9 --- /dev/null +++ b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md @@ -0,0 +1,30 @@ +# Hitachi Content Platform (HCP) Multi-Cluster Storage Configuration + +{% hint style="info" %} +Usage of a Federated Storage Bucket is only supported for Kubecost Enterprise plans. +{% endhint %} + +Because HCP is [S3 compatible](https://knowledge.hitachivantara.com/Documents/Storage/HCP\_for\_Cloud\_Scale/1.0.0/Adminstering\_HCP\_for\_cloud\_scale/Getting\_started/02\_Support\_for\_Amazon\_S3\_API), it can be used as a drop-in replacement for S3. + +To obtain the necessary S3 User Credentials, see [Hitachi's documentation](https://knowledge.hitachivantara.com/Documents/Storage/HCP\_for\_Cloud\_Scale/1.0.0/Adminstering\_HCP\_for\_cloud\_scale/Object\_storage\_management/01\_S3\_User\_Credentials#GUID-6DA3811F-FBC5-4848-B47D-B2297F0902B7). + +Now create a .YAML file named `federated-store.yaml` with the following format: + +```yaml +type: S3 +config: + bucket: "folder name" # Folder created in the HCP endpoint bucket, not the pre-existing bucket name. + endpoint: "your.hcp-endpoint.com" + access_key: "" + secret_key: "" + insecure: false + signature_version2: false + http_config: + idle_conn_timeout: 90s + response_header_timeout: 2m + insecure_skip_verify: false + trace: + enable: true + part_size: 134217728 +prefix: "" # Optional. Specify a path within the bucket (e.g. "kubecost/etl"). +``` From 61b762ed801021f22f519183b15e51b71e1970a4 Mon Sep 17 00:00:00 2001 From: Sean Pomeroy Date: Fri, 4 Oct 2024 15:28:03 -0400 Subject: [PATCH 3/3] add back Storj storage Signed-off-by: Sean Pomeroy --- SUMMARY.md | 1 + .../long-term-storage-storj.md | 28 +++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-storj.md diff --git a/SUMMARY.md b/SUMMARY.md index 9a74739b6..00485ab06 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -46,6 +46,7 @@ * [Azure Long-Term Storage](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-azure.md) * [GCP Long-Term Storage](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-gcp.md) * [Hitachi Content Platform (HCP) Storage Configuration](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-hitachi.md) + * [Storj Storage Configuration](install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-storj.md) * [Secondary Clusters Guide](install-and-configure/install/multi-cluster/secondary-clusters.md) * [Multi-Cluster Diagnostics](install-and-configure/install/multi-cluster/multi-cluster-diagnostics.md) * [Additional Configuration](install-and-configure/advanced-configuration/README.md) diff --git a/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-storj.md b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-storj.md new file mode 100644 index 000000000..e9f692c3a --- /dev/null +++ b/install-and-configure/install/multi-cluster/long-term-storage-configuration/long-term-storage-storj.md @@ -0,0 +1,28 @@ +# Storj Multi-Cluster Storage Configuration + +{% hint style="info" %} +Usage of a Federated Storage Bucket is only supported for Kubecost Enterprise plans. +{% endhint %} + +Because Storj is [S3 compatible](https://docs.storj.io/dcs/api-reference/s3-compatible-gateway/), it can be used as a drop-in replacement for S3. + +After an S3 Compatible Access Grant has been created, create a .YAML file named `federated-store.yaml` with the following format: + +```yaml +type: S3 +config: + bucket: "my-bucket" + endpoint: "gateway.storjshare.io" + access_key: "" + secret_key: "" + insecure: false + signature_version2: false + http_config: + idle_conn_timeout: 90s + response_header_timeout: 2m + insecure_skip_verify: false + trace: + enable: true + part_size: 134217728 +prefix: "" # Optional. Specify a path within the bucket (e.g. "kubecost/etl"). +```