Skip to content

Latest commit

 

History

History
30 lines (25 loc) · 1.34 KB

long-term-storage-hitachi.md

File metadata and controls

30 lines (25 loc) · 1.34 KB

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, it can be used as a drop-in replacement for S3.

To obtain the necessary S3 User Credentials, see Hitachi's documentation.

Now create a .YAML file named federated-store.yaml with the following format:

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: "<HITACHI_ACCESS_KEY>"
  secret_key: "<HITACHI_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").