From 7b19ff1b3dbaf6049da4b9a7979c052c427f4606 Mon Sep 17 00:00:00 2001 From: Kyriakos Akriotis Date: Fri, 24 Jul 2026 04:35:56 +0000 Subject: [PATCH 1/3] fix the adopters button text #66 --- src/pages/index.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/index.tsx b/src/pages/index.tsx index 5b838b1..6a6ca85 100644 --- a/src/pages/index.tsx +++ b/src/pages/index.tsx @@ -240,7 +240,7 @@ function HomepageCta(): JSX.Element { className="button button--tertiary button--lg" to="/docs/adopters" > - Already running TyKO? Join the Adopters + Join the Adopters From f82d869692e5cb5bb162050897de6cabc8fcfae2 Mon Sep 17 00:00:00 2001 From: Kyriakos Akriotis Date: Fri, 24 Jul 2026 04:48:49 +0000 Subject: [PATCH 2/3] added aksk secret for sfs obs in tabs #66 --- docs/crds/{examples.md => examples.mdx} | 112 ++++++++++++++++++------ 1 file changed, 84 insertions(+), 28 deletions(-) rename docs/crds/{examples.md => examples.mdx} (85%) diff --git a/docs/crds/examples.md b/docs/crds/examples.mdx similarity index 85% rename from docs/crds/examples.md rename to docs/crds/examples.mdx index 5334f51..1e18138 100644 --- a/docs/crds/examples.md +++ b/docs/crds/examples.mdx @@ -222,43 +222,99 @@ spec: This is by no means a production-ready Redis cluster nor a best-practice on how to deploy Redis on Kubernetes. It's just a quick spin of cluster in order to be able to work with JuiceFS. ::: -### T Cloud Public OBS +### T Cloud Public + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; If you are running on [T Cloud Public](https://www.open-telekom-cloud.com/en), you can take advantage of the additional annotations field `csi.storage.k8s.io/fstype` that controls how an S3 bucket is mounted into a Kubernetes pod. -- Using `csi.storage.k8s.io/fstype: s3fs` mounts an [SFS Turbo, Scalable File System](https://www.open-telekom-cloud.com/en/products-services/core-services/scalable-file-service) bucket using the S3-compatible API, -which is useful when you want simple “filesystem-like” access but are okay with object-storage semantics that may not fully match POSIX behavior. -- Using the annotation `csi.storage.k8s.io/fstype: obsfs` mounts the bucket using the native OBS filesystem driver and is generally the more “OBS-native” approach; -it avoids some S3FS-specific limitations and is often preferred when you want better integration with OBS. + + + Using the annotation `csi.storage.k8s.io/fstype: obsfs` mounts the bucket using the native OBS filesystem driver and is generally the more “OBS-native” approach; + it avoids some S3FS-specific limitations and is often preferred when you want better integration with OBS. + + ```yaml + apiVersion: v1 + kind: Secret + metadata: + name: otc-aksk + namespace: default + labels: + secret.kubernetes.io/used-by: csi + type: cfe/secure-opaque + data: + access.key: "" + secret.key: "" + --- + apiVersion: ts.opentelekomcloud.com/v1alpha1 + kind: TypesenseCluster + metadata: + labels: + app.kubernetes.io/name: typesense-operator + app.kubernetes.io/managed-by: kustomize + name: c-otc-2 + spec: + image: typesense/typesense:29.0 + replicas: 3 + storage: + storageClassName: csi-obs + accessMode: ReadWriteMany + annotations: + csi.storage.k8s.io/fstype: obsfs + volume.beta.kubernetes.io/storage-provisioner: everest-csi-provisioner + csi.storage.k8s.io/node-publish-secret-name: otc-aksk + csi.storage.k8s.io/node-publish-secret-namespace: default + everest.io/csi.volume-name-prefix: c-otc-2 + ``` + + + Using `csi.storage.k8s.io/fstype: s3fs` mounts an [SFS Turbo, Scalable File System](https://www.open-telekom-cloud.com/en/products-services/core-services/scalable-file-service) bucket using the S3-compatible API, + which is useful when you want simple “filesystem-like” access but are okay with object-storage semantics that may not fully match POSIX behavior. + + ```yaml + apiVersion: v1 + kind: Secret + metadata: + name: otc-aksk + namespace: default + labels: + secret.kubernetes.io/used-by: csi + type: cfe/secure-opaque + data: + access.key: "" + secret.key: "" + --- + apiVersion: ts.opentelekomcloud.com/v1alpha1 + kind: TypesenseCluster + metadata: + labels: + app.kubernetes.io/name: typesense-operator + app.kubernetes.io/managed-by: kustomize + name: c-otc-3 + spec: + image: typesense/typesense:29.0 + replicas: 3 + storage: + storageClassName: csi-obs + accessMode: ReadWriteMany + annotations: + everest.io/obs-volume-type: STANDARD + csi.storage.k8s.io/fstype: s3fs + volume.beta.kubernetes.io/storage-provisioner: everest-csi-provisioner + csi.storage.k8s.io/node-publish-secret-name: otc-aksk + csi.storage.k8s.io/node-publish-secret-namespace: default + everest.io/csi.volume-name-prefix: c-otc-3 + ``` + + -```yaml -apiVersion: ts.opentelekomcloud.com/v1alpha1 -kind: TypesenseCluster -metadata: - labels: - app.kubernetes.io/name: typesense-operator - app.kubernetes.io/managed-by: kustomize - name: c-otc-3 -spec: - image: typesense/typesense:29.0 - replicas: 3 - storage: - storageClassName: csi-obs - accessMode: ReadWriteMany - annotations: - everest.io/obs-volume-type: STANDARD - csi.storage.k8s.io/fstype: s3fs - volume.beta.kubernetes.io/storage-provisioner: everest-csi-provisioner - csi.storage.k8s.io/node-publish-secret-name: otc-aksk - csi.storage.k8s.io/node-publish-secret-namespace: default - everest.io/csi.volume-name-prefix: c-otc-3 -``` :::note One big advantage of using these annotations is that the respective S3 buckets will be provisioned dynamically by the CSI itself. -For more information about configuring T Cloud Public `StorageClass` consult +For more information about configuring a T Cloud Public `StorageClass` consult the [official documentation](https://docs.otc.t-systems.com/cloud-container-engine/umn/storage/storageclass.html). ::: From 38698c9fbefe79dac161939c2b2af185374362d8 Mon Sep 17 00:00:00 2001 From: Kyriakos Akriotis Date: Fri, 24 Jul 2026 04:59:05 +0000 Subject: [PATCH 3/3] fixed broken links #66 --- docs/crds/examples.mdx | 4 ++-- docs/crds/index.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/crds/examples.mdx b/docs/crds/examples.mdx index 1e18138..90c9a69 100644 --- a/docs/crds/examples.mdx +++ b/docs/crds/examples.mdx @@ -222,12 +222,12 @@ spec: This is by no means a production-ready Redis cluster nor a best-practice on how to deploy Redis on Kubernetes. It's just a quick spin of cluster in order to be able to work with JuiceFS. ::: -### T Cloud Public +### T Cloud Public import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -If you are running on [T Cloud Public](https://www.open-telekom-cloud.com/en), you can take advantage of the additional annotations field `csi.storage.k8s.io/fstype` +If you are running on [T Cloud Public (fka Open Telekom Cloud)](https://www.open-telekom-cloud.com/en), you can take advantage of the additional annotations field `csi.storage.k8s.io/fstype` that controls how an S3 bucket is mounted into a Kubernetes pod. diff --git a/docs/crds/index.mdx b/docs/crds/index.mdx index 20cec67..1c1cccc 100644 --- a/docs/crds/index.mdx +++ b/docs/crds/index.mdx @@ -111,7 +111,7 @@ with the `juicefs-csi-driver` to mount S3 buckets as persistent volumes in pods * If you run on-premises clusters or in any cloud provider, you can now attach any remote S3-compatible storage (e.g., AWS S3, Azure Blob Storage etc.), using `accessMode: ReadWriteMany` together with the `juicefs-csi-driver` to mount S3 buckets as persistent volumes in pods as Typesense data volumes. -For more information about installing and configuring **JuiceFS** and **JuiceFS CSI Driver** for TyKO check the [examples](/docs/crds/examples.md#use-s3-compliant-storage-as-persistent-volumes). +For more information about installing and configuring **JuiceFS** and **JuiceFS CSI Driver** for TyKO check the [examples](/docs/crds/examples.mdx#use-s3-compliant-storage-as-persistent-volumes). :::