Skip to content

Commit

Permalink
Spellcheck and grammar check
Browse files Browse the repository at this point in the history
  • Loading branch information
janekbaraniewski committed Aug 5, 2024
1 parent c9467f8 commit a443321
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 14 deletions.
16 changes: 8 additions & 8 deletions vcluster/integrations/pod-identity/eks-pod-identity.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,25 +23,25 @@ import ProAdmonition from '@site/vcluster/_partials/admonitions/pro-admonition.m

This tutorial guides you through the process of integrating AWS Service Accounts with your vCluster using Pod Identity.

Settiing up Pod Identity requires you to link a AWS Service Account with Kubernetes Service Account (KSA) used by your workloads.
Setting up Pod Identity requires you to link an AWS Service Account with the Kubernetes Service Account (KSA) used by your workloads.
This KSA needs to be available in the host cluster in which your vCluster instance runs.

To obtain this setup, we'll need to use [sync.toHost feature][sync-toHost-docs] in order to expose KSA in the host cluster together with vCluster Platform API to retrieve updated name of KSA in the host cluster.
To achieve this setup, we'll need to use the [sync.toHost feature][sync-toHost-docs] in order to expose the KSA in the host cluster together with the vCluster Platform API to retrieve the updated name of the KSA in the host cluster.

### Prerequisites
This guide assumes you have the following prerequisites:
- `kubectl` installed
- `aws` CLI installed and configured
- An existing EKS cluster with CSI driver set up, IAM OIDC provider and Pod Identity agent deployed
- An existing EKS cluster with the CSI driver set up, IAM OIDC provider, and Pod Identity agent deployed

### Step-by-Step Guide

#### 1. Start vCluster Platform and create access key
#### 1. Start vCluster Platform and create an access key

In order to integrate your workloads with EKS Pod Identity you'll need vCluster Platform instance running.
If you don't have one already, follow [vCluster Platform installation guide][vcluster-platform-install-link].
In order to integrate your workloads with EKS Pod Identity, you'll need a vCluster Platform instance running.
If you don't have one already, follow the [vCluster Platform installation guide][vcluster-platform-install-link].

Once you're done, you'll need to create a new access key. This will allow you to use vCluster Platform API.
Once you're done, you'll need to create a new access key. This will allow you to use the vCluster Platform API.
Please follow this [guide to create a new access key][access-key-link].


Expand Down Expand Up @@ -127,7 +127,7 @@ sync:
#### 5. Connect to vCluster
Establish a connection your vCluster instance:
Establish a connection to your vCluster instance:
```bash
vcluster connect ${VCLUSTER_NAME}
Expand Down
12 changes: 6 additions & 6 deletions vcluster/integrations/pod-identity/gke-workload-identity.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,10 @@ import GKEWorkloadIdentityTestDeployment from '!!raw-loader!@site/vcluster/integ

This tutorial guides you through the process of integrating GCP Service Accounts with your vCluster using Workload Identity.

Settiing up Workload Identity requires you to link a GCP Service Account with Kubernetes Service Account (KSA) used by your workloads.
Setting up Workload Identity requires you to link a GCP Service Account with the Kubernetes Service Account (KSA) used by your workloads.
This KSA needs to be available in the host cluster in which your vCluster instance runs.

To obtain this setup, we'll need to use [sync.toHost feature][sync-toHost-docs] in order to expose KSA in the host cluster together with vCluster Platform API to retrieve updated name of KSA in the host cluster.
To achieve this setup, we'll need to use the [sync.toHost feature][sync-toHost-docs] in order to expose the KSA in the host cluster together with the vCluster Platform API to retrieve the updated name of the KSA in the host cluster.

### Prerequisites
This guide assumes you have the following prerequisites:
Expand All @@ -34,10 +34,10 @@ This guide assumes you have the following prerequisites:

#### 1. Start vCluster Platform and create access key

In order to integrate your workloads with GKE Workload Identity you'll need vCluster Platform instance running.
If you don't have one already, follow [vCluster Platform installation guide][vcluster-platform-install-link].
In order to integrate your workloads with GKE Workload Identity, you'll need a vCluster Platform instance running.
If you don't have one already, follow the [vCluster Platform installation guide][vcluster-platform-install-link].

Once you're done, you'll need to create a new access key. This will allow you to use vCluster Platform API.
Once you're done, you'll need to create a new access key. This will allow you to use the vCluster Platform API.
Please follow this [guide to create a new access key][access-key-link].

#### 2. Set Up Environment Variables
Expand Down Expand Up @@ -78,7 +78,7 @@ sync:
#### 6. Connect to vCluster
Establish a connection your vCluster instance:
Establish a connection to your vCluster instance:
```bash
vcluster connect ${VCLUSTER_NAME}
Expand Down

0 comments on commit a443321

Please sign in to comment.