chunk_id stringlengths 36 36 | source stringclasses 35
values | source_url stringlengths 0 290 | upstream_license stringclasses 1
value | document_id stringlengths 36 36 | chunk_index int64 0 324k | retrieved_at stringclasses 2
values | chunker_version stringclasses 4
values | content_hash stringlengths 15 64 | content stringlengths 50 44.7k | namespace stringclasses 9
values | source_name stringclasses 35
values | raw_text stringlengths 50 44.7k | cleaned_text stringlengths 50 44.7k | tags stringclasses 49
values | collection_name stringclasses 11
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1f4f7fc9-45fe-4fa7-8381-713fff7ff44b | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 1 | opea-semantic-v1 | 3f4eb02339b4f187 | a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release.
## Install Habana Driver (Gaudi Only)
1. Driver and software installation
https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html
2. Firmware upgrade
https:... | ai_ref_knowledge | OPEA Documentation | a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release.
## Install Habana Driver (Gaudi Only)
1. Driver and software installation
https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html
2. Firmware upgrade
https:... | a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release.
## Install Habana Driver (Gaudi Only)
1. Driver and software installation
https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html
2. Firmware upgrade
https:... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2ca4a81a-951b-46ca-a554-8e02c4ed4263 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 29 | opea-semantic-v1 | c6593516967b619e | helm install "${RUNNER_SET_NAME}" \ --namespace "${RUNNERS_NAMESPACE}" \ --create-namespace \ -f xeon_large.yaml \ --set githubConfigUrl="${GITHUB_CONFIG_URL}" \ --set githubConfigSecret.github_token="${GITHUB_PAT}" \ --set runnerGroup="${RUNNER_GROUP}" \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runne... | ai_ref_knowledge | OPEA Documentation | helm install "${RUNNER_SET_NAME}" \ --namespace "${RUNNERS_NAMESPACE}" \ --create-namespace \ -f xeon_large.yaml \ --set githubConfigUrl="${GITHUB_CONFIG_URL}" \ --set githubConfigSecret.github_token="${GITHUB_PAT}" \ --set runnerGroup="${RUNNER_GROUP}" \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runne... | helm install "${RUNNER_SET_NAME}" \ --namespace "${RUNNERS_NAMESPACE}" \ --create-namespace \ -f xeon_large.yaml \ --set githubConfigUrl="${GITHUB_CONFIG_URL}" \ --set githubConfigSecret.github_token="${GITHUB_PAT}" \ --set runnerGroup="${RUNNER_GROUP}" \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runne... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2e348054-d005-4be9-91f5-b81f8a763bd6 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 4 | opea-semantic-v1 | da4da70d2c611059 | echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install -y docker-compose-plugin
2. Issue: permission... | ai_ref_knowledge | OPEA Documentation | echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install -y docker-compose-plugin
2. Issue: permission... | echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install -y docker-compose-plugin
2. Issue: permission... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
31fb9dad-93c5-4d55-a1c3-27fea36ec324 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 0 | opea-semantic-v1 | 852afbbc6390a542 | # Setup Test Environment for CI/CD
This document outlines the steps to set up a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release. | ai_ref_knowledge | OPEA Documentation | # Setup Test Environment for CI/CD
This document outlines the steps to set up a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release. | # Setup Test Environment for CI/CD
This document outlines the steps to set up a test environment for OPEA CI/CD from scratch. The environment will be used to run tests and ensure code quality before PR merge and Release. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3655aae9-2bfe-4a7c-865d-9eff426687ef | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 22 | opea-semantic-v1 | e43733723617a1be | 4. Setup ENV for CI/CD. ```shell vi .bashrc export OPEA_IMAGE_REPO=100.83.111.232:5000/
5. Build and push images to the new local registry. | ai_ref_knowledge | OPEA Documentation | 4. Setup ENV for CI/CD. ```shell vi .bashrc export OPEA_IMAGE_REPO=100.83.111.232:5000/
5. Build and push images to the new local registry. | 4. Setup ENV for CI/CD. ```shell vi .bashrc export OPEA_IMAGE_REPO=100.83.111.232:5000/
5. Build and push images to the new local registry. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3840b0a9-88d9-4523-8e74-29a4812ebd62 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 8 | opea-semantic-v1 | 4b56bf17e104c0df | ## Install Conda For e2e test env setup. ```shell wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh bash Miniconda3-latest-Linux-x86_64.sh
## Install K8S
1. Use kubeadm to setup k8s cluster. https://github.com/opea-project/docs/blob/main/guide/installation/k8s_install/k8s_install_kubeadm.md
2.... | ai_ref_knowledge | OPEA Documentation | ## Install Conda For e2e test env setup. ```shell wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh bash Miniconda3-latest-Linux-x86_64.sh
## Install K8S
1. Use kubeadm to setup k8s cluster. https://github.com/opea-project/docs/blob/main/guide/installation/k8s_install/k8s_install_kubeadm.md
2.... | ## Install Conda For e2e test env setup. ```shell wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh bash Miniconda3-latest-Linux-x86_64.sh
## Install K8S
1. Use kubeadm to setup k8s cluster. https://github.com/opea-project/docs/blob/main/guide/installation/k8s_install/k8s_install_kubeadm.md
2.... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5c63209b-76b9-4b7c-8044-d7bbc835ec92 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 27 | opea-semantic-v1 | 7d16ecf5b89e0ec5 | helm uninstall arc -n $NAMESPACE kubectl delete namespace $NAMESPACE --grace-period=0 --force
2. Install a runner scale set
The runner image that we used in CI/CD build by this [dockerfile](https://github.com/opea-project/Validation/blob/main/tools/actions-runner-controller/xeon.dockerfile). And the config setting for ... | ai_ref_knowledge | OPEA Documentation | helm uninstall arc -n $NAMESPACE kubectl delete namespace $NAMESPACE --grace-period=0 --force
2. Install a runner scale set
The runner image that we used in CI/CD build by this [dockerfile](https://github.com/opea-project/Validation/blob/main/tools/actions-runner-controller/xeon.dockerfile). And the config setting for ... | helm uninstall arc -n $NAMESPACE kubectl delete namespace $NAMESPACE --grace-period=0 --force
2. Install a runner scale set
The runner image that we used in CI/CD build by this [dockerfile](https://github.com/opea-project/Validation/blob/main/tools/actions-runner-controller/xeon.dockerfile). And the config setting for ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5cae7929-a2fa-4903-8195-c47fe6a7c35e | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 7 | opea-semantic-v1 | f7a2705879b6fc4f | memory mapped areas that a process can have. [optional] **solution:** ```shell echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf sudo sysctl -p sysctl vm.max_map_count # check
## Install Conda
For e2e test env setup. ```shell
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash ... | ai_ref_knowledge | OPEA Documentation | memory mapped areas that a process can have. [optional] **solution:** ```shell echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf sudo sysctl -p sysctl vm.max_map_count # check
## Install Conda
For e2e test env setup. ```shell
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash ... | memory mapped areas that a process can have. [optional] **solution:** ```shell echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf sudo sysctl -p sysctl vm.max_map_count # check
## Install Conda
For e2e test env setup. ```shell
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6491cc19-cd10-4a9d-8723-da19b9195711 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 18 | opea-semantic-v1 | c3582cc998254b95 | # setup in client side cat /etc/containerd/config.toml ... [plugins."io.containerd.grpc.v1.cri".registry.mirrors] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"] endpoint = ["https://registry-1.docker.io"] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."100.83.111.232:5000"] endpoint = ["http:... | ai_ref_knowledge | OPEA Documentation | # setup in client side cat /etc/containerd/config.toml ... [plugins."io.containerd.grpc.v1.cri".registry.mirrors] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"] endpoint = ["https://registry-1.docker.io"] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."100.83.111.232:5000"] endpoint = ["http:... | # setup in client side cat /etc/containerd/config.toml ... [plugins."io.containerd.grpc.v1.cri".registry.mirrors] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"] endpoint = ["https://registry-1.docker.io"] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."100.83.111.232:5000"] endpoint = ["http:... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6c6d67c2-4a9a-4a6e-8a86-90eaa6c800e9 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 10 | opea-semantic-v1 | dfc23a5ba1e42bdc | template: spec: hostIPC: true restartPolicy: OnFailure containers: - name: habana-ai-base-container image: vault.habana.ai/gaudi-docker/1.21.1/ubuntu24.04/habanalabs/pytorch-installer-2.6.0:latest workingDir: /root command: ["hl-smi"] securityContext: capabilities: add: ["SYS_NICE"] resources: limits: habana.ai/gaudi: ... | ai_ref_knowledge | OPEA Documentation | template: spec: hostIPC: true restartPolicy: OnFailure containers: - name: habana-ai-base-container image: vault.habana.ai/gaudi-docker/1.21.1/ubuntu24.04/habanalabs/pytorch-installer-2.6.0:latest workingDir: /root command: ["hl-smi"] securityContext: capabilities: add: ["SYS_NICE"] resources: limits: habana.ai/gaudi: ... | template: spec: hostIPC: true restartPolicy: OnFailure containers: - name: habana-ai-base-container image: vault.habana.ai/gaudi-docker/1.21.1/ubuntu24.04/habanalabs/pytorch-installer-2.6.0:latest workingDir: /root command: ["hl-smi"] securityContext: capabilities: add: ["SYS_NICE"] resources: limits: habana.ai/gaudi: ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6d270789-23d9-4b1c-93da-e411cf5b1247 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 9 | opea-semantic-v1 | 82d64d9692efce8d | Test Code after Installation ```shell kubectl get nodes -o wide kubectl get pods -A kubectl get cs kubectl describe node <node_name> kubectl describe pod <pod_name>
Test for Gaudi:
```shell
cat <<EOF | tee test.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: habanalabs-gaudi-demo
spec:
template:
spec:
hostIPC:... | ai_ref_knowledge | OPEA Documentation | Test Code after Installation ```shell kubectl get nodes -o wide kubectl get pods -A kubectl get cs kubectl describe node <node_name> kubectl describe pod <pod_name>
Test for Gaudi:
```shell
cat <<EOF | tee test.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: habanalabs-gaudi-demo
spec:
template:
spec:
hostIPC:... | Test Code after Installation ```shell kubectl get nodes -o wide kubectl get pods -A kubectl get cs kubectl describe node <node_name> kubectl describe pod <pod_name>
Test for Gaudi:
```shell
cat <<EOF | tee test.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: habanalabs-gaudi-demo
spec:
template:
spec:
hostIPC:... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
737c14ec-29a6-4e8e-8939-43a6fbfd48ab | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 13 | opea-semantic-v1 | 15359f99e9fba35d | place to store the images mkdir local_image_registry && chmod -R 777 local_image_registry docker run -d -p 5000:5000 --restart=always --name registry -v /home/sdp/workspace/registry.yaml:/etc/docker/registry/config.yml -v /scratch-1/local_image_registry:/var/lib/registry registry:2
2. Setup docker registry clean up cro... | ai_ref_knowledge | OPEA Documentation | place to store the images mkdir local_image_registry && chmod -R 777 local_image_registry docker run -d -p 5000:5000 --restart=always --name registry -v /home/sdp/workspace/registry.yaml:/etc/docker/registry/config.yml -v /scratch-1/local_image_registry:/var/lib/registry registry:2
2. Setup docker registry clean up cro... | place to store the images mkdir local_image_registry && chmod -R 777 local_image_registry docker run -d -p 5000:5000 --restart=always --name registry -v /home/sdp/workspace/registry.yaml:/etc/docker/registry/config.yml -v /scratch-1/local_image_registry:/var/lib/registry registry:2
2. Setup docker registry clean up cro... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7b156a5f-97a2-4438-8e80-206dec20a639 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 5 | opea-semantic-v1 | 620e96e7318c871b | unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/json": dial unix /var/run/docker.sock: connect: permission denied **solution:** ```shell # option1. sudo usermod -a -G docker xxx # option2. sudo chmod 666 /var/run/docker.sock
3. Issue: ulimit -n setting. [optional]
**solution:**
``... | ai_ref_knowledge | OPEA Documentation | unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/json": dial unix /var/run/docker.sock: connect: permission denied **solution:** ```shell # option1. sudo usermod -a -G docker xxx # option2. sudo chmod 666 /var/run/docker.sock
3. Issue: ulimit -n setting. [optional]
**solution:**
``... | unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/json": dial unix /var/run/docker.sock: connect: permission denied **solution:** ```shell # option1. sudo usermod -a -G docker xxx # option2. sudo chmod 666 /var/run/docker.sock
3. Issue: ulimit -n setting. [optional]
**solution:**
``... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
860a4a59-b399-4e83-9486-a6186bdc2b28 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 20 | opea-semantic-v1 | 2ad87be83f34c707 | # restart containerd sudo systemctl restart containerd.service
# for test
docker pull opea/chatqna:latest
docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test
docker push 100.83.111.232:5000/opea/chatqna:test
sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test | ai_ref_knowledge | OPEA Documentation | # restart containerd sudo systemctl restart containerd.service
# for test
docker pull opea/chatqna:latest
docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test
docker push 100.83.111.232:5000/opea/chatqna:test
sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test | # restart containerd sudo systemctl restart containerd.service
# for test
docker pull opea/chatqna:latest
docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test
docker push 100.83.111.232:5000/opea/chatqna:test
sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
89b80745-c99c-4801-890c-fd74f72c6a49 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 3 | opea-semantic-v1 | a73490b7bb53b735 | ## Install Docker ```shell sudo apt update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin sudo systemctl enable docker.service sudo systemctl daemon-reload sudo systemctl start docker
### Troubleshooting Docker Installation
1. Issue: E: Unable to locate package docker-compose-plugin
*... | ai_ref_knowledge | OPEA Documentation | ## Install Docker ```shell sudo apt update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin sudo systemctl enable docker.service sudo systemctl daemon-reload sudo systemctl start docker
### Troubleshooting Docker Installation
1. Issue: E: Unable to locate package docker-compose-plugin
*... | ## Install Docker ```shell sudo apt update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin sudo systemctl enable docker.service sudo systemctl daemon-reload sudo systemctl start docker
### Troubleshooting Docker Installation
1. Issue: E: Unable to locate package docker-compose-plugin
*... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8edc2cf8-2a13-4be9-bab4-06ca261cccb6 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 26 | opea-semantic-v1 | 806eeca24ae37065 | Make sure you have installed k8s and helm charts in your test machine. ```shell NAMESPACE="opea-arc-systems" helm install arc \ --namespace "${NAMESPACE}" \ --create-namespace \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
helm uninstall arc -n $NAMESPACE
kubectl delete namespa... | ai_ref_knowledge | OPEA Documentation | Make sure you have installed k8s and helm charts in your test machine. ```shell NAMESPACE="opea-arc-systems" helm install arc \ --namespace "${NAMESPACE}" \ --create-namespace \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
helm uninstall arc -n $NAMESPACE
kubectl delete namespa... | Make sure you have installed k8s and helm charts in your test machine. ```shell NAMESPACE="opea-arc-systems" helm install arc \ --namespace "${NAMESPACE}" \ --create-namespace \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
helm uninstall arc -n $NAMESPACE
kubectl delete namespa... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
acab9d01-f666-4c11-8bc5-2f554f0be19b | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 14 | opea-semantic-v1 | f12c3065afa6cac9 | 2. Setup docker registry clean up cron. https://github.com/opea-project/Validation/blob/main/tools/image-registry/cleanup.sh 3. Setup connection to the local registry.
For docker:
```shell
cat /etc/docker/daemon.json
# gaudi:
{"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "... | ai_ref_knowledge | OPEA Documentation | 2. Setup docker registry clean up cron. https://github.com/opea-project/Validation/blob/main/tools/image-registry/cleanup.sh 3. Setup connection to the local registry.
For docker:
```shell
cat /etc/docker/daemon.json
# gaudi:
{"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "... | 2. Setup docker registry clean up cron. https://github.com/opea-project/Validation/blob/main/tools/image-registry/cleanup.sh 3. Setup connection to the local registry.
For docker:
```shell
cat /etc/docker/daemon.json
# gaudi:
{"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
bc679cc5-27b0-43d4-b0ac-1fe75233c5fd | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 28 | opea-semantic-v1 | 5d29e2c67b28b27e | group has been created in GHA. GITHUB_CONFIG_URL="https://github.com/opea-project" GITHUB_PAT="xxx" # the personal access token for GHA, which has the permission to create runners in the repo.
helm install "${RUNNER_SET_NAME}" \
--namespace "${RUNNERS_NAMESPACE}" \
--create-namespace \
-f xeon_large.yaml \
--set gi... | ai_ref_knowledge | OPEA Documentation | group has been created in GHA. GITHUB_CONFIG_URL="https://github.com/opea-project" GITHUB_PAT="xxx" # the personal access token for GHA, which has the permission to create runners in the repo.
helm install "${RUNNER_SET_NAME}" \
--namespace "${RUNNERS_NAMESPACE}" \
--create-namespace \
-f xeon_large.yaml \
--set gi... | group has been created in GHA. GITHUB_CONFIG_URL="https://github.com/opea-project" GITHUB_PAT="xxx" # the personal access token for GHA, which has the permission to create runners in the repo.
helm install "${RUNNER_SET_NAME}" \
--namespace "${RUNNERS_NAMESPACE}" \
--create-namespace \
-f xeon_large.yaml \
--set gi... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c9085274-989b-4599-a648-85e59187d0af | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 15 | opea-semantic-v1 | e18799b8b84ba9eb | For docker: ```shell cat /etc/docker/daemon.json # gaudi: {"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "default-runtime": "habana", "insecure-registries" : [ "100.83.111.232:5000" ]} # xeon: {"insecure-registries": ["100.83.111.232:5000"]}
# restart docker
sudo systemctl re... | ai_ref_knowledge | OPEA Documentation | For docker: ```shell cat /etc/docker/daemon.json # gaudi: {"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "default-runtime": "habana", "insecure-registries" : [ "100.83.111.232:5000" ]} # xeon: {"insecure-registries": ["100.83.111.232:5000"]}
# restart docker
sudo systemctl re... | For docker: ```shell cat /etc/docker/daemon.json # gaudi: {"runtimes": {"habana": {"path": "/usr/bin/habana-container-runtime", "runtimeArgs": []}}, "default-runtime": "habana", "insecure-registries" : [ "100.83.111.232:5000" ]} # xeon: {"insecure-registries": ["100.83.111.232:5000"]}
# restart docker
sudo systemctl re... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d60683fc-fb0c-4c88-8400-e7eca1a807be | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 6 | opea-semantic-v1 | 23a0b747e2c53b9c | 3. Issue: ulimit -n setting. [optional] **solution:** ```shell cat << EOF | tee /etc/systemd/system/containerd.service.d/override.conf [Service] LimitNOFILE=infinity EOF sudo systemctl restart containerd.service
4. Issue: control the maximum number of memory mapped areas that a process can have. [optional]
**solution:... | ai_ref_knowledge | OPEA Documentation | 3. Issue: ulimit -n setting. [optional] **solution:** ```shell cat << EOF | tee /etc/systemd/system/containerd.service.d/override.conf [Service] LimitNOFILE=infinity EOF sudo systemctl restart containerd.service
4. Issue: control the maximum number of memory mapped areas that a process can have. [optional]
**solution:... | 3. Issue: ulimit -n setting. [optional] **solution:** ```shell cat << EOF | tee /etc/systemd/system/containerd.service.d/override.conf [Service] LimitNOFILE=infinity EOF sudo systemctl restart containerd.service
4. Issue: control the maximum number of memory mapped areas that a process can have. [optional]
**solution:... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
da9bc6ec-b8cd-4872-942b-f44b6d9bb924 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 30 | opea-semantic-v1 | 6ec6f4510b8ea270 | with `kubectl label nodes opea-cicd-spr-0 runner-node=true` and use `kubectl get nodes --show-labels` to check the labels. d. Make sure you have `/data2` for model cache.
3. Clean up the ARC (If needed)
```shell
# clean up runner set
(
RUNNER_SET_NAME="xeon"
RUNNERS_NAMESPACE="opea-runner-set-c1"
helm uninstall $RUNNER... | ai_ref_knowledge | OPEA Documentation | with `kubectl label nodes opea-cicd-spr-0 runner-node=true` and use `kubectl get nodes --show-labels` to check the labels. d. Make sure you have `/data2` for model cache.
3. Clean up the ARC (If needed)
```shell
# clean up runner set
(
RUNNER_SET_NAME="xeon"
RUNNERS_NAMESPACE="opea-runner-set-c1"
helm uninstall $RUNNER... | with `kubectl label nodes opea-cicd-spr-0 runner-node=true` and use `kubectl get nodes --show-labels` to check the labels. d. Make sure you have `/data2` for model cache.
3. Clean up the ARC (If needed)
```shell
# clean up runner set
(
RUNNER_SET_NAME="xeon"
RUNNERS_NAMESPACE="opea-runner-set-c1"
helm uninstall $RUNNER... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
dd1d0a05-74dc-4603-8a11-f2cd8209efd3 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 24 | opea-semantic-v1 | 88d8852a604cfb4d | ## Setup GHA ENV for CI/CD 1. Setup self-hosed runner for GHA, follow official steps. 2. Setup ENV for GHA. ```shell vi ~/action_runner/.env OPEA_IMAGE_REPO=100.83.111.232:5000/
3. Start runner with svc. ```shell
sudo ./svc.sh install # use svc.sh instead of run.sh
sudo ./svc.sh start
sudo ./svc.sh status
sudo ./svc.... | ai_ref_knowledge | OPEA Documentation | ## Setup GHA ENV for CI/CD 1. Setup self-hosed runner for GHA, follow official steps. 2. Setup ENV for GHA. ```shell vi ~/action_runner/.env OPEA_IMAGE_REPO=100.83.111.232:5000/
3. Start runner with svc. ```shell
sudo ./svc.sh install # use svc.sh instead of run.sh
sudo ./svc.sh start
sudo ./svc.sh status
sudo ./svc.... | ## Setup GHA ENV for CI/CD 1. Setup self-hosed runner for GHA, follow official steps. 2. Setup ENV for GHA. ```shell vi ~/action_runner/.env OPEA_IMAGE_REPO=100.83.111.232:5000/
3. Start runner with svc. ```shell
sudo ./svc.sh install # use svc.sh instead of run.sh
sudo ./svc.sh start
sudo ./svc.sh status
sudo ./svc.... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ee013224-b402-4fed-96e2-cb287b9189ba | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 17 | opea-semantic-v1 | 262c84fe9b5fe0b2 | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test
For K8S:
```shell
# setup in client side
cat /etc/containerd/config.toml
... [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
[plugins."io.containerd.... | ai_ref_knowledge | OPEA Documentation | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test
For K8S:
```shell
# setup in client side
cat /etc/containerd/config.toml
... [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
[plugins."io.containerd.... | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test
For K8S:
```shell
# setup in client side
cat /etc/containerd/config.toml
... [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
[plugins."io.containerd.... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f781b844-1254-42c3-9573-829aafffd9e8 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 12 | opea-semantic-v1 | 97490b3851ecca54 | storage: cache: blobdescriptor: inmemory filesystem: rootdirectory: /var/lib/registry delete: enabled: true http: addr: :5000 headers: X-Content-Type-Options: [nosniff] health: storagedriver: enabled: true interval: 10s threshold: 3 EOF
cd /scratch-1 # place to store the images
mkdir local_image_registry && chmod -R 77... | ai_ref_knowledge | OPEA Documentation | storage: cache: blobdescriptor: inmemory filesystem: rootdirectory: /var/lib/registry delete: enabled: true http: addr: :5000 headers: X-Content-Type-Options: [nosniff] health: storagedriver: enabled: true interval: 10s threshold: 3 EOF
cd /scratch-1 # place to store the images
mkdir local_image_registry && chmod -R 77... | storage: cache: blobdescriptor: inmemory filesystem: rootdirectory: /var/lib/registry delete: enabled: true http: addr: :5000 headers: X-Content-Type-Options: [nosniff] health: storagedriver: enabled: true interval: 10s threshold: 3 EOF
cd /scratch-1 # place to store the images
mkdir local_image_registry && chmod -R 77... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f81ce0cb-5a80-4cf5-a484-3540017b4d0a | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 21 | opea-semantic-v1 | fc5fc5a820186bd8 | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test
4. Setup ENV for CI/CD. ```shell
vi .bashrc
export OPEA_IMAGE_REPO=100.83.111.232:5000/ | ai_ref_knowledge | OPEA Documentation | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test
4. Setup ENV for CI/CD. ```shell
vi .bashrc
export OPEA_IMAGE_REPO=100.83.111.232:5000/ | # for test docker pull opea/chatqna:latest docker tag opea/chatqna:latest 100.83.111.232:5000/opea/chatqna:test docker push 100.83.111.232:5000/opea/chatqna:test sudo nerdctl -n k8s.io pull 100.83.111.232:5000/opea/chatqna:test
4. Setup ENV for CI/CD. ```shell
vi .bashrc
export OPEA_IMAGE_REPO=100.83.111.232:5000/ | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fa522321-5c5c-495d-9fbd-5294eded55ef | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 2 | opea-semantic-v1 | 9d05424621028e19 | ## Install Habana Driver (Gaudi Only) 1. Driver and software installation https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html 2. Firmware upgrade https://docs.habana.ai/en/latest/Installation_Guide/Firmware_Upgrade.html
## Install Docker
```shell
sudo apt update
sudo apt-get install docker-ce... | ai_ref_knowledge | OPEA Documentation | ## Install Habana Driver (Gaudi Only) 1. Driver and software installation https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html 2. Firmware upgrade https://docs.habana.ai/en/latest/Installation_Guide/Firmware_Upgrade.html
## Install Docker
```shell
sudo apt update
sudo apt-get install docker-ce... | ## Install Habana Driver (Gaudi Only) 1. Driver and software installation https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html 2. Firmware upgrade https://docs.habana.ai/en/latest/Installation_Guide/Firmware_Upgrade.html
## Install Docker
```shell
sudo apt update
sudo apt-get install docker-ce... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fdcec34f-52ae-45db-885d-fcbebc83d4c5 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 19 | opea-semantic-v1 | b7bd10cfab2288a5 | cd /etc/containerd sudo mkdir -p certs.d/100.83.111.232:5000 cd certs.d/100.83.111.232:5000 cat << EOF | sudo tee hosts.toml server = "http://100.83.111.232:5000" [host."http://100.83.111.232:5000"] capabilities = ["pull", "resolve", "push"] EOF
# restart containerd
sudo systemctl restart containerd.service | ai_ref_knowledge | OPEA Documentation | cd /etc/containerd sudo mkdir -p certs.d/100.83.111.232:5000 cd certs.d/100.83.111.232:5000 cat << EOF | sudo tee hosts.toml server = "http://100.83.111.232:5000" [host."http://100.83.111.232:5000"] capabilities = ["pull", "resolve", "push"] EOF
# restart containerd
sudo systemctl restart containerd.service | cd /etc/containerd sudo mkdir -p certs.d/100.83.111.232:5000 cd certs.d/100.83.111.232:5000 cat << EOF | sudo tee hosts.toml server = "http://100.83.111.232:5000" [host."http://100.83.111.232:5000"] capabilities = ["pull", "resolve", "push"] EOF
# restart containerd
sudo systemctl restart containerd.service | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ff88539b-a5f2-4cb0-9c1c-5b53b06430f4 | OPEA Documentation | file://datasets/opea-docs/guide/cicd/setup_cicd_env.md | unknown | 34529bab-8f69-469c-a761-118b9ac9a218 | 25 | opea-semantic-v1 | 70be4b47fe3abd97 | 3. Start runner with svc. ```shell sudo ./svc.sh install # use svc.sh instead of run.sh sudo ./svc.sh start sudo ./svc.sh status sudo ./svc.sh stop
## Setup Action Runner Controller (ARC)
https://docs.github.com/en/actions/tutorials/quickstart-for-actions-runner-controller
For now, we only support use ARC on Xeon K8S ... | ai_ref_knowledge | OPEA Documentation | 3. Start runner with svc. ```shell sudo ./svc.sh install # use svc.sh instead of run.sh sudo ./svc.sh start sudo ./svc.sh status sudo ./svc.sh stop
## Setup Action Runner Controller (ARC)
https://docs.github.com/en/actions/tutorials/quickstart-for-actions-runner-controller
For now, we only support use ARC on Xeon K8S ... | 3. Start runner with svc. ```shell sudo ./svc.sh install # use svc.sh instead of run.sh sudo ./svc.sh start sudo ./svc.sh status sudo ./svc.sh stop
## Setup Action Runner Controller (ARC)
https://docs.github.com/en/actions/tutorials/quickstart-for-actions-runner-controller
For now, we only support use ARC on Xeon K8S ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0a2222fe-1143-49cf-bb9c-32a1faac4e59 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 4 | opea-semantic-v1 | 9a17a3c33ac6aaf3 | **Prerequisites**
- For the ChatQnA example ensure your cluster has a running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to:
["Kubernetes installation"](../k8s_install/README.md) | ai_ref_knowledge | OPEA Documentation | **Prerequisites**
- For the ChatQnA example ensure your cluster has a running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to:
["Kubernetes installation"](../k8s_install/README.md) | **Prerequisites**
- For the ChatQnA example ensure your cluster has a running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to:
["Kubernetes installation"](../k8s_install/README.md) | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1c056271-e3e3-42a0-9cb9-8388d14905e0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 14 | opea-semantic-v1 | c79e55ecf7023e71 | ```sh kubectl get pods -n system NAME READY STATUS RESTARTS AGE gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m
## Use GMC to compose a chatQnA Pipeline
A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml | ai_ref_knowledge | OPEA Documentation | ```sh kubectl get pods -n system NAME READY STATUS RESTARTS AGE gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m
## Use GMC to compose a chatQnA Pipeline
A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml | ```sh kubectl get pods -n system NAME READY STATUS RESTARTS AGE gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m
## Use GMC to compose a chatQnA Pipeline
A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1df34cc5-7c54-4442-957a-f1365798bed0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 13 | opea-semantic-v1 | d3f4975b3a9fa119 | **Check the installation result**
```sh
kubectl get pods -n system
NAME READY STATUS RESTARTS AGE
gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m | ai_ref_knowledge | OPEA Documentation | **Check the installation result**
```sh
kubectl get pods -n system
NAME READY STATUS RESTARTS AGE
gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m | **Check the installation result**
```sh
kubectl get pods -n system
NAME READY STATUS RESTARTS AGE
gmc-controller-78f9c748cb-ltcdv 1/1 Running 0 3m | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2fd17f3c-f061-4fb8-a30f-43d47576c286 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 11 | opea-semantic-v1 | 330711c095af28b1 | ```sh kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests
**NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap. | ai_ref_knowledge | OPEA Documentation | ```sh kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests
**NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap. | ```sh kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests
**NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
35aa1df7-335a-46a0-a7a8-96edca99e5a6 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 17 | opea-semantic-v1 | 1ad362d4f3de64f5 | **Check GMC chatQnA custom resource to get access URL for the pipeline**
```bash
$kubectl get gmconnectors.gmc.opea.io -n chatqa
NAME URL READY AGE
chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m | ai_ref_knowledge | OPEA Documentation | **Check GMC chatQnA custom resource to get access URL for the pipeline**
```bash
$kubectl get gmconnectors.gmc.opea.io -n chatqa
NAME URL READY AGE
chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m | **Check GMC chatQnA custom resource to get access URL for the pipeline**
```bash
$kubectl get gmconnectors.gmc.opea.io -n chatqa
NAME URL READY AGE
chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4b1ff636-2e8a-42c9-8518-9c876e97b519 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 20 | opea-semantic-v1 | d5f49dbca1e6cbe4 | ```bash kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity
**Access the pipeline using the above URL from the client pod** | ai_ref_knowledge | OPEA Documentation | ```bash kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity
**Access the pipeline using the above URL from the client pod** | ```bash kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity
**Access the pipeline using the above URL from the client pod** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4cea2e02-43e9-49f7-a6cd-98551a60fa74 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 2 | opea-semantic-v1 | c05bc347c3d21a27 | ## GenAI-microservices-connector(GMC)
GMC can be used to compose and adjust GenAI pipelines dynamically on Kubernetes. It can leverage the microservices provided by GenAIComps and external services to compose GenAI pipelines. External services might be running in a public cloud or on-prem. Just provide an URL and acces... | ai_ref_knowledge | OPEA Documentation | ## GenAI-microservices-connector(GMC)
GMC can be used to compose and adjust GenAI pipelines dynamically on Kubernetes. It can leverage the microservices provided by GenAIComps and external services to compose GenAI pipelines. External services might be running in a public cloud or on-prem. Just provide an URL and acces... | ## GenAI-microservices-connector(GMC)
GMC can be used to compose and adjust GenAI pipelines dynamically on Kubernetes. It can leverage the microservices provided by GenAIComps and external services to compose GenAI pipelines. External services might be running in a public cloud or on-prem. Just provide an URL and acces... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5cb773d8-12fd-4d90-af8b-980789feaeeb | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 3 | opea-semantic-v1 | 0c2b519cf463af66 | functions into the chain(like adding guardrails), etc. GMC supports different types of steps in the pipeline, like sequential, parallel and conditional. For more information: https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector
## Install GMC | ai_ref_knowledge | OPEA Documentation | functions into the chain(like adding guardrails), etc. GMC supports different types of steps in the pipeline, like sequential, parallel and conditional. For more information: https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector
## Install GMC | functions into the chain(like adding guardrails), etc. GMC supports different types of steps in the pipeline, like sequential, parallel and conditional. For more information: https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector
## Install GMC | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
60fe74e6-5d8a-48bb-a0d8-45e8e6934f53 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 7 | opea-semantic-v1 | a9b80d5bdfe610d0 | access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands don’t work.
**Install GMC CRD** | ai_ref_knowledge | OPEA Documentation | access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands don’t work.
**Install GMC CRD** | access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands don’t work.
**Install GMC CRD** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a7200766-392f-4105-99be-73fcd1e18282 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 18 | opea-semantic-v1 | 8432596fd99aedbf | ```bash $kubectl get gmconnectors.gmc.opea.io -n chatqa NAME URL READY AGE chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m
**Deploy one client pod for testing the chatQnA application** | ai_ref_knowledge | OPEA Documentation | ```bash $kubectl get gmconnectors.gmc.opea.io -n chatqa NAME URL READY AGE chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m
**Deploy one client pod for testing the chatQnA application** | ```bash $kubectl get gmconnectors.gmc.opea.io -n chatqa NAME URL READY AGE chatqa http://router-service.chatqa.svc.cluster.local:8080 8/0/8 3m
**Deploy one client pod for testing the chatQnA application** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a75d53eb-bd06-45e3-8927-86aeb390ea9c | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 1 | opea-semantic-v1 | cd5ebab8a3be8b2f | will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities.
## GenAI-microservices-connector(GMC) | ai_ref_knowledge | OPEA Documentation | will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities.
## GenAI-microservices-connector(GMC) | will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities.
## GenAI-microservices-connector(GMC) | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b4040c4f-c70e-4e74-94b0-2e9153ad4e0b | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 16 | opea-semantic-v1 | 677a9c5f25578db0 | ```sh kubectl create ns chatqa kubectl apply -f $(pwd)/config/samples/chatQnA_xeon.yaml
**GMC will reconcile chatQnA custom resource and get all related components/services ready** | ai_ref_knowledge | OPEA Documentation | ```sh kubectl create ns chatqa kubectl apply -f $(pwd)/config/samples/chatQnA_xeon.yaml
**GMC will reconcile chatQnA custom resource and get all related components/services ready** | ```sh kubectl create ns chatqa kubectl apply -f $(pwd)/config/samples/chatQnA_xeon.yaml
**GMC will reconcile chatQnA custom resource and get all related components/services ready** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
bdf9d82b-7b79-4919-adf3-22dfa24ae787 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 8 | opea-semantic-v1 | eaa4afe125c59816 | ```sh export SYSTEM_NAMESPACE=system kubectl create namespace $SYSTEM_NAMESPACE
**NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml. | ai_ref_knowledge | OPEA Documentation | ```sh export SYSTEM_NAMESPACE=system kubectl create namespace $SYSTEM_NAMESPACE
**NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml. | ```sh export SYSTEM_NAMESPACE=system kubectl create namespace $SYSTEM_NAMESPACE
**NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c0d6a3e4-b88c-48e8-867c-63401043b455 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 10 | opea-semantic-v1 | cda3f897eeb7207f | **Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests**
```sh
kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests | ai_ref_knowledge | OPEA Documentation | **Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests**
```sh
kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests | **Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests**
```sh
kubectl create configmap gmcyaml -n $SYSTEM_NAMESPACE --from-file $(pwd)/config/manifests | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c6d4c4bb-6ba3-4d4c-8f70-d2b28d79feed | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 0 | opea-semantic-v1 | 94a2efc4d3071830 | # GenAI-microservices-connector(GMC) Installation
This document will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities. | ai_ref_knowledge | OPEA Documentation | # GenAI-microservices-connector(GMC) Installation
This document will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities. | # GenAI-microservices-connector(GMC) Installation
This document will introduce the GenAI Microservices Connector (GMC) and its installation. It will then use the ChatQnA pipeline as a use case to demonstrate GMC's functionalities. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d2760e72-7a57-496f-a411-dbfbdf8dbff9 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 6 | opea-semantic-v1 | c9a26352ad612599 | ```sh make docker.build docker.push CTR_IMG=<some-registry>/gmcmanager:<tag>
**NOTE:** This image will be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands do... | ai_ref_knowledge | OPEA Documentation | ```sh make docker.build docker.push CTR_IMG=<some-registry>/gmcmanager:<tag>
**NOTE:** This image will be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands do... | ```sh make docker.build docker.push CTR_IMG=<some-registry>/gmcmanager:<tag>
**NOTE:** This image will be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permissions to the registry if the above commands do... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d28b468b-73cc-464b-ac4a-2769dbd18a4a | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 12 | opea-semantic-v1 | b37352435b50ac69 | **NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap.
**Install GMC manager** | ai_ref_knowledge | OPEA Documentation | **NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap.
**Install GMC manager** | **NOTE:** The configmap name `gmcyaml' is defined in gmcmanager deployment Spec. Please modify accordingly if you want use a different name for the configmap.
**Install GMC manager** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d8efcbbd-c5df-4c8e-bafc-80d7ee7c0526 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 15 | opea-semantic-v1 | 96b00b52e3303929 | ## Use GMC to compose a chatQnA Pipeline A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml
**Deploy chatQnA GMC custom resource** | ai_ref_knowledge | OPEA Documentation | ## Use GMC to compose a chatQnA Pipeline A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml
**Deploy chatQnA GMC custom resource** | ## Use GMC to compose a chatQnA Pipeline A sample for chatQnA can be found at config/samples/chatQnA_xeon.yaml
**Deploy chatQnA GMC custom resource** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
db700f22-174f-4700-9d56-713e96aa15a8 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 5 | opea-semantic-v1 | 816071b178dc74dc | running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to: ["Kubernetes installation"](../k8s_install/README.md)
**Download the GMC github repository** | ai_ref_knowledge | OPEA Documentation | running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to: ["Kubernetes installation"](../k8s_install/README.md)
**Download the GMC github repository** | running Kubernetes cluster with at least 16 CPUs, 32GB of memory, and 100GB of disk space. To install a Kubernetes cluster refer to: ["Kubernetes installation"](../k8s_install/README.md)
**Download the GMC github repository** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e230a965-e85d-47f0-87ca-9078987ffded | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 9 | opea-semantic-v1 | d2cd201e1313a712 | **NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml.
**Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests** | ai_ref_knowledge | OPEA Documentation | **NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml.
**Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests** | **NOTE:** Please use the exact same `SYSTEM_NAMESPACE` value setting you used while deploying gmc-manager.yaml and gmc-manager-rbac.yaml.
**Create ConfigMap for GMC to hold GenAI Components and GMC Router manifests** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e53464d9-0eb2-48e1-84d1-5431cef01419 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 21 | opea-semantic-v1 | e3b0b843dae7b91b | **Access the pipeline using the above URL from the client pod**
```bash
export CLIENT_POD=$(kubectl get pod -n chatqa -l app=client-test -o jsonpath={.items..metadata.name})
export accessUrl=$(kubectl get gmc -n chatqa -o jsonpath="{.items[?(@.metadata.name=='chatqa')].status.accessUrl}")
kubectl exec "$CLIENT_POD" -n ... | ai_ref_knowledge | OPEA Documentation | **Access the pipeline using the above URL from the client pod**
```bash
export CLIENT_POD=$(kubectl get pod -n chatqa -l app=client-test -o jsonpath={.items..metadata.name})
export accessUrl=$(kubectl get gmc -n chatqa -o jsonpath="{.items[?(@.metadata.name=='chatqa')].status.accessUrl}")
kubectl exec "$CLIENT_POD" -n ... | **Access the pipeline using the above URL from the client pod**
```bash
export CLIENT_POD=$(kubectl get pod -n chatqa -l app=client-test -o jsonpath={.items..metadata.name})
export accessUrl=$(kubectl get gmc -n chatqa -o jsonpath="{.items[?(@.metadata.name=='chatqa')].status.accessUrl}")
kubectl exec "$CLIENT_POD" -n ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fbebd5d7-0982-40e7-ae0b-6d4a70ba12a1 | OPEA Documentation | file://datasets/opea-docs/guide/installation/gmc_install/gmc_install.md | unknown | 01d9e620-3d0a-4476-9e3f-57c5b8c89d3d | 19 | opea-semantic-v1 | f7893e076eb621c5 | **Deploy one client pod for testing the chatQnA application**
```bash
kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity | ai_ref_knowledge | OPEA Documentation | **Deploy one client pod for testing the chatQnA application**
```bash
kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity | **Deploy one client pod for testing the chatQnA application**
```bash
kubectl create deployment client-test -n chatqa --image=python:3.8.13 -- sleep infinity | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
99c32219-1bbc-45e9-98c3-bfeed6faced2 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/README.md | unknown | 7128805b-23bd-43e4-b80d-01599b40d915 | 0 | opea-semantic-v1 | a78f8000d45d4e29 | Here are a variety of ways to install Kubernetes:
* [Using AWS EKS Cluster](k8s_instal_aws_eks.md)
* [Using kubeadm](k8s_install_kubeadm.md)
* [Using Kubespray](k8s_install_kubespray.md) | ai_ref_knowledge | OPEA Documentation | Here are a variety of ways to install Kubernetes:
* [Using AWS EKS Cluster](k8s_instal_aws_eks.md)
* [Using kubeadm](k8s_install_kubeadm.md)
* [Using Kubespray](k8s_install_kubespray.md) | Here are a variety of ways to install Kubernetes:
* [Using AWS EKS Cluster](k8s_instal_aws_eks.md)
* [Using kubeadm](k8s_install_kubeadm.md)
* [Using Kubespray](k8s_install_kubespray.md) | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
01c2798d-45bf-48c6-beee-3d46805a9d17 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 2 | opea-semantic-v1 | bf1f03c67984c659 | ## Prerequisites
Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster. | ai_ref_knowledge | OPEA Documentation | ## Prerequisites
Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster. | ## Prerequisites
Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0d8822d0-21a0-4740-bd2e-89c36b9b6d6a | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 17 | opea-semantic-v1 | 39d1445ee6ba2a4e | docker build -t my-app:<tag> .
4. Tag your Docker image so that it can be pushed to your ECR repository: | ai_ref_knowledge | OPEA Documentation | docker build -t my-app:<tag> .
4. Tag your Docker image so that it can be pushed to your ECR repository: | docker build -t my-app:<tag> .
4. Tag your Docker image so that it can be pushed to your ECR repository: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
22d11e1e-990c-4d86-bf61-eaadcd403524 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 1 | opea-semantic-v1 | 1bc689cb3170e7e8 | There are two ways to create a new Kubernetes cluster with nodes in AWS EKS: - ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html) - ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html).
In this document, we'll introdu... | ai_ref_knowledge | OPEA Documentation | There are two ways to create a new Kubernetes cluster with nodes in AWS EKS: - ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html) - ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html).
In this document, we'll introdu... | There are two ways to create a new Kubernetes cluster with nodes in AWS EKS: - ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html) - ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html).
In this document, we'll introdu... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
235a5f13-609e-4390-a71e-34d8228ce7ca | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 16 | opea-semantic-v1 | b9ee109767549c6c | aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <account_id>.dkr.ecr.<region>.amazonaws.com
Replace <region> with your AWS region and <account_id> with your AWS account ID. | ai_ref_knowledge | OPEA Documentation | aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <account_id>.dkr.ecr.<region>.amazonaws.com
Replace <region> with your AWS region and <account_id> with your AWS account ID. | aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <account_id>.dkr.ecr.<region>.amazonaws.com
Replace <region> with your AWS region and <account_id> with your AWS account ID. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
28caf383-9219-4111-9216-04f594174c1c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 7 | opea-semantic-v1 | c1d2387386f77a29 | ## Create AWS EKS Cluster in AWS Console
You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console:
https://www.youtube.com/watch?v=KxxgF-DAGWc | ai_ref_knowledge | OPEA Documentation | ## Create AWS EKS Cluster in AWS Console
You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console:
https://www.youtube.com/watch?v=KxxgF-DAGWc | ## Create AWS EKS Cluster in AWS Console
You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console:
https://www.youtube.com/watch?v=KxxgF-DAGWc | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2956216e-159f-4ee3-a76d-ce3d76944248 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 14 | opea-semantic-v1 | 461a0bd34edc8b0e | aws ecr create-repository --repository-name my-app-repo --region <region>
Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1). | ai_ref_knowledge | OPEA Documentation | aws ecr create-repository --repository-name my-app-repo --region <region>
Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1). | aws ecr create-repository --repository-name my-app-repo --region <region>
Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1). | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
453936db-0624-47e0-946f-90a4cf7d5d68 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 19 | opea-semantic-v1 | 42ac548c642d49c5 | Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name.
5. Push your Docker image to the ECR repository with this command: | ai_ref_knowledge | OPEA Documentation | Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name.
5. Push your Docker image to the ECR repository with this command: | Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name.
5. Push your Docker image to the ECR repository with this command: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
523a7254-d7f7-474a-b55a-a1234dc40826 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 5 | opea-semantic-v1 | 9e38738307ceb33c | - kubectl – A command line tool for working with Kubernetes clusters. For more information, see ["Installing or updating kubectl"](https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html).
- Required IAM permissions – The IAM security principal that you're using must have permissions to work with Amazon E... | ai_ref_knowledge | OPEA Documentation | - kubectl – A command line tool for working with Kubernetes clusters. For more information, see ["Installing or updating kubectl"](https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html).
- Required IAM permissions – The IAM security principal that you're using must have permissions to work with Amazon E... | - kubectl – A command line tool for working with Kubernetes clusters. For more information, see ["Installing or updating kubectl"](https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html).
- Required IAM permissions – The IAM security principal that you're using must have permissions to work with Amazon E... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
58b33bb9-2487-494f-8c55-36407cea7aee | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 13 | opea-semantic-v1 | 245f87c2890e5538 | Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html
aws ecr create-repository --repository-name my-app-repo --region... | ai_ref_knowledge | OPEA Documentation | Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html
aws ecr create-repository --repository-name my-app-repo --region... | Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html
aws ecr create-repository --repository-name my-app-repo --region... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
68b9f50c-d155-4a22-b8bb-b606fb49dd65 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 18 | opea-semantic-v1 | a412daba8a75cdcd | docker tag my-app:<tag> <account_id>.dkr.ecr.<region>.amazonaws.com/my-app-repo:<tag>
Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name. | ai_ref_knowledge | OPEA Documentation | docker tag my-app:<tag> <account_id>.dkr.ecr.<region>.amazonaws.com/my-app-repo:<tag>
Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name. | docker tag my-app:<tag> <account_id>.dkr.ecr.<region>.amazonaws.com/my-app-repo:<tag>
Replace <account_id> with your AWS account ID, <region> with your AWS region, and my-app-repo with your repository name. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6d7dc08b-2fdb-4d16-8b1a-2feb35309d51 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 3 | opea-semantic-v1 | 860d73d8a274eee2 | Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster.
- AWS CLI – A command line tool for working with AWS services, including Amazon EKS. For more information, see ["Installing, updating, and uninstalling the AWS CLI"](... | ai_ref_knowledge | OPEA Documentation | Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster.
- AWS CLI – A command line tool for working with AWS services, including Amazon EKS. For more information, see ["Installing, updating, and uninstalling the AWS CLI"](... | Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster.
- AWS CLI – A command line tool for working with AWS services, including Amazon EKS. For more information, see ["Installing, updating, and uninstalling the AWS CLI"](... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
72ab28ea-4cf8-4397-8e30-af6f35cc83ad | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 4 | opea-semantic-v1 | 77e3e938bddfed6c | CLI, we recommend that you also configure it. For more information, see ["Quick configuration with aws configure"](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html#cli-configure-quickstart-config) in the AWS Command Line Interface User Guide.
- kubectl – A command line tool for working with Kube... | ai_ref_knowledge | OPEA Documentation | CLI, we recommend that you also configure it. For more information, see ["Quick configuration with aws configure"](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html#cli-configure-quickstart-config) in the AWS Command Line Interface User Guide.
- kubectl – A command line tool for working with Kube... | CLI, we recommend that you also configure it. For more information, see ["Quick configuration with aws configure"](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html#cli-configure-quickstart-config) in the AWS Command Line Interface User Guide.
- kubectl – A command line tool for working with Kube... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7d388c34-e9b0-4499-affb-5296a6c8c43c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 12 | opea-semantic-v1 | 4b7f0d7b08203fec | 1. Create a new ECR repository (if not already created):
An Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html | ai_ref_knowledge | OPEA Documentation | 1. Create a new ECR repository (if not already created):
An Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html | 1. Create a new ECR repository (if not already created):
An Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. More information about Amazon ECR private repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
878ba160-087c-40d6-90e0-99791ba5d97b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 10 | opea-semantic-v1 | dd453d01e567dfb4 | ## Uploading images to an AWS Private Registry
There are several reasons why your images might not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps: | ai_ref_knowledge | OPEA Documentation | ## Uploading images to an AWS Private Registry
There are several reasons why your images might not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps: | ## Uploading images to an AWS Private Registry
There are several reasons why your images might not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
acf3dbe2-33c2-4bea-87c2-84a1d5b3bf24 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 9 | opea-semantic-v1 | cc00679747b2f1fd | the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html) or the AWS workshop to to learn how to create an EKS cluster at https://www.eksworkshop.com/
## Uploading images to an AWS Private Registry | ai_ref_knowledge | OPEA Documentation | the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html) or the AWS workshop to to learn how to create an EKS cluster at https://www.eksworkshop.com/
## Uploading images to an AWS Private Registry | the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html) or the AWS workshop to to learn how to create an EKS cluster at https://www.eksworkshop.com/
## Uploading images to an AWS Private Registry | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b459984b-18a2-4c6b-931a-7c904dc33289 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 8 | opea-semantic-v1 | 60211e5d44344d90 | You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console: https://www.youtube.com/watch?v=KxxgF-DAGWc
Alternatively, you can refer to the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-... | ai_ref_knowledge | OPEA Documentation | You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console: https://www.youtube.com/watch?v=KxxgF-DAGWc
Alternatively, you can refer to the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-... | You can refer to the YouTube video that demonstrates the steps to create an EKS cluster in the AWS console: https://www.youtube.com/watch?v=KxxgF-DAGWc
Alternatively, you can refer to the AWS documentation directly: ["AWS Management Console and AWS CLI"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d4c750de-179e-4704-b504-8a9924c312f5 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 0 | opea-semantic-v1 | 9005aca2e11fb091 | In this document, we'll install Kubernetes v1.30 using [AWS EKS Cluster](https://docs.aws.amazon.com/eks/latest/userguide/clusters.html).
There are two ways to create a new Kubernetes cluster with nodes in AWS EKS:
- ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html)
- ["AWS Manage... | ai_ref_knowledge | OPEA Documentation | In this document, we'll install Kubernetes v1.30 using [AWS EKS Cluster](https://docs.aws.amazon.com/eks/latest/userguide/clusters.html).
There are two ways to create a new Kubernetes cluster with nodes in AWS EKS:
- ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html)
- ["AWS Manage... | In this document, we'll install Kubernetes v1.30 using [AWS EKS Cluster](https://docs.aws.amazon.com/eks/latest/userguide/clusters.html).
There are two ways to create a new Kubernetes cluster with nodes in AWS EKS:
- ["eksctl"](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html)
- ["AWS Manage... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d9ad9141-d4d1-45b0-8843-596f9fc7c775 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 6 | opea-semantic-v1 | 4fcfea77fa82f016 | the IAM User Guide. You must complete all steps in this guide as the same user. To check the current user, run the following command:
aws sts get-caller-identity | ai_ref_knowledge | OPEA Documentation | the IAM User Guide. You must complete all steps in this guide as the same user. To check the current user, run the following command:
aws sts get-caller-identity | the IAM User Guide. You must complete all steps in this guide as the same user. To check the current user, run the following command:
aws sts get-caller-identity | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e19b9608-762d-47d2-bec9-dd487d44cf0b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 11 | opea-semantic-v1 | 0a91a0c27ff385a7 | not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps:
1. Create a new ECR repository (if not already created): | ai_ref_knowledge | OPEA Documentation | not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps:
1. Create a new ECR repository (if not already created): | not be uploaded to a public image repository like Docker Hub. You can upload your image to an AWS private registry using the following steps:
1. Create a new ECR repository (if not already created): | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
efb161a1-d307-4a30-bebf-4b10d8999172 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_instal_aws_eks.md | unknown | 8f1cd499-b2f8-4efa-a686-7de5475276a8 | 15 | opea-semantic-v1 | f24c86cc8a13ed35 | Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1).
2. Authenticate Docker to Your ECR Registry： | ai_ref_knowledge | OPEA Documentation | Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1).
2. Authenticate Docker to Your ECR Registry： | Replace my-app-repo with your desired repository name and <region> with your AWS region (e.g., us-west-1).
2. Authenticate Docker to Your ECR Registry： | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
03faf284-77eb-4bf5-bd9b-e3a7ee4024b0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 4 | opea-semantic-v1 | c3bb2b711ea709a8 | these 2 nodes have been set correctly with the corresponding proxy so we can access the internet both in bash terminal and in apt repository.
## Step 0. Clean up the environment | ai_ref_knowledge | OPEA Documentation | these 2 nodes have been set correctly with the corresponding proxy so we can access the internet both in bash terminal and in apt repository.
## Step 0. Clean up the environment | these 2 nodes have been set correctly with the corresponding proxy so we can access the internet both in bash terminal and in apt repository.
## Step 0. Clean up the environment | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0f5b45fc-4150-42fc-9306-6f057a4d5460 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 0 | opea-semantic-v1 | 106608bba8e1e433 | # Kubernetes installation demo using kubeadm
In this demo, we'll install Kubernetes v1.32 using official [kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/) on a 2 node cluster. | ai_ref_knowledge | OPEA Documentation | # Kubernetes installation demo using kubeadm
In this demo, we'll install Kubernetes v1.32 using official [kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/) on a 2 node cluster. | # Kubernetes installation demo using kubeadm
In this demo, we'll install Kubernetes v1.32 using official [kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/) on a 2 node cluster. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
184f852f-e17b-4e27-a771-c23765b8cdbd | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 37 | opea-semantic-v1 | 6e48d02668910aa5 | 3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands:
```bash
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
# install bash-completion for kubectl
sudo apt-get install -y bash-completion
kubectl ... | ai_ref_knowledge | OPEA Documentation | 3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands:
```bash
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
# install bash-completion for kubectl
sudo apt-get install -y bash-completion
kubectl ... | 3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands:
```bash
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
# install bash-completion for kubectl
sudo apt-get install -y bash-completion
kubectl ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
199b2b7f-db40-4425-83ab-0c50d65207d1 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 7 | opea-semantic-v1 | c91182e0fc17eb79 | there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) first.
If there is any previous Kubernetes installed on any of these node... | ai_ref_knowledge | OPEA Documentation | there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) first.
If there is any previous Kubernetes installed on any of these node... | there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) first.
If there is any previous Kubernetes installed on any of these node... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1b5a37ef-abf1-4d4b-893f-71a536302694 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 30 | opea-semantic-v1 | 162662b23260a1d7 | Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user: | ai_ref_knowledge | OPEA Documentation | Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user: | Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1c69efde-c140-40a0-831f-7c2894019efd | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 32 | opea-semantic-v1 | b859aab59b7c2f4c | mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run: | ai_ref_knowledge | OPEA Documentation | mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run: | mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1f9812da-94b9-4b6b-abc7-68f312db1001 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 66 | opea-semantic-v1 | 90d24d95f520859b | --- 192.168.121.133 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.339/1.339/1.339/0.000 ms
Delete debug pods after use: | ai_ref_knowledge | OPEA Documentation | --- 192.168.121.133 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.339/1.339/1.339/0.000 ms
Delete debug pods after use: | --- 192.168.121.133 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.339/1.339/1.339/0.000 ms
Delete debug pods after use: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2109fd58-9ea5-452b-9fa1-75cc497d01ab | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 34 | opea-semantic-v1 | f3c05dea7fe8e18b | You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: https://kubernetes.io/docs/concepts/cluster-administration/addons/
Then you can join any number of worker nodes by running the following on each as root: | ai_ref_knowledge | OPEA Documentation | You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: https://kubernetes.io/docs/concepts/cluster-administration/addons/
Then you can join any number of worker nodes by running the following on each as root: | You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: https://kubernetes.io/docs/concepts/cluster-administration/addons/
Then you can join any number of worker nodes by running the following on each as root: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
23ad8b89-099d-40bc-aacb-564e9c9b2911 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 61 | opea-semantic-v1 | e2c92340ca09dfb9 | `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7gsdc` on node k8s-worker1 to verify east-west traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 10.244.194.66
PING 10.244.194.66 (10.244.194.66) 56(84) bytes of data. 64 ... | ai_ref_knowledge | OPEA Documentation | `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7gsdc` on node k8s-worker1 to verify east-west traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 10.244.194.66
PING 10.244.194.66 (10.244.194.66) 56(84) bytes of data. 64 ... | `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7gsdc` on node k8s-worker1 to verify east-west traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 10.244.194.66
PING 10.244.194.66 (10.244.194.66) 56(84) bytes of data. 64 ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
24b1bf87-1c6b-4609-8f53-e55845809a03 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 38 | opea-semantic-v1 | 18750f91c6cf02a3 | /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config # install bash-completion for kubectl sudo apt-get install -y bash-completion kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl
4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands: | ai_ref_knowledge | OPEA Documentation | /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config # install bash-completion for kubectl sudo apt-get install -y bash-completion kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl
4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands: | /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config # install bash-completion for kubectl sudo apt-get install -y bash-completion kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl
4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
25572e4b-6cf8-4b55-864d-4d460817c219 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 48 | opea-semantic-v1 | 236dd32ac1f53a38 | 25m kube-system kube-proxy-jbd6r 1/1 Running 0 2m7s kube-system kube-proxy-lrgb6 1/1 Running 0 25m kube-system kube-scheduler-k8s-master 1/1 Running 0 25m tigera-operator tigera-operator-76c4974c85-lx79h 1/1 Running 0 10m
Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should... | ai_ref_knowledge | OPEA Documentation | 25m kube-system kube-proxy-jbd6r 1/1 Running 0 2m7s kube-system kube-proxy-lrgb6 1/1 Running 0 25m kube-system kube-scheduler-k8s-master 1/1 Running 0 25m tigera-operator tigera-operator-76c4974c85-lx79h 1/1 Running 0 10m
Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should... | 25m kube-system kube-proxy-jbd6r 1/1 Running 0 2m7s kube-system kube-proxy-lrgb6 1/1 Running 0 25m kube-system kube-scheduler-k8s-master 1/1 Running 0 25m tigera-operator tigera-operator-76c4974c85-lx79h 1/1 Running 0 10m
Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
27049fc0-4b6b-4425-8812-c13f763d85cf | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 49 | opea-semantic-v1 | 70a3f4828ccc9849 | Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should be something like:
vagrant@k8s-master:~$ kubectl get node -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <n... | ai_ref_knowledge | OPEA Documentation | Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should be something like:
vagrant@k8s-master:~$ kubectl get node -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <n... | Run command `kubectl get node` to make sure all node are in 'Ready' status. Possible output should be something like:
vagrant@k8s-master:~$ kubectl get node -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <n... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2a81d632-c228-42e8-a4db-c8d9fbffb0ab | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 55 | opea-semantic-v1 | 72de600259f362fb | K8S role(i.e. K8S master node). If you want K8S to schedule normal workload to those nodes, please run the following commands on K8S master node:
```bash
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers- | ai_ref_knowledge | OPEA Documentation | K8S role(i.e. K8S master node). If you want K8S to schedule normal workload to those nodes, please run the following commands on K8S master node:
```bash
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers- | K8S role(i.e. K8S master node). If you want K8S to schedule normal workload to those nodes, please run the following commands on K8S master node:
```bash
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers- | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2e5e1d17-4b49-4833-b586-fbc20c4b435e | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 28 | opea-semantic-v1 | 60a97cf1f89910b0 | ```bash export POD_CIDR="10.244.0.0/16" sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}"
Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use. | ai_ref_knowledge | OPEA Documentation | ```bash export POD_CIDR="10.244.0.0/16" sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}"
Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use. | ```bash export POD_CIDR="10.244.0.0/16" sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}"
Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
310028c3-b862-438e-8869-68b7f35edc0f | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 13 | opea-semantic-v1 | bcf735e80ed2fe7c | 2. Config system settings
```bash
# Disable swap
sudo swapoff -a
sudo sed -i "s/^\(.* swap \)/#\1/g" /etc/fstab
# load kernel module for containerd
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF
sudo modprobe overlay
sudo modprobe br_netfilter
# Enable IPv4 packet forwarding
cat <<EOF | sudo... | ai_ref_knowledge | OPEA Documentation | 2. Config system settings
```bash
# Disable swap
sudo swapoff -a
sudo sed -i "s/^\(.* swap \)/#\1/g" /etc/fstab
# load kernel module for containerd
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF
sudo modprobe overlay
sudo modprobe br_netfilter
# Enable IPv4 packet forwarding
cat <<EOF | sudo... | 2. Config system settings
```bash
# Disable swap
sudo swapoff -a
sudo sed -i "s/^\(.* swap \)/#\1/g" /etc/fstab
# load kernel module for containerd
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF
sudo modprobe overlay
sudo modprobe br_netfilter
# Enable IPv4 packet forwarding
cat <<EOF | sudo... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
39ed208a-fd75-4a78-b395-67af12975004 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 31 | opea-semantic-v1 | 192c498deb23dc32 | To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config | ai_ref_knowledge | OPEA Documentation | To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config | To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3b94eaa4-8d2e-474a-a4b2-486b0d86b3ef | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 64 | opea-semantic-v1 | 4191bf7d79ff293c | Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 192.168.121.133
PING 192.168.121.133 (192.168.121.133) 56(84) bytes of data. 64 bytes f... | ai_ref_knowledge | OPEA Documentation | Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 192.168.121.133
PING 192.168.121.133 (192.168.121.133) 56(84) bytes of data. 64 bytes f... | Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S.
vagrant@k8s-master:~$ kubectl exec debug-ddfd698ff-z5qpv -- ping -c 1 192.168.121.133
PING 192.168.121.133 (192.168.121.133) 56(84) bytes of data. 64 bytes f... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3c119e13-6f3c-45ca-bde3-b8f4c75ca839 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 51 | opea-semantic-v1 | f866f5489a036d09 | ## Step 3 (optional) Reset Kubernetes cluster
In some cases, you may want to reset the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kub... | ai_ref_knowledge | OPEA Documentation | ## Step 3 (optional) Reset Kubernetes cluster
In some cases, you may want to reset the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kub... | ## Step 3 (optional) Reset Kubernetes cluster
In some cases, you may want to reset the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kub... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3c8dbf17-d49c-45cf-9793-368319b5f788 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 53 | opea-semantic-v1 | 757d345836b93bb8 | Below is the example of how to reset the Kubernetes cluster we just created:
On node k8s-master, run the following command: | ai_ref_knowledge | OPEA Documentation | Below is the example of how to reset the Kubernetes cluster we just created:
On node k8s-master, run the following command: | Below is the example of how to reset the Kubernetes cluster we just created:
On node k8s-master, run the following command: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
439c5e9d-a89c-4b76-a063-50f9abbd98ee | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 52 | opea-semantic-v1 | 539e239468ada6d2 | the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) for details.
Below is the example of how to reset the Kubernetes c... | ai_ref_knowledge | OPEA Documentation | the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) for details.
Below is the example of how to reset the Kubernetes c... | the Kubernetes cluster in case some commands after `kubeadm init` fail and you want to reinstall Kubernetes. Please check [tear down the Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#tear-down) for details.
Below is the example of how to reset the Kubernetes c... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4c408ca5-5c4f-4004-b250-30ad76dcb67c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 25 | opea-semantic-v1 | 89e4472ce1be2665 | 1. (optional) Install helm v3: on node k8s-master, run the following commands:
```bash
#You may skip helm v3 installation if you don't plan to use helm
curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-sta... | ai_ref_knowledge | OPEA Documentation | 1. (optional) Install helm v3: on node k8s-master, run the following commands:
```bash
#You may skip helm v3 installation if you don't plan to use helm
curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-sta... | 1. (optional) Install helm v3: on node k8s-master, run the following commands:
```bash
#You may skip helm v3 installation if you don't plan to use helm
curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-sta... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
50f95583-a6fe-4cf4-9556-82d638f30e57 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 42 | opea-semantic-v1 | f227890dd999a115 | # This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.APIServer apiVersion: operator.tigera.io/v1 kind: APIServer metadata: name: default spec: {} EOF
5. Join Kubernetes worker nodes: on node k8s-worker, run th... | ai_ref_knowledge | OPEA Documentation | # This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.APIServer apiVersion: operator.tigera.io/v1 kind: APIServer metadata: name: default spec: {} EOF
5. Join Kubernetes worker nodes: on node k8s-worker, run th... | # This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.APIServer apiVersion: operator.tigera.io/v1 kind: APIServer metadata: name: default spec: {} EOF
5. Join Kubernetes worker nodes: on node k8s-worker, run th... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
55e36548-73bf-4640-be49-865bbfa1c217 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 63 | opea-semantic-v1 | 97732b22f76f20e8 | --- 10.244.194.66 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.755/1.755/1.755/0.000 ms
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S. | ai_ref_knowledge | OPEA Documentation | --- 10.244.194.66 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.755/1.755/1.755/0.000 ms
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S. | --- 10.244.194.66 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.755/1.755/1.755/0.000 ms
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another node `k8s-worker1` to verify north-south traffic is working in K8S. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
565c578b-4ca7-462e-82cb-0825c3f76a02 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 2 | opea-semantic-v1 | f027e6f64ead346a | System | | ---------- | ------------------ | ---------------- | | k8s-master | 192.168.121.35/24 | Ubuntu 22.04 | | k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 |
These 2 nodes needs the following proxy to access the internet: | ai_ref_knowledge | OPEA Documentation | System | | ---------- | ------------------ | ---------------- | | k8s-master | 192.168.121.35/24 | Ubuntu 22.04 | | k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 |
These 2 nodes needs the following proxy to access the internet: | System | | ---------- | ------------------ | ---------------- | | k8s-master | 192.168.121.35/24 | Ubuntu 22.04 | | k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 |
These 2 nodes needs the following proxy to access the internet: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
56b5f6de-b516-4544-8f78-9a98b8aa73b0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 16 | opea-semantic-v1 | ed14e5f270899ebc | ```bash # You may change the component version if necessary CONTAINERD_VER="1.7.27" RUNC_VER="1.2.5" CNI_VER="1.6.2" NERDCTL_VER="2.0.4" BUILDKIT_VER="0.20.0"
#Install Runc
wget https://github.com/opencontainers/runc/releases/download/v${RUNC_VER}/runc.amd64
sudo install -m 755 runc.amd64 /usr/local/sbin/runc
rm -f run... | ai_ref_knowledge | OPEA Documentation | ```bash # You may change the component version if necessary CONTAINERD_VER="1.7.27" RUNC_VER="1.2.5" CNI_VER="1.6.2" NERDCTL_VER="2.0.4" BUILDKIT_VER="0.20.0"
#Install Runc
wget https://github.com/opencontainers/runc/releases/download/v${RUNC_VER}/runc.amd64
sudo install -m 755 runc.amd64 /usr/local/sbin/runc
rm -f run... | ```bash # You may change the component version if necessary CONTAINERD_VER="1.7.27" RUNC_VER="1.2.5" CNI_VER="1.6.2" NERDCTL_VER="2.0.4" BUILDKIT_VER="0.20.0"
#Install Runc
wget https://github.com/opencontainers/runc/releases/download/v${RUNC_VER}/runc.amd64
sudo install -m 755 runc.amd64 /usr/local/sbin/runc
rm -f run... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5ab0ab58-981a-404c-b2df-f60cd5db0650 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 50 | opea-semantic-v1 | 202c6fb4749beb0f | CONTAINER-RUNTIME k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27 k8s-worker1 Ready <none> 5m39s v1.32.3 192.168.121.133 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27
## Step 3 (optional) Reset Kubernetes cluster | ai_ref_knowledge | OPEA Documentation | CONTAINER-RUNTIME k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27 k8s-worker1 Ready <none> 5m39s v1.32.3 192.168.121.133 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27
## Step 3 (optional) Reset Kubernetes cluster | CONTAINER-RUNTIME k8s-master Ready control-plane 16m v1.32.3 192.168.121.35 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27 k8s-worker1 Ready <none> 5m39s v1.32.3 192.168.121.133 <none> Ubuntu 22.04.1 LTS 5.15.0-46-generic containerd://1.7.27
## Step 3 (optional) Reset Kubernetes cluster | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
61d7b1ee-08a2-41fe-a6f3-152240232601 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 26 | opea-semantic-v1 | 065ca0cdc8088925 | helm curl https://baltocdn.com/helm/signing.asc | sudo apt-key add - echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list sudo apt-get update sudo apt-get install -y helm
2. Initialize the Kubernetes control-plane node: on node k8s-master, run the follo... | ai_ref_knowledge | OPEA Documentation | helm curl https://baltocdn.com/helm/signing.asc | sudo apt-key add - echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list sudo apt-get update sudo apt-get install -y helm
2. Initialize the Kubernetes control-plane node: on node k8s-master, run the follo... | helm curl https://baltocdn.com/helm/signing.asc | sudo apt-key add - echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list sudo apt-get update sudo apt-get install -y helm
2. Initialize the Kubernetes control-plane node: on node k8s-master, run the follo... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
644207ab-8753-4f3d-a437-0fecf771e1ea | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 5 | opea-semantic-v1 | c0bd21476a6a129c | ## Step 0. Clean up the environment
If on any of the above 2 nodes, you have previously installed either Kubernetes, or any other container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. | ai_ref_knowledge | OPEA Documentation | ## Step 0. Clean up the environment
If on any of the above 2 nodes, you have previously installed either Kubernetes, or any other container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. | ## Step 0. Clean up the environment
If on any of the above 2 nodes, you have previously installed either Kubernetes, or any other container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
67ce546e-6446-4449-80ff-f31ca2758281 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 57 | opea-semantic-v1 | 40d857170364c956 | K8S CNI If you see any issues of the inter-node pod-to-pod communication, please use the following steps to verify that k8s CNI is working correctly:
```bash
# Create the K8S manifest file for our debug pods
cat <<EOF | tee debug.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
run: debug
name: debug
spec... | ai_ref_knowledge | OPEA Documentation | K8S CNI If you see any issues of the inter-node pod-to-pod communication, please use the following steps to verify that k8s CNI is working correctly:
```bash
# Create the K8S manifest file for our debug pods
cat <<EOF | tee debug.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
run: debug
name: debug
spec... | K8S CNI If you see any issues of the inter-node pod-to-pod communication, please use the following steps to verify that k8s CNI is working correctly:
```bash
# Create the K8S manifest file for our debug pods
cat <<EOF | tee debug.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
run: debug
name: debug
spec... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.