Skip to content

Instantly share code, notes, and snippets.

@arun-gupta

arun-gupta/readme.md

Last active September 5, 2024 01:24
Show Gist options
  • Save arun-gupta/fd3793baadc9feb4c3883c80b9481161 to your computer and use it in GitHub Desktop.
Save arun-gupta/fd3793baadc9feb4c3883c80b9481161 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. arun-gupta revised this gist Sep 5, 2024. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -95,9 +95,9 @@
    ```
    export HUGGINGFACEHUB_API_TOKEN="YourOwnToken"
    ```
    - Apply Helm chart:
    - Apply manifest:
    ```
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml | sed -e 's/mnt\/opea-models/tmp/g' | kubectl apply -f -
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml | sed -e 's/insert-your-huggingface-token-here/$HUGGINGFACEHUB_API_TOKEN/g' -e 's/mnt\/opea-models/tmp/g' | envsubst | kubectl apply -f -
    configmap/chatqna-data-prep-config created
    configmap/chatqna-embedding-usvc-config created
    configmap/chatqna-llm-uservice-config created
  2. arun-gupta revised this gist Sep 5, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    # OPEA on Amazon EKS

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. `m7i.4xlarge` is causing [this issue](https://repost.aws/questions/QUC5iSilyhRDS42QSlAPxqFQ/eks-cluster-with-m7i-4xlarge-instance-type-not-getting-create). Use this command instead to create the cluster:
    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. `m7i.4xlarge` and `m5.4xlarge` is causing [this issue](https://repost.aws/questions/QUC5iSilyhRDS42QSlAPxqFQ/eks-cluster-with-m7i-4xlarge-instance-type-not-getting-create). Use this command instead to create the cluster:
    ```
    export EKS_CLUSTER_NAME=eks-workshop
    #curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
  3. arun-gupta revised this gist Sep 5, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -97,7 +97,7 @@
    ```
    - Apply Helm chart:
    ```
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml | envsubst | kubectl apply -f -
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml | sed -e 's/mnt\/opea-models/tmp/g' | kubectl apply -f -
    configmap/chatqna-data-prep-config created
    configmap/chatqna-embedding-usvc-config created
    configmap/chatqna-llm-uservice-config created
  4. arun-gupta revised this gist Sep 5, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -7,7 +7,7 @@
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m5.4xlarge/g' | \
    envsubst | eksctl create cluster -f -
    ```
    This will create a one-node EKS cluster using `m7i.4xlarge` instance type. The default is 3-node cluster with `m5.large` instance type. Here is the final output:
    This will create a three-node EKS cluster using `m5.4xlarge` instead of the default `m5.large` instance type. Here is the final output:
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
  5. arun-gupta revised this gist Sep 5, 2024. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,10 +1,10 @@
    # OPEA on Amazon EKS

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Use this command instead to create the cluster:
    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. `m7i.4xlarge` is causing [this issue](https://repost.aws/questions/QUC5iSilyhRDS42QSlAPxqFQ/eks-cluster-with-m7i-4xlarge-instance-type-not-getting-create). Use this command instead to create the cluster:
    ```
    export EKS_CLUSTER_NAME=eks-workshop
    #curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' | \
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m5.4xlarge/g' | \
    envsubst | eksctl create cluster -f -
    ```
    This will create a one-node EKS cluster using `m7i.4xlarge` instance type. The default is 3-node cluster with `m5.large` instance type. Here is the final output:
  6. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,8 @@
    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Use this command instead to create the cluster:
    ```
    export EKS_CLUSTER_NAME=eks-workshop
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
    #curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' | \
    envsubst | eksctl create cluster -f -
    ```
    This will create a one-node EKS cluster using `m7i.4xlarge` instance type. The default is 3-node cluster with `m5.large` instance type. Here is the final output:
  7. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 2 additions and 7 deletions.
    9 changes: 2 additions & 7 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -90,18 +90,13 @@
    2024-09-04 01:02:36 [ℹ] kubectl command should work with "/home/ec2-user/.kube/config", try 'kubectl get nodes'
    2024-09-04 01:02:36 [✔] EKS cluster "eks-workshop" in "us-west-2" region is ready
    ```
    - Download Helm chart:
    ```
    curl -O https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml
    ```
    - Setup Hugging Face token:
    ```
    export HUGGINGFACEHUB_API_TOKEN="YourOwnToken"
    sed -i "s/insert-your-huggingface-token-here/${HUGGINGFACEHUB_API_TOKEN}/g" chatqna.yaml
    ```
    - Apply the Helm chart:
    - Apply Helm chart:
    ```
    ec2-user:~/environment:$ kubectl apply -f chatqna.yaml
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml | envsubst | kubectl apply -f -
    configmap/chatqna-data-prep-config created
    configmap/chatqna-embedding-usvc-config created
    configmap/chatqna-llm-uservice-config created
  8. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,7 +6,7 @@
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
    envsubst | eksctl create cluster -f -
    ```
    Here is the final output:
    This will create a one-node EKS cluster using `m7i.4xlarge` instance type. The default is 3-node cluster with `m5.large` instance type. Here is the final output:
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
  9. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 4 additions and 3 deletions.
    7 changes: 4 additions & 3 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,9 +1,10 @@
    # OPEA on Amazon EKS

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Run the following command before starting the cluster:
    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Use this command instead to create the cluster:
    ```
    sed -i "s/m5.large/m7i.4xlarge/g" chatqna.yaml
    sed -i "s/': 3'/': 1'/g" chatqna.yaml
    export EKS_CLUSTER_NAME=eks-workshop
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | sed -e 's/m5.large/m7i.4xlarge/g' -e 's/: 3/: 1/g' | \
    envsubst | eksctl create cluster -f -
    ```
    Here is the final output:
    ```
  10. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 6 additions and 1 deletion.
    7 changes: 6 additions & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,11 @@
    # OPEA on Amazon EKS

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Here is the final output:
    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Run the following command before starting the cluster:
    ```
    sed -i "s/m5.large/m7i.4xlarge/g" chatqna.yaml
    sed -i "s/': 3'/': 1'/g" chatqna.yaml
    ```
    Here is the final output:
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
  11. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -183,3 +183,5 @@
    ec2-user:~/environment:$ kubectl logs pod/chatqna-tgi-587b54f5ff-fcfqn
    Error from server (BadRequest): container "tgi" in pod "chatqna-tgi-587b54f5ff-fcfqn" is waiting to start: ContainerCreating
    ```
    Blocked on https://github.com/opea-project/GenAIExamples/issues/725
  12. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 58 additions and 1 deletion.
    59 changes: 58 additions & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -125,4 +125,61 @@
    deployment.apps/chatqna-tgi created
    deployment.apps/chatqna created
    ```
    -
    - Here is the log output:
    ```
    ec2-user:~/environment:$ kubectl get all
    NAME READY STATUS RESTARTS AGE
    pod/chatqna-79d8c5ffff-m2fb9 1/1 Running 0 8m29s
    pod/chatqna-data-prep-77dcc665f4-gjj7t 1/1 Running 0 8m30s
    pod/chatqna-embedding-usvc-55d4dc8f67-6qrln 1/1 Running 0 8m30s
    pod/chatqna-llm-uservice-66cc67785-vkpc9 1/1 Running 0 8m30s
    pod/chatqna-redis-vector-db-5dcd98f579-x7k9q 1/1 Running 0 8m30s
    pod/chatqna-reranking-usvc-759bf96c5c-fl6f8 1/1 Running 0 8m30s
    pod/chatqna-retriever-usvc-86f8dfbfb6-pfktk 1/1 Running 0 8m30s
    pod/chatqna-tei-565488dd9-p4cj7 0/1 ContainerCreating 0 8m30s
    pod/chatqna-teirerank-6c9854cfdf-mmgqh 0/1 ContainerCreating 0 8m30s
    pod/chatqna-tgi-587b54f5ff-fcfqn 0/1 ContainerCreating 0 8m29s
    NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
    service/chatqna ClusterIP 172.20.167.162 <none> 8888/TCP 8m30s
    service/chatqna-data-prep ClusterIP 172.20.240.173 <none> 6007/TCP 8m30s
    service/chatqna-embedding-usvc ClusterIP 172.20.194.245 <none> 6000/TCP 8m30s
    service/chatqna-llm-uservice ClusterIP 172.20.70.157 <none> 9000/TCP 8m30s
    service/chatqna-redis-vector-db ClusterIP 172.20.165.213 <none> 6379/TCP,8001/TCP 8m30s
    service/chatqna-reranking-usvc ClusterIP 172.20.112.188 <none> 8000/TCP 8m30s
    service/chatqna-retriever-usvc ClusterIP 172.20.204.167 <none> 7000/TCP 8m30s
    service/chatqna-tei ClusterIP 172.20.116.54 <none> 80/TCP 8m30s
    service/chatqna-teirerank ClusterIP 172.20.22.103 <none> 80/TCP 8m30s
    service/chatqna-tgi ClusterIP 172.20.10.36 <none> 80/TCP 8m30s
    service/kubernetes ClusterIP 172.20.0.1 <none> 443/TCP 24m
    NAME READY UP-TO-DATE AVAILABLE AGE
    deployment.apps/chatqna 1/1 1 1 8m30s
    deployment.apps/chatqna-data-prep 1/1 1 1 8m30s
    deployment.apps/chatqna-embedding-usvc 1/1 1 1 8m30s
    deployment.apps/chatqna-llm-uservice 1/1 1 1 8m30s
    deployment.apps/chatqna-redis-vector-db 1/1 1 1 8m30s
    deployment.apps/chatqna-reranking-usvc 1/1 1 1 8m30s
    deployment.apps/chatqna-retriever-usvc 1/1 1 1 8m30s
    deployment.apps/chatqna-tei 0/1 1 0 8m30s
    deployment.apps/chatqna-teirerank 0/1 1 0 8m30s
    deployment.apps/chatqna-tgi 0/1 1 0 8m30s
    NAME DESIRED CURRENT READY AGE
    replicaset.apps/chatqna-79d8c5ffff 1 1 1 8m29s
    replicaset.apps/chatqna-data-prep-77dcc665f4 1 1 1 8m30s
    replicaset.apps/chatqna-embedding-usvc-55d4dc8f67 1 1 1 8m30s
    replicaset.apps/chatqna-llm-uservice-66cc67785 1 1 1 8m30s
    replicaset.apps/chatqna-redis-vector-db-5dcd98f579 1 1 1 8m30s
    replicaset.apps/chatqna-reranking-usvc-759bf96c5c 1 1 1 8m30s
    replicaset.apps/chatqna-retriever-usvc-86f8dfbfb6 1 1 1 8m30s
    replicaset.apps/chatqna-tei-565488dd9 1 1 0 8m30s
    replicaset.apps/chatqna-teirerank-6c9854cfdf 1 1 0 8m30s
    replicaset.apps/chatqna-tgi-587b54f5ff 1 1 0 8m29s
    ec2-user:~/environment:$ kubectl logs pod/chatqna-tei-565488dd9-p4cj7
    Error from server (BadRequest): container "tei" in pod "chatqna-tei-565488dd9-p4cj7" is waiting to start: ContainerCreating
    ec2-user:~/environment:$ kubectl logs pod/chatqna-teirerank-6c9854cfdf-mmgqh
    Error from server (BadRequest): container "teirerank" in pod "chatqna-teirerank-6c9854cfdf-mmgqh" is waiting to start: ContainerCreating
    ec2-user:~/environment:$ kubectl logs pod/chatqna-tgi-587b54f5ff-fcfqn
    Error from server (BadRequest): container "tgi" in pod "chatqna-tgi-587b54f5ff-fcfqn" is waiting to start: ContainerCreating
    ```
  13. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 0 additions and 269 deletions.
    269 changes: 0 additions & 269 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -126,272 +126,3 @@
    deployment.apps/chatqna created
    ```
    -
    ## OLD
    Not able to create EKS cluster using EKS workshop: https://repost.aws/questions/QUeF1yD6ahSR-a0ZkYyB04Qw/cloud9-access-no-longer-available, so starting a fresh.
    ## Download AWS CLI
    ```
    arungupt@Aruns-MBP-67774 %curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg"
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    100 38.1M 100 38.1M 0 0 26.6M 0 0:00:01 0:00:01 --:--:-- 26.6M
    arungupt@Aruns-MBP-67774 %sudo installer -pkg AWSCLIV2.pkg -target /
    Password:
    installer: Package name is AWS Command Line Interface
    installer: Installing at base path /
    installer: The install was successful.
    arungupt@Aruns-MBP-67774 %which aws
    /usr/local/bin/aws
    arungupt@Aruns-MBP-67774 %aws --version
    aws-cli/2.17.20 Python/3.11.9 Darwin/23.5.0 exe/x86_64
    ```
    ## Install `eksctl`
    ```
    arungupt@Aruns-MBP-67774 %brew tap weaveworks/tap
    brew install weaveworks/tap/eksctl
    Running `brew update --auto-update`...
    ==> Downloading https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:1e64d7393d6bed090ebd892514457a10a2066682693eaade7d4a25568fa35312
    #################################################################################################################################################################################### 100.0%
    ==> Pouring portable-ruby-3.3.4.arm64_big_sur.bottle.tar.gz
    ==> Auto-updated Homebrew!
    Updated 3 taps (homebrew/services, homebrew/core and homebrew/cask).
    ==> New Formulae
    actions-batch cyme gitu kuzu nerdfetch pulsarctl tenv
    age-plugin-se deadfinder glasskube lando-cli netaddr qrtool terrahash
    ansible-creator dep-tree gnmic lexido nextdns qshell terramaid
    ansible@9 descope go-size-analyzer [email protected] nmail

    . . .


    yass
    font-encode-sans-sc font-micro-5 font-rubik yes24-ebook
    font-encode-sans-semi-condensed font-micro-5-charted font-rubik-80s-fade youlean-loudness-meter
    font-encode-sans-semi-expanded font-migmix-1m font-rubik-beastly zed@preview
    font-engagement font-migmix-1p font-rubik-broken-fax zotero@beta
    font-englebert font-migmix-2m font-rubik-bubbles zulu@11
    font-enriqueta font-migmix-2p font-rubik-burned zulu@17
    font-envy-code-r font-migu-1c font-rubik-dirt zulu@21
    font-envy-code-r-nerd-font font-migu-1m font-rubik-distressed zulu@8
    font-ephesis font-migu-1p font-rubik-doodle-shadow
    font-epilogue font-migu-2m font-rubik-doodle-triangles
    font-erica-one font-milonga font-rubik-gemstones

    You have 27 outdated formulae installed.

    ==> Tapping weaveworks/tap
    Cloning into '/opt/homebrew/Library/Taps/weaveworks/homebrew-tap'...
    remote: Enumerating objects: 1927, done.
    remote: Counting objects: 100% (763/763), done.
    remote: Compressing objects: 100% (423/423), done.
    remote: Total 1927 (delta 460), reused 590 (delta 340), pack-reused 1164
    Receiving objects: 100% (1927/1927), 306.41 KiB | 1.93 MiB/s, done.
    Resolving deltas: 100% (1024/1024), done.
    Tapped 7 formulae (21 files, 377.2KB).
    ==> Fetching dependencies for weaveworks/tap/eksctl: aws-iam-authenticator and kubernetes-cli
    ==> Fetching aws-iam-authenticator
    ==> Downloading https://ghcr.io/v2/homebrew/core/aws-iam-authenticator/manifests/0.6.22
    #################################################################################################################################################################################### 100.0%
    ==> Downloading https://ghcr.io/v2/homebrew/core/aws-iam-authenticator/blobs/sha256:6ae552fde609c25ddb65bd5d4f0f122f9b180f3721a6c153daa9ce449167d297
    #################################################################################################################################################################################### 100.0%
    ==> Fetching kubernetes-cli
    ==> Downloading https://ghcr.io/v2/homebrew/core/kubernetes-cli/manifests/1.30.3
    #################################################################################################################################################################################### 100.0%
    ==> Downloading https://ghcr.io/v2/homebrew/core/kubernetes-cli/blobs/sha256:997269d89ad1a95bb8146f107aa8b8a003bc26039758b77e6e78b8cb402142c8
    #################################################################################################################################################################################### 100.0%
    ==> Fetching weaveworks/tap/eksctl
    ==> Downloading https://github.com/eksctl-io/eksctl/releases/download/v0.188.0/eksctl_Darwin_arm64.tar.gz
    ==> Downloading from https://objects.githubusercontent.com/github-production-release-asset-2e65be/134539560/5e30df5d-0577-486c-93f7-0c16acfa57b9?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Cre
    #################################################################################################################################################################################### 100.0%
    ==> Installing eksctl from weaveworks/tap
    ==> Installing dependencies for weaveworks/tap/eksctl: aws-iam-authenticator and kubernetes-cli
    ==> Installing weaveworks/tap/eksctl dependency: aws-iam-authenticator
    ==> Downloading https://ghcr.io/v2/homebrew/core/aws-iam-authenticator/manifests/0.6.22
    Already downloaded: /Users/arungupt/Library/Caches/Homebrew/downloads/83a9eaaa411dcca7f64bc0064ee2c51f771cec43dc974b66f602c23c7cd3fff6--aws-iam-authenticator-0.6.22.bottle_manifest.json
    ==> Pouring aws-iam-authenticator--0.6.22.arm64_sonoma.bottle.tar.gz
    🍺 /opt/homebrew/Cellar/aws-iam-authenticator/0.6.22: 7 files, 56.7MB
    ==> Installing weaveworks/tap/eksctl dependency: kubernetes-cli
    ==> Downloading https://ghcr.io/v2/homebrew/core/kubernetes-cli/manifests/1.30.3
    Already downloaded: /Users/arungupt/Library/Caches/Homebrew/downloads/6d1a6d2bb19610586f3df47cc991e16dffaa1ff3073b234b784d7f1b888ddc2c--kubernetes-cli-1.30.3.bottle_manifest.json
    ==> Pouring kubernetes-cli--1.30.3.arm64_sonoma.bottle.tar.gz
    🍺 /opt/homebrew/Cellar/kubernetes-cli/1.30.3: 236 files, 54.3MB
    ==> Installing weaveworks/tap/eksctl
    ==> Caveats
    zsh completions have been installed to:
    /opt/homebrew/share/zsh/site-functions
    ==> Summary
    🍺 /opt/homebrew/Cellar/eksctl/0.188.0: 6 files, 151MB, built in 5 seconds
    ==> Running `brew cleanup eksctl`...
    Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
    Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
    ==> `brew cleanup` has not been run in the last 30 days, running now...
    Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
    Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
    Removing: /Users/arungupt/Library/Caches/Homebrew/ca-certificates_bottle_manifest--2023-12-12... (1.8KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/ca-certificates--2023-12-12... (127.7KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/libidn2_bottle_manifest--2.3.4_1-1... (10.5KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/libidn2--2.3.4_1... (324.2KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/libunistring_bottle_manifest--1.1... (8.9KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/libunistring--1.1... (1.6MB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/md5sha1sum_bottle_manifest--0.9.5_1-1... (11.3KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/md5sha1sum--0.9.5_1... (14.2KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/openssl@3_bottle_manifest--3.2.0_1... (9.2KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/[email protected]_1... (9.4MB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/wget_bottle_manifest--1.21.4... (13.3KB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/wget--1.21.4... (1.5MB)
    Removing: /Users/arungupt/Library/Caches/Homebrew/portable-ruby-3.1.4.arm64_big_sur.bottle.tar.gz... (12.4MB)
    Removing: /Users/arungupt/Library/Logs/Homebrew/openssl@3... (64B)
    Removing: /Users/arungupt/Library/Logs/Homebrew/ca-certificates... (64B)
    Pruned 0 symbolic links and 2 directories from /opt/homebrew
    ==> Caveats
    ==> eksctl
    zsh completions have been installed to:
    /opt/homebrew/share/zsh/site-functions
    ```
    ## Create EKS cluster
    Use this `cluster.yaml`
    ```
    apiVersion: eksctl.io/v1alpha5
    kind: ClusterConfig
    availabilityZones:
    - us-west-2a
    - us-west-2b
    - us-west-2c
    metadata:
    name: eks-opea
    region: us-west-2
    version: "1.30"
    tags:
    karpenter.sh/discovery: eks-opea
    created-by: eks-workshop-v2
    env: eks-opea
    iam:
    withOIDC: true
    vpc:
    cidr: 10.42.0.0/16
    clusterEndpoints:
    privateAccess: true
    publicAccess: true
    addons:
    - name: vpc-cni
    version: 1.16.0
    configurationValues: '{"env":{"ENABLE_PREFIX_DELEGATION":"true", "ENABLE_POD_ENI":"true", "POD_SECURITY_GROUP_ENFORCING_MODE":"standard"},"enableNetworkPolicy": "true"}'
    resolveConflicts: overwrite
    managedNodeGroups:
    - name: default
    desiredCapacity: 2
    minSize: 2
    maxSize: 4
    instanceType: m7i.large
    privateNetworking: true
    releaseVersion: "1.30.0-20240625"
    updateConfig:
    maxUnavailablePercentage: 50
    labels:
    workshop-default: "yes"
    ```
    Create cluster:
    ```
    arungupt@Aruns-MBP-67774 eks-demo %eksctl create cluster -f cluster.yaml
    2024-07-31 17:10:49 [ℹ] eksctl version 0.188.0
    2024-07-31 17:10:49 [ℹ] using region us-west-2
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2a - public:10.42.0.0/19 private:10.42.96.0/19
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2b - public:10.42.32.0/19 private:10.42.128.0/19
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2c - public:10.42.64.0/19 private:10.42.160.0/19
    2024-07-31 17:10:49 [ℹ] nodegroup "default" will use "" [AmazonLinux2023/1.30]
    2024-07-31 17:10:49 [ℹ] using Kubernetes version 1.30
    2024-07-31 17:10:49 [ℹ] creating EKS cluster "eks-opea" in "us-west-2" region with managed nodes
    2024-07-31 17:10:49 [ℹ] 1 nodegroup (default) was included (based on the include/exclude rules)
    2024-07-31 17:10:49 [ℹ] will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
    2024-07-31 17:10:49 [ℹ] will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
    2024-07-31 17:10:49 [ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-opea'
    2024-07-31 17:10:49 [ℹ] Kubernetes API endpoint access will use provided values {publicAccess=true, privateAccess=true} for cluster "eks-opea" in "us-west-2"
    2024-07-31 17:10:49 [ℹ] CloudWatch logging will not be enabled for cluster "eks-opea" in "us-west-2"
    2024-07-31 17:10:49 [ℹ] you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-opea'
    2024-07-31 17:10:49 [ℹ] default addons kube-proxy, coredns were not specified, will install them as EKS addons
    2024-07-31 17:10:49 [ℹ]
    2 sequential tasks: { create cluster control plane "eks-opea",
    2 sequential sub-tasks: {
    5 sequential sub-tasks: {
    1 task: { create addons },
    wait for control plane to become ready,
    associate IAM OIDC provider,
    no tasks,
    update VPC CNI to use IRSA if required,
    },
    create managed nodegroup "default",
    }
    }
    2024-07-31 17:10:49 [ℹ] building cluster stack "eksctl-eks-opea-cluster"
    2024-07-31 17:10:50 [ℹ] deploying stack "eksctl-eks-opea-cluster"
    2024-07-31 17:11:20 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:11:50 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:12:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:13:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:14:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:15:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:16:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:17:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:18:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:19:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:19:56 [!] recommended policies were found for "vpc-cni" addon, but since OIDC is disabled on the cluster, eksctl cannot configure the requested permissions; the recommended way to provide IAM permissions for "vpc-cni" addon is via pod identity associations; after addon creation is completed, add all recommended policies to the config file, under `addon.PodIdentityAssociations`, and run `eksctl update addon`
    2024-07-31 17:19:56 [ℹ] creating addon
    2024-07-31 17:19:56 [ℹ] successfully created addon
    2024-07-31 17:19:56 [ℹ] creating addon
    2024-07-31 17:19:57 [ℹ] successfully created addon
    2024-07-31 17:19:57 [ℹ] creating addon
    2024-07-31 17:19:57 [ℹ] successfully created addon
    2024-07-31 17:22:01 [ℹ] deploying stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:01 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:31 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:31 [ℹ] updating addon
    2024-07-31 17:22:42 [ℹ] addon "vpc-cni" active
    2024-07-31 17:22:42 [ℹ] building managed nodegroup stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:22:43 [ℹ] deploying stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:22:43 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:23:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:23:54 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:25:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:27:38 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:28:18 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:28:54 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:29:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:30:34 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:31:16 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:32:01 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:33:17 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:33:57 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:34:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:35:15 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:36:35 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:38:05 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:39:33 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:40:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:42:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:44:09 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:45:29 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:46:23 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:47:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:47:13 [!] 1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
    2024-07-31 17:47:13 [ℹ] to cleanup resources, run 'eksctl delete cluster --region=us-west-2 --name=eks-opea'
    2024-07-31 17:47:13 [✖] exceeded max wait time for StackCreateComplete waiter
    Error: failed to create cluster "eks-opea"
    ```
    ## Install GMC
    ```
    kubectl create ns chatqa
    kubectl config set-context --current --namespace=chatqa
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/chatQnA_xeon.yaml | kubectl apply -f -
    ```
  14. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # EKS cluster
    # OPEA on Amazon EKS

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Here is the final output:
    ```
  15. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 83 additions and 83 deletions.
    166 changes: 83 additions & 83 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,89 +1,89 @@
    # EKS cluster

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Here is the final output:
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | \
    envsubst | eksctl create cluster -f -
    2024-09-04 00:47:25 [ℹ] eksctl version 0.188.0
    2024-09-04 00:47:25 [ℹ] using region us-west-2
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2a - public:10.42.0.0/19 private:10.42.96.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2b - public:10.42.32.0/19 private:10.42.128.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2c - public:10.42.64.0/19 private:10.42.160.0/19
    2024-09-04 00:47:25 [ℹ] nodegroup "default" will use "" [AmazonLinux2023/1.30]
    2024-09-04 00:47:25 [ℹ] using Kubernetes version 1.30
    2024-09-04 00:47:25 [ℹ] creating EKS cluster "eks-workshop" in "us-west-2" region with managed nodes
    2024-09-04 00:47:25 [ℹ] 1 nodegroup (default) was included (based on the include/exclude rules)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] Kubernetes API endpoint access will use provided values {publicAccess=true, privateAccess=true} for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] CloudWatch logging will not be enabled for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] default addons kube-proxy, coredns were not specified, will install them as EKS addons
    2024-09-04 00:47:25 [ℹ]
    2 sequential tasks: { create cluster control plane "eks-workshop",
    2 sequential sub-tasks: {
    5 sequential sub-tasks: {
    1 task: { create addons },
    wait for control plane to become ready,
    associate IAM OIDC provider,
    no tasks,
    update VPC CNI to use IRSA if required,
    },
    create managed nodegroup "default",
    }
    }
    2024-09-04 00:47:25 [ℹ] building cluster stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:26 [ℹ] deploying stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:56 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:48:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:49:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:50:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:51:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:52:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:53:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:54:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:55:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:56:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:27 [!] recommended policies were found for "vpc-cni" addon, but since OIDC is disabled on the cluster, eksctl cannot configure the requested permissions; the recommended way to provide IAM permissions for "vpc-cni" addon is via pod identity associations; after addon creation is completed, add all recommended policies to the config file, under `addon.PodIdentityAssociations`, and run `eksctl update addon`
    2024-09-04 00:57:27 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:28 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:29 [ℹ] creating addon
    2024-09-04 00:57:29 [ℹ] successfully created addon
    2024-09-04 00:59:30 [ℹ] deploying stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 00:59:30 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] updating addon
    2024-09-04 01:00:11 [ℹ] addon "vpc-cni" active
    2024-09-04 01:00:11 [ℹ] building managed nodegroup stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] deploying stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:01:38 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for the control plane to become ready
    2024-09-04 01:02:34 [✔] saved kubeconfig as "/home/ec2-user/.kube/config"
    2024-09-04 01:02:34 [ℹ] no tasks
    2024-09-04 01:02:34 [✔] all EKS cluster resources for "eks-workshop" have been created
    2024-09-04 01:02:34 [✔] created 0 nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] waiting for at least 3 node(s) to become ready in "default"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [✔] created 1 managed nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:36 [ℹ] kubectl command should work with "/home/ec2-user/.kube/config", try 'kubectl get nodes'
    2024-09-04 01:02:36 [✔] EKS cluster "eks-workshop" in "us-west-2" region is ready
    ```
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | \
    envsubst | eksctl create cluster -f -
    2024-09-04 00:47:25 [ℹ] eksctl version 0.188.0
    2024-09-04 00:47:25 [ℹ] using region us-west-2
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2a - public:10.42.0.0/19 private:10.42.96.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2b - public:10.42.32.0/19 private:10.42.128.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2c - public:10.42.64.0/19 private:10.42.160.0/19
    2024-09-04 00:47:25 [ℹ] nodegroup "default" will use "" [AmazonLinux2023/1.30]
    2024-09-04 00:47:25 [ℹ] using Kubernetes version 1.30
    2024-09-04 00:47:25 [ℹ] creating EKS cluster "eks-workshop" in "us-west-2" region with managed nodes
    2024-09-04 00:47:25 [ℹ] 1 nodegroup (default) was included (based on the include/exclude rules)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] Kubernetes API endpoint access will use provided values {publicAccess=true, privateAccess=true} for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] CloudWatch logging will not be enabled for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] default addons kube-proxy, coredns were not specified, will install them as EKS addons
    2024-09-04 00:47:25 [ℹ]
    2 sequential tasks: { create cluster control plane "eks-workshop",
    2 sequential sub-tasks: {
    5 sequential sub-tasks: {
    1 task: { create addons },
    wait for control plane to become ready,
    associate IAM OIDC provider,
    no tasks,
    update VPC CNI to use IRSA if required,
    },
    create managed nodegroup "default",
    }
    }
    2024-09-04 00:47:25 [ℹ] building cluster stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:26 [ℹ] deploying stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:56 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:48:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:49:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:50:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:51:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:52:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:53:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:54:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:55:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:56:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:27 [!] recommended policies were found for "vpc-cni" addon, but since OIDC is disabled on the cluster, eksctl cannot configure the requested permissions; the recommended way to provide IAM permissions for "vpc-cni" addon is via pod identity associations; after addon creation is completed, add all recommended policies to the config file, under `addon.PodIdentityAssociations`, and run `eksctl update addon`
    2024-09-04 00:57:27 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:28 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:29 [ℹ] creating addon
    2024-09-04 00:57:29 [ℹ] successfully created addon
    2024-09-04 00:59:30 [ℹ] deploying stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 00:59:30 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] updating addon
    2024-09-04 01:00:11 [ℹ] addon "vpc-cni" active
    2024-09-04 01:00:11 [ℹ] building managed nodegroup stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] deploying stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:01:38 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for the control plane to become ready
    2024-09-04 01:02:34 [✔] saved kubeconfig as "/home/ec2-user/.kube/config"
    2024-09-04 01:02:34 [ℹ] no tasks
    2024-09-04 01:02:34 [✔] all EKS cluster resources for "eks-workshop" have been created
    2024-09-04 01:02:34 [✔] created 0 nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] waiting for at least 3 node(s) to become ready in "default"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [✔] created 1 managed nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:36 [ℹ] kubectl command should work with "/home/ec2-user/.kube/config", try 'kubectl get nodes'
    2024-09-04 01:02:36 [✔] EKS cluster "eks-workshop" in "us-west-2" region is ready
    ```
    - Download Helm chart:
    ```
    curl -O https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml
  16. arun-gupta revised this gist Sep 4, 2024. 1 changed file with 131 additions and 0 deletions.
    131 changes: 131 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,3 +1,134 @@
    # EKS cluster

    - Create EKS cluster as explained at https://www.eksworkshop.com/docs/introduction/setup/your-account/ using VSCode option. Here is the final output:
    ```
    ec2-user:~/environment:$
    export EKS_CLUSTER_NAME=eks-workshop
    curl -fsSL https://raw.githubusercontent.com/aws-samples/eks-workshop-v2/stable/cluster/eksctl/cluster.yaml | \
    envsubst | eksctl create cluster -f -
    2024-09-04 00:47:25 [ℹ] eksctl version 0.188.0
    2024-09-04 00:47:25 [ℹ] using region us-west-2
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2a - public:10.42.0.0/19 private:10.42.96.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2b - public:10.42.32.0/19 private:10.42.128.0/19
    2024-09-04 00:47:25 [ℹ] subnets for us-west-2c - public:10.42.64.0/19 private:10.42.160.0/19
    2024-09-04 00:47:25 [ℹ] nodegroup "default" will use "" [AmazonLinux2023/1.30]
    2024-09-04 00:47:25 [ℹ] using Kubernetes version 1.30
    2024-09-04 00:47:25 [ℹ] creating EKS cluster "eks-workshop" in "us-west-2" region with managed nodes
    2024-09-04 00:47:25 [ℹ] 1 nodegroup (default) was included (based on the include/exclude rules)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
    2024-09-04 00:47:25 [ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] Kubernetes API endpoint access will use provided values {publicAccess=true, privateAccess=true} for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] CloudWatch logging will not be enabled for cluster "eks-workshop" in "us-west-2"
    2024-09-04 00:47:25 [ℹ] you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-workshop'
    2024-09-04 00:47:25 [ℹ] default addons kube-proxy, coredns were not specified, will install them as EKS addons
    2024-09-04 00:47:25 [ℹ]
    2 sequential tasks: { create cluster control plane "eks-workshop",
    2 sequential sub-tasks: {
    5 sequential sub-tasks: {
    1 task: { create addons },
    wait for control plane to become ready,
    associate IAM OIDC provider,
    no tasks,
    update VPC CNI to use IRSA if required,
    },
    create managed nodegroup "default",
    }
    }
    2024-09-04 00:47:25 [ℹ] building cluster stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:26 [ℹ] deploying stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:47:56 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:48:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:49:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:50:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:51:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:52:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:53:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:54:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:55:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:56:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:26 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-cluster"
    2024-09-04 00:57:27 [!] recommended policies were found for "vpc-cni" addon, but since OIDC is disabled on the cluster, eksctl cannot configure the requested permissions; the recommended way to provide IAM permissions for "vpc-cni" addon is via pod identity associations; after addon creation is completed, add all recommended policies to the config file, under `addon.PodIdentityAssociations`, and run `eksctl update addon`
    2024-09-04 00:57:27 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:28 [ℹ] creating addon
    2024-09-04 00:57:28 [ℹ] successfully created addon
    2024-09-04 00:57:29 [ℹ] creating addon
    2024-09-04 00:57:29 [ℹ] successfully created addon
    2024-09-04 00:59:30 [ℹ] deploying stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 00:59:30 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-addon-vpc-cni"
    2024-09-04 01:00:00 [ℹ] updating addon
    2024-09-04 01:00:11 [ℹ] addon "vpc-cni" active
    2024-09-04 01:00:11 [ℹ] building managed nodegroup stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] deploying stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:11 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:00:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:01:38 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for CloudFormation stack "eksctl-eks-workshop-nodegroup-default"
    2024-09-04 01:02:33 [ℹ] waiting for the control plane to become ready
    2024-09-04 01:02:34 [✔] saved kubeconfig as "/home/ec2-user/.kube/config"
    2024-09-04 01:02:34 [ℹ] no tasks
    2024-09-04 01:02:34 [✔] all EKS cluster resources for "eks-workshop" have been created
    2024-09-04 01:02:34 [✔] created 0 nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] waiting for at least 3 node(s) to become ready in "default"
    2024-09-04 01:02:34 [ℹ] nodegroup "default" has 3 node(s)
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-110-222.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-151-87.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [ℹ] node "ip-10-42-173-37.us-west-2.compute.internal" is ready
    2024-09-04 01:02:34 [✔] created 1 managed nodegroup(s) in cluster "eks-workshop"
    2024-09-04 01:02:36 [ℹ] kubectl command should work with "/home/ec2-user/.kube/config", try 'kubectl get nodes'
    2024-09-04 01:02:36 [✔] EKS cluster "eks-workshop" in "us-west-2" region is ready
    ```
    - Download Helm chart:
    ```
    curl -O https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml
    ```
    - Setup Hugging Face token:
    ```
    export HUGGINGFACEHUB_API_TOKEN="YourOwnToken"
    sed -i "s/insert-your-huggingface-token-here/${HUGGINGFACEHUB_API_TOKEN}/g" chatqna.yaml
    ```
    - Apply the Helm chart:
    ```
    ec2-user:~/environment:$ kubectl apply -f chatqna.yaml
    configmap/chatqna-data-prep-config created
    configmap/chatqna-embedding-usvc-config created
    configmap/chatqna-llm-uservice-config created
    configmap/chatqna-reranking-usvc-config created
    configmap/chatqna-retriever-usvc-config created
    configmap/chatqna-tei-config created
    configmap/chatqna-teirerank-config created
    configmap/chatqna-tgi-config created
    service/chatqna-data-prep created
    service/chatqna-embedding-usvc created
    service/chatqna-llm-uservice created
    service/chatqna-redis-vector-db created
    service/chatqna-reranking-usvc created
    service/chatqna-retriever-usvc created
    service/chatqna-tei created
    service/chatqna-teirerank created
    service/chatqna-tgi created
    service/chatqna created
    deployment.apps/chatqna-data-prep created
    deployment.apps/chatqna-embedding-usvc created
    deployment.apps/chatqna-llm-uservice created
    deployment.apps/chatqna-redis-vector-db created
    deployment.apps/chatqna-reranking-usvc created
    deployment.apps/chatqna-retriever-usvc created
    deployment.apps/chatqna-tei created
    deployment.apps/chatqna-teirerank created
    deployment.apps/chatqna-tgi created
    deployment.apps/chatqna created
    ```
    -

    ## OLD

    Not able to create EKS cluster using EKS workshop: https://repost.aws/questions/QUeF1yD6ahSR-a0ZkYyB04Qw/cloud9-access-no-longer-available, so starting a fresh.

    ## Download AWS CLI
  17. arun-gupta revised this gist Aug 1, 2024. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,3 +1,5 @@
    Not able to create EKS cluster using EKS workshop: https://repost.aws/questions/QUeF1yD6ahSR-a0ZkYyB04Qw/cloud9-access-no-longer-available, so starting a fresh.

    ## Download AWS CLI

    ```
  18. arun-gupta revised this gist Aug 1, 2024. 1 changed file with 92 additions and 1 deletion.
    93 changes: 92 additions & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -169,5 +169,96 @@ managedNodeGroups:
    Create cluster:

    ```
    eksctl create cluster -f cluster.yaml
    arungupt@Aruns-MBP-67774 eks-demo %eksctl create cluster -f cluster.yaml
    2024-07-31 17:10:49 [ℹ] eksctl version 0.188.0
    2024-07-31 17:10:49 [ℹ] using region us-west-2
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2a - public:10.42.0.0/19 private:10.42.96.0/19
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2b - public:10.42.32.0/19 private:10.42.128.0/19
    2024-07-31 17:10:49 [ℹ] subnets for us-west-2c - public:10.42.64.0/19 private:10.42.160.0/19
    2024-07-31 17:10:49 [ℹ] nodegroup "default" will use "" [AmazonLinux2023/1.30]
    2024-07-31 17:10:49 [ℹ] using Kubernetes version 1.30
    2024-07-31 17:10:49 [ℹ] creating EKS cluster "eks-opea" in "us-west-2" region with managed nodes
    2024-07-31 17:10:49 [ℹ] 1 nodegroup (default) was included (based on the include/exclude rules)
    2024-07-31 17:10:49 [ℹ] will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
    2024-07-31 17:10:49 [ℹ] will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
    2024-07-31 17:10:49 [ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-opea'
    2024-07-31 17:10:49 [ℹ] Kubernetes API endpoint access will use provided values {publicAccess=true, privateAccess=true} for cluster "eks-opea" in "us-west-2"
    2024-07-31 17:10:49 [ℹ] CloudWatch logging will not be enabled for cluster "eks-opea" in "us-west-2"
    2024-07-31 17:10:49 [ℹ] you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-opea'
    2024-07-31 17:10:49 [ℹ] default addons kube-proxy, coredns were not specified, will install them as EKS addons
    2024-07-31 17:10:49 [ℹ]
    2 sequential tasks: { create cluster control plane "eks-opea",
    2 sequential sub-tasks: {
    5 sequential sub-tasks: {
    1 task: { create addons },
    wait for control plane to become ready,
    associate IAM OIDC provider,
    no tasks,
    update VPC CNI to use IRSA if required,
    },
    create managed nodegroup "default",
    }
    }
    2024-07-31 17:10:49 [ℹ] building cluster stack "eksctl-eks-opea-cluster"
    2024-07-31 17:10:50 [ℹ] deploying stack "eksctl-eks-opea-cluster"
    2024-07-31 17:11:20 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:11:50 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:12:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:13:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:14:51 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:15:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:16:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:17:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:18:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:19:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-cluster"
    2024-07-31 17:19:56 [!] recommended policies were found for "vpc-cni" addon, but since OIDC is disabled on the cluster, eksctl cannot configure the requested permissions; the recommended way to provide IAM permissions for "vpc-cni" addon is via pod identity associations; after addon creation is completed, add all recommended policies to the config file, under `addon.PodIdentityAssociations`, and run `eksctl update addon`
    2024-07-31 17:19:56 [ℹ] creating addon
    2024-07-31 17:19:56 [ℹ] successfully created addon
    2024-07-31 17:19:56 [ℹ] creating addon
    2024-07-31 17:19:57 [ℹ] successfully created addon
    2024-07-31 17:19:57 [ℹ] creating addon
    2024-07-31 17:19:57 [ℹ] successfully created addon
    2024-07-31 17:22:01 [ℹ] deploying stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:01 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:31 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-addon-vpc-cni"
    2024-07-31 17:22:31 [ℹ] updating addon
    2024-07-31 17:22:42 [ℹ] addon "vpc-cni" active
    2024-07-31 17:22:42 [ℹ] building managed nodegroup stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:22:43 [ℹ] deploying stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:22:43 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:23:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:23:54 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:25:53 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:27:38 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:28:18 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:28:54 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:29:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:30:34 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:31:16 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:32:01 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:33:17 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:33:57 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:34:41 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:35:15 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:36:35 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:38:05 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:39:33 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:40:52 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:42:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:44:09 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:45:29 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:46:23 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:47:13 [ℹ] waiting for CloudFormation stack "eksctl-eks-opea-nodegroup-default"
    2024-07-31 17:47:13 [!] 1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
    2024-07-31 17:47:13 [ℹ] to cleanup resources, run 'eksctl delete cluster --region=us-west-2 --name=eks-opea'
    2024-07-31 17:47:13 [✖] exceeded max wait time for StackCreateComplete waiter
    Error: failed to create cluster "eks-opea"
    ```

    ## Install GMC

    ```
    kubectl create ns chatqa
    kubectl config set-context --current --namespace=chatqa
    curl -fsSL https://raw.githubusercontent.com/opea-project/GenAIExamples/main/ChatQnA/kubernetes/chatQnA_xeon.yaml | kubectl apply -f -
    ```
  19. arun-gupta revised this gist Aug 1, 2024. No changes.
  20. arun-gupta revised this gist Aug 1, 2024. 1 changed file with 47 additions and 3 deletions.
    50 changes: 47 additions & 3 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -121,9 +121,53 @@ zsh completions have been installed to:
    /opt/homebrew/share/zsh/site-functions
    ```

    ## Set up environment variables
    ## Create EKS cluster

    Use this `cluster.yaml`

    ```
    apiVersion: eksctl.io/v1alpha5
    kind: ClusterConfig
    availabilityZones:
    - us-west-2a
    - us-west-2b
    - us-west-2c
    metadata:
    name: eks-opea
    region: us-west-2
    version: "1.30"
    tags:
    karpenter.sh/discovery: eks-opea
    created-by: eks-workshop-v2
    env: eks-opea
    iam:
    withOIDC: true
    vpc:
    cidr: 10.42.0.0/16
    clusterEndpoints:
    privateAccess: true
    publicAccess: true
    addons:
    - name: vpc-cni
    version: 1.16.0
    configurationValues: '{"env":{"ENABLE_PREFIX_DELEGATION":"true", "ENABLE_POD_ENI":"true", "POD_SECURITY_GROUP_ENFORCING_MODE":"standard"},"enableNetworkPolicy": "true"}'
    resolveConflicts: overwrite
    managedNodeGroups:
    - name: default
    desiredCapacity: 2
    minSize: 2
    maxSize: 4
    instanceType: m7i.large
    privateNetworking: true
    releaseVersion: "1.30.0-20240625"
    updateConfig:
    maxUnavailablePercentage: 50
    labels:
    workshop-default: "yes"
    ```

    Create cluster:

    ```
    arungupt@Aruns-MBP-67774 %export AWS_REGION=us-west-2
    arungupt@Aruns-MBP-67774 %export EKS_CLUSTER_NAME=eks-opea
    eksctl create cluster -f cluster.yaml
    ```
  21. arun-gupta revised this gist Jul 31, 2024. 1 changed file with 6 additions and 689 deletions.
    695 changes: 6 additions & 689 deletions readme.md
    View file
    6 additions, 689 deletions not shown because the diff is too large. Please use a local Git client to view these changes.
  22. arun-gupta created this gist Jul 31, 2024.
    812 changes: 812 additions & 0 deletions readme.md
    View file
    812 additions, 0 deletions not shown because the diff is too large. Please use a local Git client to view these changes.