From b0764aa7dd9d4640f384b74d8a0423a1d3f3f01e Mon Sep 17 00:00:00 2001 From: Mads Emil <30866619+madsemildahlgaard@users.noreply.github.com> Date: Thu, 11 May 2023 03:14:07 +0200 Subject: [PATCH] Change presistent to persistent and delpoy to deploy (#11541) --- .../content/v0.13.2/deployment/kubernetes/eks.md | 2 +- .../content/v0.13.2/deployment/kubernetes/gke.md | 4 ++-- .../content/v0.13.2/deployment/kubernetes/on-prem.md | 4 ++-- .../content/v0.13.3/deployment/kubernetes/eks.md | 2 +- .../content/v0.13.3/deployment/kubernetes/gke.md | 4 ++-- .../content/v0.13.3/deployment/kubernetes/on-prem.md | 4 ++-- .../content/v1.0.0/deployment/kubernetes/eks.md | 2 +- .../content/v1.0.0/deployment/kubernetes/gke.md | 4 ++-- .../content/v1.0.0/deployment/kubernetes/on-prem.md | 4 ++-- openmetadata-docs/content/deployment/kubernetes/eks.md | 2 +- openmetadata-docs/content/deployment/kubernetes/gke.md | 4 ++-- openmetadata-docs/content/deployment/kubernetes/on-prem.md | 4 ++-- 12 files changed, 20 insertions(+), 20 deletions(-) diff --git a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/eks.md b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/eks.md index 36be32a18d1..9509d7aaf23 100644 --- a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/eks.md +++ b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/eks.md @@ -23,7 +23,7 @@ You can follow official AWS Guides [here](https://docs.aws.amazon.com/efs/latest ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). In AWS, this is achieved by Elastic File System (EFS) service. AWS Elastic Block Store (EBS) does not provide ReadWriteMany Volume access mode as EBS will only be attached to one Kubernetes Node at any given point of time. diff --git a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/gke.md b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/gke.md index d76aa662708..8f5b4f010a6 100644 --- a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/gke.md +++ b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/gke.md @@ -25,9 +25,9 @@ All the code snippets in this section assume the `default` namespace for kuberne ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the presistent claim and delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the persistent claim and deploy OpenMetadata by implementing the following steps in order. ## Create NFS Share diff --git a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/on-prem.md b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/on-prem.md index 2a65befad2e..e4fc2b5a1c1 100644 --- a/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/on-prem.md +++ b/openmetadata-docs-v1/content/v0.13.2/deployment/kubernetes/on-prem.md @@ -18,9 +18,9 @@ This guide presumes you have an on premises Kubernetes cluster setup and you are ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-share and use that as the presistent claim to delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-share and use that as the persistent claim to deploy OpenMetadata by implementing the following steps in order. {% note %} diff --git a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/eks.md b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/eks.md index 36be32a18d1..9509d7aaf23 100644 --- a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/eks.md +++ b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/eks.md @@ -23,7 +23,7 @@ You can follow official AWS Guides [here](https://docs.aws.amazon.com/efs/latest ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). In AWS, this is achieved by Elastic File System (EFS) service. AWS Elastic Block Store (EBS) does not provide ReadWriteMany Volume access mode as EBS will only be attached to one Kubernetes Node at any given point of time. diff --git a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/gke.md b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/gke.md index d76aa662708..8f5b4f010a6 100644 --- a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/gke.md +++ b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/gke.md @@ -25,9 +25,9 @@ All the code snippets in this section assume the `default` namespace for kuberne ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the presistent claim and delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the persistent claim and deploy OpenMetadata by implementing the following steps in order. ## Create NFS Share diff --git a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/on-prem.md b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/on-prem.md index 2a65befad2e..e4fc2b5a1c1 100644 --- a/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/on-prem.md +++ b/openmetadata-docs-v1/content/v0.13.3/deployment/kubernetes/on-prem.md @@ -18,9 +18,9 @@ This guide presumes you have an on premises Kubernetes cluster setup and you are ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-share and use that as the presistent claim to delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-share and use that as the persistent claim to deploy OpenMetadata by implementing the following steps in order. {% note %} diff --git a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/eks.md b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/eks.md index 22023367034..382ac0ff888 100644 --- a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/eks.md +++ b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/eks.md @@ -23,7 +23,7 @@ You can follow official AWS Guides [here](https://docs.aws.amazon.com/efs/latest ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). In AWS, this is achieved by Elastic File System (EFS) service. AWS Elastic Block Store (EBS) does not provide ReadWriteMany Volume access mode as EBS will only be attached to one Kubernetes Node at any given point of time. diff --git a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/gke.md b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/gke.md index 0fcedfe9a0e..d156842d32f 100644 --- a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/gke.md +++ b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/gke.md @@ -25,9 +25,9 @@ All the code snippets in this section assume the `default` namespace for kuberne ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the presistent claim and delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the persistent claim and deploy OpenMetadata by implementing the following steps in order. ## Create NFS Share diff --git a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/on-prem.md b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/on-prem.md index 49cf7e1dbf4..fc99ad0b613 100644 --- a/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/on-prem.md +++ b/openmetadata-docs-v1/content/v1.0.0/deployment/kubernetes/on-prem.md @@ -18,9 +18,9 @@ This guide presumes you have an on premises Kubernetes cluster setup and you are ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-share and use that as the presistent claim to delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-share and use that as the persistent claim to deploy OpenMetadata by implementing the following steps in order. {%note%} diff --git a/openmetadata-docs/content/deployment/kubernetes/eks.md b/openmetadata-docs/content/deployment/kubernetes/eks.md index 426ef4e0bf5..77742a69155 100644 --- a/openmetadata-docs/content/deployment/kubernetes/eks.md +++ b/openmetadata-docs/content/deployment/kubernetes/eks.md @@ -23,7 +23,7 @@ You can follow official AWS Guides [here](https://docs.aws.amazon.com/efs/latest ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). In AWS, this is achieved by Elastic File System (EFS) service. AWS Elastic Block Store (EBS) does not provide ReadWriteMany Volume access mode as EBS will only be attached to one Kubernetes Node at any given point of time. diff --git a/openmetadata-docs/content/deployment/kubernetes/gke.md b/openmetadata-docs/content/deployment/kubernetes/gke.md index 939231fb0af..c0f23d44562 100644 --- a/openmetadata-docs/content/deployment/kubernetes/gke.md +++ b/openmetadata-docs/content/deployment/kubernetes/gke.md @@ -25,9 +25,9 @@ All the code snippets in this section assume the `default` namespace for kuberne ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the presistent claim and delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-server disk on Google Kubernetes Engine and use that as the persistent claim and deploy OpenMetadata by implementing the following steps in order. ## Create NFS Share diff --git a/openmetadata-docs/content/deployment/kubernetes/on-prem.md b/openmetadata-docs/content/deployment/kubernetes/on-prem.md index 48d012bda82..66f08924f07 100644 --- a/openmetadata-docs/content/deployment/kubernetes/on-prem.md +++ b/openmetadata-docs/content/deployment/kubernetes/on-prem.md @@ -18,9 +18,9 @@ This guide presumes you have an on premises Kubernetes cluster setup and you are ### Persistent Volumes with ReadWriteMany Access Modes -OpenMetadata helm chart depends on Airflow and Airflow expects a presistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). +OpenMetadata helm chart depends on Airflow and Airflow expects a persistent disk that support ReadWriteMany (the volume can be mounted as read-write by many nodes). -The workaround is to create nfs-share and use that as the presistent claim to delpoy OpenMetadata by implementing the following steps in order. +The workaround is to create nfs-share and use that as the persistent claim to deploy OpenMetadata by implementing the following steps in order.