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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
68901570-c076-4507-beb9-6f0ed69a2886 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 45 | opea-semantic-v1 | 8d3e4965ea5ff30c | 6. On Kubernetes master node, verify that all nodes are joined successfully:
Run command `kubectl get pod -A` to make sure all pods are in 'Running' status. If any of the pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready. | ai_ref_knowledge | OPEA Documentation | 6. On Kubernetes master node, verify that all nodes are joined successfully:
Run command `kubectl get pod -A` to make sure all pods are in 'Running' status. If any of the pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready. | 6. On Kubernetes master node, verify that all nodes are joined successfully:
Run command `kubectl get pod -A` to make sure all pods are in 'Running' status. If any of the pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
692bab93-0ff8-4f94-abda-58d470489ef6 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 21 | opea-semantic-v1 | fe82aa245b920029 | #You may skip buildkit installation if you don't need to build container images.
#Install buildkit
wget -c https://github.com/moby/buildkit/releases/download/v${BUILDKIT_VER}/buildkit-v${BUILDKIT_VER}.linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local
sudo mkdir -p /etc/buildkit
cat <<EOF | sudo tee /etc/buildkit/bu... | ai_ref_knowledge | OPEA Documentation | #You may skip buildkit installation if you don't need to build container images.
#Install buildkit
wget -c https://github.com/moby/buildkit/releases/download/v${BUILDKIT_VER}/buildkit-v${BUILDKIT_VER}.linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local
sudo mkdir -p /etc/buildkit
cat <<EOF | sudo tee /etc/buildkit/bu... | #You may skip buildkit installation if you don't need to build container images.
#Install buildkit
wget -c https://github.com/moby/buildkit/releases/download/v${BUILDKIT_VER}/buildkit-v${BUILDKIT_VER}.linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local
sudo mkdir -p /etc/buildkit
cat <<EOF | sudo tee /etc/buildkit/bu... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6c8174ef-eb00-4cff-9b2e-78287ac0b853 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 20 | opea-semantic-v1 | 8477a6a54af36ad2 | #Install nerdctl wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCTL_VER}/nerdctl-${NERDCTL_VER}-linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local/bin
#You may skip buildkit installation if you don't need to build container images. | ai_ref_knowledge | OPEA Documentation | #Install nerdctl wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCTL_VER}/nerdctl-${NERDCTL_VER}-linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local/bin
#You may skip buildkit installation if you don't need to build container images. | #Install nerdctl wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCTL_VER}/nerdctl-${NERDCTL_VER}-linux-amd64.tar.gz -qO - | sudo tar xvz -C /usr/local/bin
#You may skip buildkit installation if you don't need to build container images. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6dc4b2f3-4fd8-4e8a-bb2a-8eed5885e25c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 15 | opea-semantic-v1 | 78288c9d698dc22a | 3. Install containerd CRI and relevant components
```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" | ai_ref_knowledge | OPEA Documentation | 3. Install containerd CRI and relevant components
```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" | 3. Install containerd CRI and relevant components
```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" | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
77e54ff9-6fdf-4b83-92db-f6162d5a16e4 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 35 | opea-semantic-v1 | b8921271893b6ff5 | Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \
--discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99 | ai_ref_knowledge | OPEA Documentation | Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \
--discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99 | Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \
--discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99 | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
79ce9e7a-471e-46a2-904d-88d34f879442 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 8 | opea-semantic-v1 | 0fae08bbd329fe09 | If there is any previous Kubernetes installed on any of these nodes by `kubespray`, please refer to kubespray doc to [clean up the Kubernetes](https://kubespray.io/#/?id=quick-start) first.
Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages: | ai_ref_knowledge | OPEA Documentation | If there is any previous Kubernetes installed on any of these nodes by `kubespray`, please refer to kubespray doc to [clean up the Kubernetes](https://kubespray.io/#/?id=quick-start) first.
Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages: | If there is any previous Kubernetes installed on any of these nodes by `kubespray`, please refer to kubespray doc to [clean up the Kubernetes](https://kubespray.io/#/?id=quick-start) first.
Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
800d6fe9-347a-4910-897b-bdd6d8e3ce6d | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 14 | opea-semantic-v1 | 62487b5b6d2ac03c | br_netfilter # Enable IPv4 packet forwarding cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-ip6tables = 1 EOF sudo sysctl --system
3. Install containerd CRI and relevant components | ai_ref_knowledge | OPEA Documentation | br_netfilter # Enable IPv4 packet forwarding cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-ip6tables = 1 EOF sudo sysctl --system
3. Install containerd CRI and relevant components | br_netfilter # Enable IPv4 packet forwarding cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-ip6tables = 1 EOF sudo sysctl --system
3. Install containerd CRI and relevant components | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8be14322-3d0f-43e5-84a9-26d3de2fab4b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 47 | opea-semantic-v1 | aea91a73b547d38e | Possible output of pod status could be something like
vagrant@k8s-master:~$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
calico-apiserver calico-apiserver-59c8dc5bff-ff9vs 1/1 Running 0 3m15s
calico-apiserver calico-apiserver-59c8dc5bff-zblxr 1/1 Running 0 3m15s
calico-system calico-kube-controllers-596b... | ai_ref_knowledge | OPEA Documentation | Possible output of pod status could be something like
vagrant@k8s-master:~$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
calico-apiserver calico-apiserver-59c8dc5bff-ff9vs 1/1 Running 0 3m15s
calico-apiserver calico-apiserver-59c8dc5bff-zblxr 1/1 Running 0 3m15s
calico-system calico-kube-controllers-596b... | Possible output of pod status could be something like
vagrant@k8s-master:~$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
calico-apiserver calico-apiserver-59c8dc5bff-ff9vs 1/1 Running 0 3m15s
calico-apiserver calico-apiserver-59c8dc5bff-zblxr 1/1 Running 0 3m15s
calico-system calico-kube-controllers-596b... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8c0d6695-ecd5-43df-90e1-38c8be68d3c0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 24 | opea-semantic-v1 | 4876fe074d59d7a5 | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg --yes echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubelet kubeadm kubectl
## Step... | ai_ref_knowledge | OPEA Documentation | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg --yes echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubelet kubeadm kubectl
## Step... | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg --yes echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubelet kubeadm kubectl
## Step... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8e861151-b6e0-4822-94dd-deb9c853f88b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 6 | opea-semantic-v1 | 0167a1104d3e1b45 | 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.
If there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](... | ai_ref_knowledge | OPEA Documentation | 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.
If there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](... | 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.
If there is any previous Kubernetes installed on any of these nodes by `kubeadm`, please refer to the listed steps to [tear down the Kubernetes](... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
90f8a80b-9b90-4e76-b818-23fe3f7d5862 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 46 | opea-semantic-v1 | f82f88a2aa6f4622 | pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready.
Possible output of pod status could be something like | ai_ref_knowledge | OPEA Documentation | pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready.
Possible output of pod status could be something like | pods are not in 'Running' status, please retry the above command. It could take up to several minutes for all the pods to be ready.
Possible output of pod status could be something like | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9dfd1055-1cca-4a1f-b7ea-bd03e41df397 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 41 | opea-semantic-v1 | 6c87856d8ddebfa1 | calicoNetwork: ipPools: - name: default-ipv4-ippool blockSize: 26 cidr: ${POD_CIDR} encapsulation: VXLANCrossSubnet natOutgoing: Enabled nodeSelector: all() nodeAddressAutodetectionV4: cidrs: ["${NODE_CIDR}"]
# This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/lat... | ai_ref_knowledge | OPEA Documentation | calicoNetwork: ipPools: - name: default-ipv4-ippool blockSize: 26 cidr: ${POD_CIDR} encapsulation: VXLANCrossSubnet natOutgoing: Enabled nodeSelector: all() nodeAddressAutodetectionV4: cidrs: ["${NODE_CIDR}"]
# This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/lat... | calicoNetwork: ipPools: - name: default-ipv4-ippool blockSize: 26 cidr: ${POD_CIDR} encapsulation: VXLANCrossSubnet natOutgoing: Enabled nodeSelector: all() nodeAddressAutodetectionV4: cidrs: ["${NODE_CIDR}"]
# This section configures the Calico API server. # For more information, see: https://docs.tigera.io/calico/lat... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a320a882-d6a2-44e6-b3c4-accc1445e5a5 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 19 | opea-semantic-v1 | dda6ecc2cf18f678 | | sudo tee /etc/containerd/config.toml sudo sed -i "s/SystemdCgroup = false/SystemdCgroup = true/g" /etc/containerd/config.toml sudo systemctl daemon-reload sudo systemctl enable --now containerd sudo systemctl restart containerd
#Install nerdctl
wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCT... | ai_ref_knowledge | OPEA Documentation | | sudo tee /etc/containerd/config.toml sudo sed -i "s/SystemdCgroup = false/SystemdCgroup = true/g" /etc/containerd/config.toml sudo systemctl daemon-reload sudo systemctl enable --now containerd sudo systemctl restart containerd
#Install nerdctl
wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCT... | | sudo tee /etc/containerd/config.toml sudo sed -i "s/SystemdCgroup = false/SystemdCgroup = true/g" /etc/containerd/config.toml sudo systemctl daemon-reload sudo systemctl enable --now containerd sudo systemctl restart containerd
#Install nerdctl
wget -c https://github.com/containerd/nerdctl/releases/download/v${NERDCT... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a4a7183a-f7ae-4293-af18-198d22c73d21 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 62 | opea-semantic-v1 | dc2c66eb9a53fe33 | 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 bytes from 10.244.194.66: icmp_seq=1 ttl=62 time=1.76 ms
--- 10.244.194.66 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev ... | ai_ref_knowledge | OPEA Documentation | 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 bytes from 10.244.194.66: icmp_seq=1 ttl=62 time=1.76 ms
--- 10.244.194.66 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev ... | 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 bytes from 10.244.194.66: icmp_seq=1 ttl=62 time=1.76 ms
--- 10.244.194.66 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a7d2afe1-7f6c-4223-831e-5c088381a071 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 36 | opea-semantic-v1 | 59dfa413c41050ed | kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \ --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands: | ai_ref_knowledge | OPEA Documentation | kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \ --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands: | kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou \ --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
3. Create kubectl configuration for a regular user: on node k8s-master, run the following commands: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b85244e0-4c07-415d-a631-babeb94cb893 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 11 | opea-semantic-v1 | b44e9f195e6458ac | 1. Export proxy settings in bash
```bash
export http_proxy="http://proxy.fake-proxy.com:911"
export https_proxy="http://proxy.fake-proxy.com:912"
# Please make sure you've added all the node's ip addresses into the no_proxy environment variable
export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/1... | ai_ref_knowledge | OPEA Documentation | 1. Export proxy settings in bash
```bash
export http_proxy="http://proxy.fake-proxy.com:911"
export https_proxy="http://proxy.fake-proxy.com:912"
# Please make sure you've added all the node's ip addresses into the no_proxy environment variable
export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/1... | 1. Export proxy settings in bash
```bash
export http_proxy="http://proxy.fake-proxy.com:911"
export https_proxy="http://proxy.fake-proxy.com:912"
# Please make sure you've added all the node's ip addresses into the no_proxy environment variable
export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/1... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b95604a6-f160-46dd-b5bc-52ca381442ca | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 39 | opea-semantic-v1 | 8e1226aef7f1d7a5 | 4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands:
```bash
# Please set correct NODE_CIDR based on your node ip address. # In this example, because both nodes are in 192.168.121.0/24 subnet,
# we set NODE_CIDR accordingly. NODE_CIDR="192.168.121.0/24"
# You may change the component versio... | ai_ref_knowledge | OPEA Documentation | 4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands:
```bash
# Please set correct NODE_CIDR based on your node ip address. # In this example, because both nodes are in 192.168.121.0/24 subnet,
# we set NODE_CIDR accordingly. NODE_CIDR="192.168.121.0/24"
# You may change the component versio... | 4. Install Kubernetes CNI Calico: on node k8s-master, run the following commands:
```bash
# Please set correct NODE_CIDR based on your node ip address. # In this example, because both nodes are in 192.168.121.0/24 subnet,
# we set NODE_CIDR accordingly. NODE_CIDR="192.168.121.0/24"
# You may change the component versio... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
bd6bdbdd-c8b1-45ea-88de-eda7b90d0deb | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 3 | opea-semantic-v1 | 82cbf67e9867f793 | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
We assume 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. | ai_ref_knowledge | OPEA Documentation | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
We assume 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. | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
We assume 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. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c5dd9020-6aef-4f21-90f3-ddaf76aafe2e | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 44 | opea-semantic-v1 | 4ab670e88aa682f3 | ```bash # run the kubeadm join command which we recorded at the end of the step 2.4 sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
6. On Kubernetes master node, verify that all nodes are joined ... | ai_ref_knowledge | OPEA Documentation | ```bash # run the kubeadm join command which we recorded at the end of the step 2.4 sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
6. On Kubernetes master node, verify that all nodes are joined ... | ```bash # run the kubeadm join command which we recorded at the end of the step 2.4 sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af159e2abc260201ba99
6. On Kubernetes master node, verify that all nodes are joined ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d3d7c3bf-4730-4722-9b07-1ad8c30808a9 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 65 | opea-semantic-v1 | ec607d687f693d98 | 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 from 192.168.121.133: icmp_seq=1 ttl=63 time=1.34 ms
--- 192.168.121.133 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg... | ai_ref_knowledge | OPEA Documentation | 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 from 192.168.121.133: icmp_seq=1 ttl=63 time=1.34 ms
--- 192.168.121.133 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg... | 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 from 192.168.121.133: icmp_seq=1 ttl=63 time=1.34 ms
--- 192.168.121.133 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d49599df-9e7f-4f5e-ab1f-882e82f6b1b9 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 60 | opea-semantic-v1 | df002b8e8470c31f | AGE IP NODE NOMINATED NODE READINESS GATES debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none> debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none> <none>
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7... | ai_ref_knowledge | OPEA Documentation | AGE IP NODE NOMINATED NODE READINESS GATES debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none> debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none> <none>
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7... | AGE IP NODE NOMINATED NODE READINESS GATES debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none> debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none> <none>
Make sure pod `debug-ddfd698ff-z5qpv` on node k8s-master can ping to the ip address of another pod `debug-ddfd698ff-7... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d8ad09b7-3843-4d87-a9ab-88b7c90f76b7 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 58 | opea-semantic-v1 | 36aad8461d57430a | - debug topologyKey: kubernetes.io/hostname containers: - image: nicolaka/netshoot:latest name: debug command: [ "sleep", "infinity" ] EOF # Create the debug pod kubectl apply -f debug.yaml
Wait until all 2 debug pods are in 'Running' status: | ai_ref_knowledge | OPEA Documentation | - debug topologyKey: kubernetes.io/hostname containers: - image: nicolaka/netshoot:latest name: debug command: [ "sleep", "infinity" ] EOF # Create the debug pod kubectl apply -f debug.yaml
Wait until all 2 debug pods are in 'Running' status: | - debug topologyKey: kubernetes.io/hostname containers: - image: nicolaka/netshoot:latest name: debug command: [ "sleep", "infinity" ] EOF # Create the debug pod kubectl apply -f debug.yaml
Wait until all 2 debug pods are in 'Running' status: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e0ea107c-0b1a-43d0-b0e6-23db8825d3fc | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 18 | opea-semantic-v1 | a990d1399cdab13d | #Install CNI sudo mkdir -p /opt/cni/bin wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v${CNI_VER}.tgz -qO - | sudo tar xvz -C /opt/cni/bin
#Install Containerd
wget -c https://github.com/containerd/containerd/releases/download/v${CONTAINERD_VER}/containerd-$... | ai_ref_knowledge | OPEA Documentation | #Install CNI sudo mkdir -p /opt/cni/bin wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v${CNI_VER}.tgz -qO - | sudo tar xvz -C /opt/cni/bin
#Install Containerd
wget -c https://github.com/containerd/containerd/releases/download/v${CONTAINERD_VER}/containerd-$... | #Install CNI sudo mkdir -p /opt/cni/bin wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v${CNI_VER}.tgz -qO - | sudo tar xvz -C /opt/cni/bin
#Install Containerd
wget -c https://github.com/containerd/containerd/releases/download/v${CONTAINERD_VER}/containerd-$... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e1a6a288-a7d4-4361-894f-799f4a8f1bed | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 54 | opea-semantic-v1 | 598bb43a017b16ba | ## NOTES
1. By default, normal workload won't be scheduled to nodes in `control-plane` 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: | ai_ref_knowledge | OPEA Documentation | ## NOTES
1. By default, normal workload won't be scheduled to nodes in `control-plane` 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: | ## NOTES
1. By default, normal workload won't be scheduled to nodes in `control-plane` 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: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e5cde6b6-8b41-4fed-88c9-1bb873ec05f0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 10 | opea-semantic-v1 | 8ebd62fa794bd9ee | ```bash sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/containerd /etc/systemd/system/containerd.service.d /etc/default/kubelet
## Step 1. Install relevant components | ai_ref_knowledge | OPEA Documentation | ```bash sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/containerd /etc/systemd/system/containerd.service.d /etc/default/kubelet
## Step 1. Install relevant components | ```bash sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/containerd /etc/systemd/system/containerd.service.d /etc/default/kubelet
## Step 1. Install relevant components | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e62982aa-3c4d-4170-b892-6fac7e66d516 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 17 | opea-semantic-v1 | 6aae6cffc0110e07 | #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 runc.amd64
#Install CNI
sudo mkdir -p /opt/cni/bin
wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v$... | ai_ref_knowledge | OPEA Documentation | #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 runc.amd64
#Install CNI
sudo mkdir -p /opt/cni/bin
wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v$... | #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 runc.amd64
#Install CNI
sudo mkdir -p /opt/cni/bin
wget -c https://github.com/containernetworking/plugins/releases/download/v${CNI_VER}/cni-plugins-linux-amd64-v$... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ea91ea09-d182-4082-93d6-92e749bd0861 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 43 | opea-semantic-v1 | 744cbe2c7cb385d5 | 5. Join Kubernetes worker nodes: on node k8s-worker, run the following commands:
```bash
# run the kubeadm join command which we recorded at the end of the step 2.4
sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af1... | ai_ref_knowledge | OPEA Documentation | 5. Join Kubernetes worker nodes: on node k8s-worker, run the following commands:
```bash
# run the kubeadm join command which we recorded at the end of the step 2.4
sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af1... | 5. Join Kubernetes worker nodes: on node k8s-worker, run the following commands:
```bash
# run the kubeadm join command which we recorded at the end of the step 2.4
sudo kubeadm join 192.168.121.35:6443 --token 26tg15.km2ru94h9ht9h6ou --discovery-token-ca-cert-hash sha256:123f3f8ebaf62f8dfc4542360e5103842408a6cdf630af1... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ed8cde70-3817-4c92-b8a2-19ab6a703bd6 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 27 | opea-semantic-v1 | eced9af110a4b4b0 | 2. Initialize the Kubernetes control-plane node: on node k8s-master, run the following commands:
```bash
export POD_CIDR="10.244.0.0/16"
sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}" | ai_ref_knowledge | OPEA Documentation | 2. Initialize the Kubernetes control-plane node: on node k8s-master, run the following commands:
```bash
export POD_CIDR="10.244.0.0/16"
sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}" | 2. Initialize the Kubernetes control-plane node: on node k8s-master, run the following commands:
```bash
export POD_CIDR="10.244.0.0/16"
sudo -E kubeadm init --pod-network-cidr "${POD_CIDR}" | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
edfb3836-8c10-4a6e-a73c-6bfae702dd6e | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 9 | opea-semantic-v1 | a58d3fc808cd3e12 | Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages:
```bash
sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet
sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/c... | ai_ref_knowledge | OPEA Documentation | Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages:
```bash
sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet
sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/c... | Once the Kubernetes is teared down or cleaned up, please run the following command on all the nodes to remove relevant packages:
```bash
sudo apt-get purge docker docker-engine docker.io containerd runc containerd.io kubeadm kubectl kubelet
sudo rm -r /etc/cni /etc/kubernetes /var/lib/kubelet /var/run/kubernetes /etc/c... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ee585fa7-eef2-4e6d-b583-ab3449bd3a4f | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 40 | opea-semantic-v1 | 199d93521a524b49 | This section includes base Calico installation configuration. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.Installation apiVersion: operator.tigera.io/v1 kind: Installation metadata: name: default spec: # Configures Calico networking.
calicoNetwork:
... | ai_ref_knowledge | OPEA Documentation | This section includes base Calico installation configuration. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.Installation apiVersion: operator.tigera.io/v1 kind: Installation metadata: name: default spec: # Configures Calico networking.
calicoNetwork:
... | This section includes base Calico installation configuration. # For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.Installation apiVersion: operator.tigera.io/v1 kind: Installation metadata: name: default spec: # Configures Calico networking.
calicoNetwork:
... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ef42652a-9909-4cc5-8a5c-6aa64f2d1b28 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 56 | opea-semantic-v1 | a9ca3a3bbb4a45a8 | ```bash kubectl taint nodes --all node-role.kubernetes.io/control-plane- kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers-
2. Verifying 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: | ai_ref_knowledge | OPEA Documentation | ```bash kubectl taint nodes --all node-role.kubernetes.io/control-plane- kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers-
2. Verifying 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 kubectl taint nodes --all node-role.kubernetes.io/control-plane- kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers-
2. Verifying 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: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ef8b4c24-3239-40b1-891f-0d1472d28f24 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 22 | opea-semantic-v1 | 8bae7a19322f3eb5 | EOF sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.service -qO /usr/local/lib/systemd/system/buildkit.service sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.socket -qO /usr/local/lib/systemd/s... | ai_ref_knowledge | OPEA Documentation | EOF sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.service -qO /usr/local/lib/systemd/system/buildkit.service sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.socket -qO /usr/local/lib/systemd/s... | EOF sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.service -qO /usr/local/lib/systemd/system/buildkit.service sudo -E wget https://raw.githubusercontent.com/moby/buildkit/v${BUILDKIT_VER}/examples/systemd/system/buildkit.socket -qO /usr/local/lib/systemd/s... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f0eeafeb-6a16-4ab1-9c24-5e2adbde5927 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 12 | opea-semantic-v1 | 6734d5668d970937 | ```bash export http_proxy="http://proxy.fake-proxy.com:911" export https_proxy="http://proxy.fake-proxy.com:912" # Please make sure you've added all the node's ip addresses into the no_proxy environment variable export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,192.168.121.35,192.168.121.133"... | ai_ref_knowledge | OPEA Documentation | ```bash export http_proxy="http://proxy.fake-proxy.com:911" export https_proxy="http://proxy.fake-proxy.com:912" # Please make sure you've added all the node's ip addresses into the no_proxy environment variable export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,192.168.121.35,192.168.121.133"... | ```bash export http_proxy="http://proxy.fake-proxy.com:911" export https_proxy="http://proxy.fake-proxy.com:912" # Please make sure you've added all the node's ip addresses into the no_proxy environment variable export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,192.168.121.35,192.168.121.133"... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f1bb8807-52b4-4f6c-8f0c-ef0f23d529a2 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 29 | opea-semantic-v1 | dcdf720c655a6be0 | Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use.
Your Kubernetes control-plane has initialized successfully! | ai_ref_knowledge | OPEA Documentation | Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use.
Your Kubernetes control-plane has initialized successfully! | Once succeed, you'll find the kubeadm's output such as the following. Please record the `kubeadm join` command line for later use.
Your Kubernetes control-plane has initialized successfully! | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f4e04f1e-74f1-4a81-a05d-cf552f98f906 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 23 | opea-semantic-v1 | 458c801771c01e63 | ```bash # You may change the component version if necessary K8S_VER="1.32"
#Install kubeadm/kubectl/kubelet
sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl gpg
sudo mkdir -p -m 755 /etc/apt/keyrings
curl -fsSL https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/Release.key | sudo gpg ... | ai_ref_knowledge | OPEA Documentation | ```bash # You may change the component version if necessary K8S_VER="1.32"
#Install kubeadm/kubectl/kubelet
sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl gpg
sudo mkdir -p -m 755 /etc/apt/keyrings
curl -fsSL https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/Release.key | sudo gpg ... | ```bash # You may change the component version if necessary K8S_VER="1.32"
#Install kubeadm/kubectl/kubelet
sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl gpg
sudo mkdir -p -m 755 /etc/apt/keyrings
curl -fsSL https://pkgs.k8s.io/core:/stable:/v${K8S_VER}/deb/Release.key | sudo gpg ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f76f6fec-23f4-4414-8e4a-b2fc40a99e3c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 1 | opea-semantic-v1 | b9fec48f64498128 | ## Node configuration
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | ai_ref_knowledge | OPEA Documentation | ## Node configuration
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | ## Node configuration
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fb0d0d44-1796-445a-88d1-72819e30819d | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 59 | opea-semantic-v1 | 51438f4c0186604e | Wait until all 2 debug pods are in 'Running' status:
vagrant@k8s-master:~$ kubectl get pod -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none>
debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none>... | ai_ref_knowledge | OPEA Documentation | Wait until all 2 debug pods are in 'Running' status:
vagrant@k8s-master:~$ kubectl get pod -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none>
debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none>... | Wait until all 2 debug pods are in 'Running' status:
vagrant@k8s-master:~$ kubectl get pod -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
debug-ddfd698ff-7gsdc 1/1 Running 0 91s 10.244.194.66 k8s-worker1 <none> <none>
debug-ddfd698ff-z5qpv 1/1 Running 0 91s 10.244.235.199 k8s-master <none>... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fe446c3e-2969-4022-921e-63b18eea4871 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubeadm.md | unknown | 9eaa769b-9ff0-4fec-bfa5-6d1126224b0d | 33 | opea-semantic-v1 | 99b3e81628ff476b | export KUBECONFIG=/etc/kubernetes/admin.conf
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/ | ai_ref_knowledge | OPEA Documentation | export KUBECONFIG=/etc/kubernetes/admin.conf
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/ | export KUBECONFIG=/etc/kubernetes/admin.conf
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/ | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0029f855-5136-470f-a506-4d88c70d360d | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 9 | opea-semantic-v1 | ab2331b23b9e8634 | nodes cat ~/.ssh/id_rsa.pub | ssh username@k8s-master "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys" cat ~/.ssh/id_rsa.pub | ssh username@k8s-worker "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
## Step 1. Set up Kubespray and Ansible | ai_ref_knowledge | OPEA Documentation | nodes cat ~/.ssh/id_rsa.pub | ssh username@k8s-master "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys" cat ~/.ssh/id_rsa.pub | ssh username@k8s-worker "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
## Step 1. Set up Kubespray and Ansible | nodes cat ~/.ssh/id_rsa.pub | ssh username@k8s-master "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys" cat ~/.ssh/id_rsa.pub | ssh username@k8s-worker "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
## Step 1. Set up Kubespray and Ansible | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
002d1165-1beb-4766-bce4-55107399c25c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 2 | opea-semantic-v1 | ca30ec3e54d837fb | ## Node preparation
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | ai_ref_knowledge | OPEA Documentation | ## Node preparation
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | ## Node preparation
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| k8s-master | 192.168.121.35/24 | Ubuntu 22.04 |
| k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 | | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0b517440-916d-468d-a258-a13544ad450b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 22 | opea-semantic-v1 | 6b9a3806917d3347 | # The port the API Server will be listening on. kube_apiserver_ip: "{{ kube_service_addresses | ansible.utils.ipaddr('net') | ansible.utils.ipaddr(1) | ansible.utils.ipaddr('address') }}" kube_apiserver_port: 8080 # (http)
## Step 4. Deploy Kubernetes | ai_ref_knowledge | OPEA Documentation | # The port the API Server will be listening on. kube_apiserver_ip: "{{ kube_service_addresses | ansible.utils.ipaddr('net') | ansible.utils.ipaddr(1) | ansible.utils.ipaddr('address') }}" kube_apiserver_port: 8080 # (http)
## Step 4. Deploy Kubernetes | # The port the API Server will be listening on. kube_apiserver_ip: "{{ kube_service_addresses | ansible.utils.ipaddr('net') | ansible.utils.ipaddr(1) | ansible.utils.ipaddr('address') }}" kube_apiserver_port: 8080 # (http)
## Step 4. Deploy Kubernetes | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
10f73965-1e2c-4c3d-95d6-912fdddcf50e | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 45 | opea-semantic-v1 | 7f251a2043c28517 | | hostname | ip address | Operating System | | ---------- | ------------------ | ---------------- | | third-node | 192.168.121.134/24 | Ubuntu 22.04 |
Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine. | ai_ref_knowledge | OPEA Documentation | | hostname | ip address | Operating System | | ---------- | ------------------ | ---------------- | | third-node | 192.168.121.134/24 | Ubuntu 22.04 |
Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine. | | hostname | ip address | Operating System | | ---------- | ------------------ | ---------------- | | third-node | 192.168.121.134/24 | Ubuntu 22.04 |
Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
154c661f-5619-4af7-a82a-392d85945d50 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 10 | opea-semantic-v1 | d4661c0143420f22 | ## Step 1. Set up Kubespray and Ansible
Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide. | ai_ref_knowledge | OPEA Documentation | ## Step 1. Set up Kubespray and Ansible
Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide. | ## Step 1. Set up Kubespray and Ansible
Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
16fb8675-bcff-4e93-b7e6-fcca0db17d90 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 43 | opea-semantic-v1 | 786a024d2a7c771c | ### How to scale Kubernetes cluster to add more nodes?
Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is: | ai_ref_knowledge | OPEA Documentation | ### How to scale Kubernetes cluster to add more nodes?
Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is: | ### How to scale Kubernetes cluster to add more nodes?
Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1939c9f2-a320-41d8-aff1-1f43b54e0fb2 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 38 | opea-semantic-v1 | ef621c8a161b0214 | cp -r inventory/local inventory/mycluster
Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command: | ai_ref_knowledge | OPEA Documentation | cp -r inventory/local inventory/mycluster
Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command: | cp -r inventory/local inventory/mycluster
Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
209c6fbd-c0d2-4624-b9e7-979246760e37 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 37 | opea-semantic-v1 | dd10dfd7f394f931 | And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following:
cp -r inventory/local inventory/mycluster | ai_ref_knowledge | OPEA Documentation | And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following:
cp -r inventory/local inventory/mycluster | And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following:
cp -r inventory/local inventory/mycluster | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
22281e77-be46-43db-8d6e-2989bc380d8c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 41 | opea-semantic-v1 | 4376394a6ed73ced | name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you will get a 1-node K8s ready.
And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the sta... | ai_ref_knowledge | OPEA Documentation | name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you will get a 1-node K8s ready.
And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the sta... | name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you will get a 1-node K8s ready.
And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the sta... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
22484ca1-bb4b-470b-b6b3-642fd9227e10 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 0 | opea-semantic-v1 | 7dc918f11ed7e298 | In this document, we'll install Kubernetes v1.29 using [Kubespray](https://github.com/kubernetes-sigs/kubespray) on a 2-node cluster.
There are several ways to use Kubespray to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's documen... | ai_ref_knowledge | OPEA Documentation | In this document, we'll install Kubernetes v1.29 using [Kubespray](https://github.com/kubernetes-sigs/kubespray) on a 2-node cluster.
There are several ways to use Kubespray to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's documen... | In this document, we'll install Kubernetes v1.29 using [Kubespray](https://github.com/kubernetes-sigs/kubespray) on a 2-node cluster.
There are several ways to use Kubespray to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's documen... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2688f68f-9508-458a-a342-c20f0c17a364 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 32 | opea-semantic-v1 | 37dbbb8b7aefbb72 | Then run following command to check the status of your Kubernetes cluster:
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-master Ready control-plane 31m v1.29.5
k8s-worker Ready <none> 7m31s v1.29.5
$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-68485cbf9c-vwqqj... | ai_ref_knowledge | OPEA Documentation | Then run following command to check the status of your Kubernetes cluster:
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-master Ready control-plane 31m v1.29.5
k8s-worker Ready <none> 7m31s v1.29.5
$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-68485cbf9c-vwqqj... | Then run following command to check the status of your Kubernetes cluster:
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-master Ready control-plane 31m v1.29.5
k8s-worker Ready <none> 7m31s v1.29.5
$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-68485cbf9c-vwqqj... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
30f0bde8-db84-4182-bfee-f521c0cba668 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 13 | opea-semantic-v1 | b2f9d64812da4f33 | -m venv $VENVDIR source $VENVDIR/bin/activate cd $KUBESPRAYDIR # Check out the latest release version tag of kubespray. git checkout v2.25.0 pip install -U -r requirements.txt
## Step 2. Build your own inventory | ai_ref_knowledge | OPEA Documentation | -m venv $VENVDIR source $VENVDIR/bin/activate cd $KUBESPRAYDIR # Check out the latest release version tag of kubespray. git checkout v2.25.0 pip install -U -r requirements.txt
## Step 2. Build your own inventory | -m venv $VENVDIR source $VENVDIR/bin/activate cd $KUBESPRAYDIR # Check out the latest release version tag of kubespray. git checkout v2.25.0 pip install -U -r requirements.txt
## Step 2. Build your own inventory | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3a252516-87e2-44b1-8ec6-785c3132032e | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 52 | opea-semantic-v1 | 13398321fa2f9819 | If your nodes need proxy to access internet, you will need extra configurations during deploying K8s.
We assume your proxy is as below: | ai_ref_knowledge | OPEA Documentation | If your nodes need proxy to access internet, you will need extra configurations during deploying K8s.
We assume your proxy is as below: | If your nodes need proxy to access internet, you will need extra configurations during deploying K8s.
We assume your proxy is as below: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3be24a94-b8bd-4ae6-98a2-18b571b21b59 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 30 | opea-semantic-v1 | caf41685b83ea1e1 | mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
If you want to access this Kubernetes cluster from other machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ow... | 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
If you want to access this Kubernetes cluster from other machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ow... | mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
If you want to access this Kubernetes cluster from other machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ow... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3e34c8e2-a2aa-4a17-a5f8-41e00c304ea8 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 27 | opea-semantic-v1 | 57e1609523c16f81 | will take several minutes to finish. After playbook is done, you can check the output. If `failed=0` exists, it means playbook execution is successfully done.
## Step 5. Create kubectl configuration | ai_ref_knowledge | OPEA Documentation | will take several minutes to finish. After playbook is done, you can check the output. If `failed=0` exists, it means playbook execution is successfully done.
## Step 5. Create kubectl configuration | will take several minutes to finish. After playbook is done, you can check the output. If `failed=0` exists, it means playbook execution is successfully done.
## Step 5. Create kubectl configuration | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
448b35d3-8524-4dcd-9756-4b16fcc2a6b4 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 20 | opea-semantic-v1 | d8704120b32d74e4 | For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml`
**_NOTE:_** If you noted issues on `TASK [kubernetes/control-plane : Kubeadm | Initialize first master]` in K& deployment, change the port on which API Server will be listening on from 6443 to 8080. By default Kubespray configures kub... | ai_ref_knowledge | OPEA Documentation | For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml`
**_NOTE:_** If you noted issues on `TASK [kubernetes/control-plane : Kubeadm | Initialize first master]` in K& deployment, change the port on which API Server will be listening on from 6443 to 8080. By default Kubespray configures kub... | For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml`
**_NOTE:_** If you noted issues on `TASK [kubernetes/control-plane : Kubeadm | Initialize first master]` in K& deployment, change the port on which API Server will be listening on from 6443 to 8080. By default Kubespray configures kub... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
48cb4b94-b822-486d-991f-3226aa7d5210 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 31 | opea-semantic-v1 | df1dda6b3e799508 | machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ownership as above.
Then run following command to check the status of your Kubernetes cluster: | ai_ref_knowledge | OPEA Documentation | machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ownership as above.
Then run following command to check the status of your Kubernetes cluster: | machines, you can install kubectl by `sudo apt-get install -y kubectl` and copy over the configuration from the k8-master node and set ownership as above.
Then run following command to check the status of your Kubernetes cluster: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
508f3e29-f296-43cb-8463-67d7406c0a4b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 35 | opea-semantic-v1 | 434bdd55b8e6f467 | Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster.
Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment. | ai_ref_knowledge | OPEA Documentation | Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster.
Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment. | Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster.
Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
511e03ab-97cd-4f5b-9f68-cb553c5e332a | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 54 | opea-semantic-v1 | c316080cd422144f | make sure you've added all the nodes' ip addresses into the `additional_no_proxy` parameter. In this example, we use `192.168.121.0/24` to represent all nodes' ip addresses.
## Set these proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed
http_proxy: ... | ai_ref_knowledge | OPEA Documentation | make sure you've added all the nodes' ip addresses into the `additional_no_proxy` parameter. In this example, we use `192.168.121.0/24` to represent all nodes' ip addresses.
## Set these proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed
http_proxy: ... | make sure you've added all the nodes' ip addresses into the `additional_no_proxy` parameter. In this example, we use `192.168.121.0/24` to represent all nodes' ip addresses.
## Set these proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed
http_proxy: ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
54986ae0-ed74-4b79-91d9-5d34fd5778bf | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 48 | opea-semantic-v1 | 98a4f3b8307a1f5c | Then you can deploy Kubernetes to the third node with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without ... | ai_ref_knowledge | OPEA Documentation | Then you can deploy Kubernetes to the third node with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without ... | Then you can deploy Kubernetes to the third node with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5d7714ed-855d-4cbc-ab13-aec273f1c903 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 15 | opea-semantic-v1 | ab58355efa7b0e1b | inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command:
cp -r inventory/sample inventory/mycluster | ai_ref_knowledge | OPEA Documentation | inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command:
cp -r inventory/sample inventory/mycluster | inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command:
cp -r inventory/sample inventory/mycluster | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6492cc04-c518-4d6d-b1f4-b31c931e6e83 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 51 | opea-semantic-v1 | 058e602873bf9177 | ### How to config proxy?
If your nodes need proxy to access internet, you will need extra configurations during deploying K8s. | ai_ref_knowledge | OPEA Documentation | ### How to config proxy?
If your nodes need proxy to access internet, you will need extra configurations during deploying K8s. | ### How to config proxy?
If your nodes need proxy to access internet, you will need extra configurations during deploying K8s. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
67d1a990-fde6-4f28-a4df-871657ca0a2d | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 29 | opea-semantic-v1 | 945ef633a98ee71b | If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands:
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 | If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config | If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands:
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 | |
7359ea17-bd8d-4c9d-94c5-a12d7ee5d0af | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 23 | opea-semantic-v1 | 605d8c433d371eb7 | You can clean up old Kubernetes cluster with Ansible playbook with following command:
# Clean up old Kubernetes cluster with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example cleaning up SSL keys in /etc/,
# uninstalling old packages and interacting with various systemd dae... | ai_ref_knowledge | OPEA Documentation | You can clean up old Kubernetes cluster with Ansible playbook with following command:
# Clean up old Kubernetes cluster with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example cleaning up SSL keys in /etc/,
# uninstalling old packages and interacting with various systemd dae... | You can clean up old Kubernetes cluster with Ansible playbook with following command:
# Clean up old Kubernetes cluster with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example cleaning up SSL keys in /etc/,
# uninstalling old packages and interacting with various systemd dae... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7e075b3e-0581-4ca1-ad1b-e6c9200e8463 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 12 | opea-semantic-v1 | 78acb1332f65dc20 | for details. To get the kubespray code, please check out the [latest release version](https://github.com/kubernetes-sigs/kubespray/releases) tag of kubespray. Here we use kubespary v2.25.0 as an example.
git clone https://github.com/kubernetes-sigs/kubespray.git
VENVDIR=kubespray-venv
KUBESPRAYDIR=kubespray
python3 -m ... | ai_ref_knowledge | OPEA Documentation | for details. To get the kubespray code, please check out the [latest release version](https://github.com/kubernetes-sigs/kubespray/releases) tag of kubespray. Here we use kubespary v2.25.0 as an example.
git clone https://github.com/kubernetes-sigs/kubespray.git
VENVDIR=kubespray-venv
KUBESPRAYDIR=kubespray
python3 -m ... | for details. To get the kubespray code, please check out the [latest release version](https://github.com/kubernetes-sigs/kubespray/releases) tag of kubespray. Here we use kubespary v2.25.0 as an example.
git clone https://github.com/kubernetes-sigs/kubespray.git
VENVDIR=kubespray-venv
KUBESPRAYDIR=kubespray
python3 -m ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
82217dd8-d447-49f3-b7c0-2ba1e938d842 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 33 | opea-semantic-v1 | c27252cd9083a567 | 23m kube-system kube-scheduler-satg-opea-0 1/1 Running 0 24m kube-system nginx-proxy-satg-opea-3 1/1 Running 0 23m kube-system nodelocaldns-kbcnv 1/1 Running 0 23m kube-system nodelocaldns-wvktt 1/1 Running 0 24m
Now congratulations. Your two-node K8s cluster is ready to use. | ai_ref_knowledge | OPEA Documentation | 23m kube-system kube-scheduler-satg-opea-0 1/1 Running 0 24m kube-system nginx-proxy-satg-opea-3 1/1 Running 0 23m kube-system nodelocaldns-kbcnv 1/1 Running 0 23m kube-system nodelocaldns-wvktt 1/1 Running 0 24m
Now congratulations. Your two-node K8s cluster is ready to use. | 23m kube-system kube-scheduler-satg-opea-0 1/1 Running 0 24m kube-system nginx-proxy-satg-opea-3 1/1 Running 0 23m kube-system nodelocaldns-kbcnv 1/1 Running 0 23m kube-system nodelocaldns-wvktt 1/1 Running 0 24m
Now congratulations. Your two-node K8s cluster is ready to use. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
84eedacb-ada8-4205-82b1-cb0d1ccb7ac2 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 25 | opea-semantic-v1 | 522a7b14f0777052 | Then you can deploy Kubernetes with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without --become the playb... | ai_ref_knowledge | OPEA Documentation | Then you can deploy Kubernetes with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without --become the playb... | Then you can deploy Kubernetes with Ansible playbook with following command:
# Deploy Kubespray with Ansible Playbook - run the playbook as root
# The option `--become` is required, as for example writing SSL keys in /etc/,
# installing packages and interacting with various systemd daemons. # Without --become the playb... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
887b50bd-45ef-43f5-ac1a-e129d7a06135 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 14 | opea-semantic-v1 | 9a8cffa54195b593 | ## Step 2. Build your own inventory
Ansible inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command: | ai_ref_knowledge | OPEA Documentation | ## Step 2. Build your own inventory
Ansible inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command: | ## Step 2. Build your own inventory
Ansible inventory defines the hosts and groups of hosts on which Ansible tasks are to be executed. You can copy a sample inventory with following command: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
88d63138-5247-4588-9900-5e351467af10 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 4 | opea-semantic-v1 | 08d2ac8ad6d0ef54 | We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository.
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 cle... | ai_ref_knowledge | OPEA Documentation | We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository.
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 cle... | We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository.
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 cle... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
89cecffc-4ad6-413f-9b1d-87ad5e2ec31f | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 28 | opea-semantic-v1 | eea444fbdd9df782 | ## Step 5. Create kubectl configuration
If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands: | ai_ref_knowledge | OPEA Documentation | ## Step 5. Create kubectl configuration
If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands: | ## Step 5. Create kubectl configuration
If you want to use Kubernetes command line tool `kubectl` on **k8s-master** node, please login to the node **k8s-master** and run the following commands: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8aafbaad-4862-4243-8a22-9d1e6569909a | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 8 | opea-semantic-v1 | 26d2b0303a0f634e | the ssh login without password promotion. A simple way is to copy the public key of the operating machine to the K8s nodes. For example:
# generate key pair in the operation machine
ssh-keygen -t rsa -b 4096
# manually copy the public key to the K8s master and worker nodes
cat ~/.ssh/id_rsa.pub | ssh username@k8s-maste... | ai_ref_knowledge | OPEA Documentation | the ssh login without password promotion. A simple way is to copy the public key of the operating machine to the K8s nodes. For example:
# generate key pair in the operation machine
ssh-keygen -t rsa -b 4096
# manually copy the public key to the K8s master and worker nodes
cat ~/.ssh/id_rsa.pub | ssh username@k8s-maste... | the ssh login without password promotion. A simple way is to copy the public key of the operating machine to the K8s nodes. For example:
# generate key pair in the operation machine
ssh-keygen -t rsa -b 4096
# manually copy the public key to the K8s master and worker nodes
cat ~/.ssh/id_rsa.pub | ssh username@k8s-maste... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8b170736-e8c2-4e97-89b1-160196b0894f | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 55 | opea-semantic-v1 | 1f05a9c1a4bf4f54 | proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed http_proxy: "http://proxy.fake-proxy.com:911" https_proxy: "http://proxy.fake-proxy.com:912"
## If you need exclude all cluster nodes from proxy and other resources, add other resources here. additio... | ai_ref_knowledge | OPEA Documentation | proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed http_proxy: "http://proxy.fake-proxy.com:911" https_proxy: "http://proxy.fake-proxy.com:912"
## If you need exclude all cluster nodes from proxy and other resources, add other resources here. additio... | proxy values in order to update package manager and docker daemon to use proxies and custom CA for https_proxy if needed http_proxy: "http://proxy.fake-proxy.com:911" https_proxy: "http://proxy.fake-proxy.com:912"
## If you need exclude all cluster nodes from proxy and other resources, add other resources here. additio... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8d7d53ea-dcfb-4bca-81be-849660ffec66 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 21 | opea-semantic-v1 | 622808f433b638e2 | be listening on from 6443 to 8080. By default Kubespray configures kube_control_plane hosts with insecure access to kube-apiserver via port 8080. Refer to [kubespray getting-started](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting_started/getting-started.md)
# The port the API Server will be liste... | ai_ref_knowledge | OPEA Documentation | be listening on from 6443 to 8080. By default Kubespray configures kube_control_plane hosts with insecure access to kube-apiserver via port 8080. Refer to [kubespray getting-started](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting_started/getting-started.md)
# The port the API Server will be liste... | be listening on from 6443 to 8080. By default Kubespray configures kube_control_plane hosts with insecure access to kube-apiserver via port 8080. Refer to [kubespray getting-started](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting_started/getting-started.md)
# The port the API Server will be liste... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
962a1483-0d30-4ebd-94f9-5bc581896aa9 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 5 | opea-semantic-v1 | 4585ea1839dd94d3 | container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. Refer to [Kubernetes installation demo using kubeadm](./k8s_install_kubeadm.md) to clean up the environment.
## Prerequisites | ai_ref_knowledge | OPEA Documentation | container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. Refer to [Kubernetes installation demo using kubeadm](./k8s_install_kubeadm.md) to clean up the environment.
## Prerequisites | container runtime(i.e. docker, containerd, etc.), please make sure you have clean-up those first. Refer to [Kubernetes installation demo using kubeadm](./k8s_install_kubeadm.md) to clean up the environment.
## Prerequisites | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9c3081f8-3516-4af9-966e-c5a7ef3e6e52 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 3 | opea-semantic-v1 | f860f508ce948c75 | System | | ---------- | ------------------ | ---------------- | | k8s-master | 192.168.121.35/24 | Ubuntu 22.04 | | k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 |
We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository. | 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 |
We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository. | System | | ---------- | ------------------ | ---------------- | | k8s-master | 192.168.121.35/24 | Ubuntu 22.04 | | k8s-worker | 192.168.121.133/24 | Ubuntu 22.04 |
We assume these two machines are used for Kubernetes 2-node cluster. They have direct internet access both in bash terminal and in apt repository. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
acd25589-d72e-4c17-a1f3-0d9f9ff84edb | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 18 | opea-semantic-v1 | c99aca8f16de95ff | ## Step 3. Define Kubernetes configuration
Kubespray gives you ability to customize Kubernetes instalation, for example define:
- network plugin
- container manager
- kube_apiserver_port
- kube_pods_subnet
- all K&s addons configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those se... | ai_ref_knowledge | OPEA Documentation | ## Step 3. Define Kubernetes configuration
Kubespray gives you ability to customize Kubernetes instalation, for example define:
- network plugin
- container manager
- kube_apiserver_port
- kube_pods_subnet
- all K&s addons configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those se... | ## Step 3. Define Kubernetes configuration
Kubespray gives you ability to customize Kubernetes instalation, for example define:
- network plugin
- container manager
- kube_apiserver_port
- kube_pods_subnet
- all K&s addons configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those se... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
af86e63f-c8b5-437e-913d-ec50543d7d11 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 44 | opea-semantic-v1 | e39c5e0228d6d9aa | Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is:
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| third-node | 192.168.121.134/24 | Ubuntu 22.04 | | ai_ref_knowledge | OPEA Documentation | Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is:
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| third-node | 192.168.121.134/24 | Ubuntu 22.04 | | Assume you've already have a two-node K8s cluster and you want to scale it to three nodes. The third node information is:
| hostname | ip address | Operating System |
| ---------- | ------------------ | ---------------- |
| third-node | 192.168.121.134/24 | Ubuntu 22.04 | | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b0bc4b04-7689-4cd6-9c4c-ced5761fd38c | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 24 | opea-semantic-v1 | 81e1c4a25757416d | to run! # And be mindful that it will remove the current Kubernetes cluster (if it's running)! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false reset.yml
Then you can deploy Kubernetes with Ansible playbook with following command: | ai_ref_knowledge | OPEA Documentation | to run! # And be mindful that it will remove the current Kubernetes cluster (if it's running)! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false reset.yml
Then you can deploy Kubernetes with Ansible playbook with following command: | to run! # And be mindful that it will remove the current Kubernetes cluster (if it's running)! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false reset.yml
Then you can deploy Kubernetes with Ansible playbook with following command: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b25cb14e-afe2-496f-8755-2ea328fc49c2 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 39 | opea-semantic-v1 | a5f09f7a753fbd71 | Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command:
sed -i "s/node1/k8s-master/g" inventory/mycluster/hosts.ini | ai_ref_knowledge | OPEA Documentation | Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command:
sed -i "s/node1/k8s-master/g" inventory/mycluster/hosts.ini | Edit your single-node inventory `inventory/mycluster/hosts.ini` to replace the node name from `node1` to your real node name (for example `k8s-master`) using following command:
sed -i "s/node1/k8s-master/g" inventory/mycluster/hosts.ini | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b4e462f8-f65b-444f-883c-f5abfa4aca21 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 7 | opea-semantic-v1 | d5f054b95018b32a | the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine.
Please make sure that the operating machine can login to both K8s nodes via SSH without a password prompt. There are different ways to configure the ssh login wi... | ai_ref_knowledge | OPEA Documentation | the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine.
Please make sure that the operating machine can login to both K8s nodes via SSH without a password prompt. There are different ways to configure the ssh login wi... | the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine.
Please make sure that the operating machine can login to both K8s nodes via SSH without a password prompt. There are different ways to configure the ssh login wi... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b5e236ed-a5f4-459e-b98e-70b9de3e1962 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 16 | opea-semantic-v1 | 7cec4f4817d19a99 | cp -r inventory/sample inventory/mycluster
Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows: | ai_ref_knowledge | OPEA Documentation | cp -r inventory/sample inventory/mycluster
Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows: | cp -r inventory/sample inventory/mycluster
Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
bac8785f-6806-4f88-9208-78bd2907991a | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 1 | opea-semantic-v1 | fa31a2fc594df9eb | to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's document](https://github.com/kubernetes-sigs/kubespray).
## Node preparation | ai_ref_knowledge | OPEA Documentation | to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's document](https://github.com/kubernetes-sigs/kubespray).
## Node preparation | to deploy a Kubernetes cluster. In this document, we choose to use the Ansible way. For other ways to use Kubespary, refer to [Kubespray's document](https://github.com/kubernetes-sigs/kubespray).
## Node preparation | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c640ee97-a351-40f0-bbc7-96dd99adc89b | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 11 | opea-semantic-v1 | 341d74c9dc0ab98c | Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide.
You shall set up a Python virtual environment and install Ansible and other Kubespray dependencies. Simply, you can just run following commands. You can also ... | ai_ref_knowledge | OPEA Documentation | Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide.
You shall set up a Python virtual environment and install Ansible and other Kubespray dependencies. Simply, you can just run following commands. You can also ... | Python3 (version >= 3.10) is required in this step. If you don't have, go to [Python website](https://docs.python.org/3/using/index.html) for installation guide.
You shall set up a Python virtual environment and install Ansible and other Kubespray dependencies. Simply, you can just run following commands. You can also ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c90be79c-def6-47ab-870c-46b9b1677264 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 6 | opea-semantic-v1 | e9dc94a975a7a5af | ## Prerequisites
We assume that there is a third machine as your operating machine. You can log in to this machine and execute the Ansible command. Any of the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine. | ai_ref_knowledge | OPEA Documentation | ## Prerequisites
We assume that there is a third machine as your operating machine. You can log in to this machine and execute the Ansible command. Any of the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine. | ## Prerequisites
We assume that there is a third machine as your operating machine. You can log in to this machine and execute the Ansible command. Any of the above two K8s nodes can be used as the operating machine. Unless otherwise specified, all the following operations are performed on the operating machine. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d09c04fb-bc31-460b-b944-6bd98fb218f4 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 26 | opea-semantic-v1 | e43d3b5a6c172205 | installing packages and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false cluster.yml
The Ansible playbooks will take several minutes to finish. After playbook is... | ai_ref_knowledge | OPEA Documentation | installing packages and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false cluster.yml
The Ansible playbooks will take several minutes to finish. After playbook is... | installing packages and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root -e override_system_hostname=false cluster.yml
The Ansible playbooks will take several minutes to finish. After playbook is... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d113b605-f98c-4520-8e9b-e8d6bf85b549 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 50 | opea-semantic-v1 | 17d4b1c4c574d163 | When the playbook is executed successfully, you can check if the third node is ready with following command:
kubectl get nodes | ai_ref_knowledge | OPEA Documentation | When the playbook is executed successfully, you can check if the third node is ready with following command:
kubectl get nodes | When the playbook is executed successfully, you can check if the third node is ready with following command:
kubectl get nodes | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d2fc0b7d-503e-4e40-a50c-05a598711a37 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 34 | opea-semantic-v1 | bb302661a4948b41 | ### How to deploy a single node Kubernetes?
Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster. | ai_ref_knowledge | OPEA Documentation | ### How to deploy a single node Kubernetes?
Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster. | ### How to deploy a single node Kubernetes?
Deploying a single-node K8s cluster is very similar to setting up a multi-node (>=2) K8s cluster. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d8ea4351-1642-443a-b52f-a90eaf23a5d0 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 47 | opea-semantic-v1 | 5cf776bdda6e5e4a | Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133
third-node ansible_host=192.168.121.134 | ai_ref_knowledge | OPEA Documentation | Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133
third-node ansible_host=192.168.121.134 | Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133
third-node ansible_host=192.168.121.134 | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d9bf2114-7b1e-44dd-a970-1142fa8e6737 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 19 | opea-semantic-v1 | 8c4c879c5ca8a0e1 | configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those settings are stored in group vars defined in `inventory/mycluster/group_vars`
For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml` | ai_ref_knowledge | OPEA Documentation | configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those settings are stored in group vars defined in `inventory/mycluster/group_vars`
For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml` | configurations, or even define to deploy cluster on hyperscaller like AWS or GCP. All of those settings are stored in group vars defined in `inventory/mycluster/group_vars`
For K&s settings look in `inventory/mycluster/group_vars/k8s_cluster/k8s-cluster.yml` | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
da4a1da2-a34c-407f-a84e-26fd6fa25228 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 36 | opea-semantic-v1 | 3f407c405e455773 | Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment.
And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following: | ai_ref_knowledge | OPEA Documentation | Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment.
And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following: | Follow the previous [Step 1. Set up Kubespray and Ansible](#step-1-set-up-kubespray-and-ansible) to set up the environment.
And then in [Step 2. Build your own inventory](#step-2-build-your-own-inventory), you can create single-node Ansible inventory by copying the single-node inventory sample as following: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
dae4852f-c120-4c0f-a1d0-3ccf9c1d5a23 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 40 | opea-semantic-v1 | 6f92fbbbf8cbb401 | [k8s_cluster:children] kube_node kube_control_plane
And then follow [Step 3. Deploy Kubernetes](#step-3-deploy-kubernetes), please pay attention to the **inventory name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you... | ai_ref_knowledge | OPEA Documentation | [k8s_cluster:children] kube_node kube_control_plane
And then follow [Step 3. Deploy Kubernetes](#step-3-deploy-kubernetes), please pay attention to the **inventory name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you... | [k8s_cluster:children] kube_node kube_control_plane
And then follow [Step 3. Deploy Kubernetes](#step-3-deploy-kubernetes), please pay attention to the **inventory name** while executing Ansible playbook, which is `inventory/mycluster/hosts.ini` in single node deployment. When the playbook is executed successfully, you... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
dc63f37f-13f7-477a-a8b3-bede8a384947 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 17 | opea-semantic-v1 | 54efbe8d05bd8147 | Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133 | ai_ref_knowledge | OPEA Documentation | Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133 | Edit your inventory file `inventory/mycluster/inventory.ini` to config the node name and IP address. The inventory file used in this demo is as follows:
[all]
k8s-master ansible_host=192.168.121.35
k8s-worker ansible_host=192.168.121.133 | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
dd8ab16d-53d5-4303-a84b-b152af87310f | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 46 | opea-semantic-v1 | 5d77af1a97eefbfa | Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine.
Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following: | ai_ref_knowledge | OPEA Documentation | Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine.
Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following: | Make sure the third node has internet access and can be logged in via `SSH` without password promotion from your operating machine.
Edit your Ansible inventory file to add the third node information to `[all]` and `[kube_node]` section as following: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ddc9ccc7-f014-4b36-bbc7-f0fb162ab718 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 49 | opea-semantic-v1 | 40e2b65f8c31f0ac | and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --limit third-node --become --become-user=root scale.yml -b -v
When the playbook is executed successfully, you can check if the third node is ready with following command... | ai_ref_knowledge | OPEA Documentation | and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --limit third-node --become --become-user=root scale.yml -b -v
When the playbook is executed successfully, you can check if the third node is ready with following command... | and interacting with various systemd daemons. # Without --become the playbook will fail to run! ansible-playbook -i inventory/mycluster/inventory.ini --limit third-node --become --become-user=root scale.yml -b -v
When the playbook is executed successfully, you can check if the third node is ready with following command... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e990f985-d2a8-4152-850b-c29091bf1e87 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 53 | opea-semantic-v1 | e5df8045fce0decc | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
You can change parameters in `inventory/mycluster/group_vars/all/all.yml` to set `http_proxy`,`https_proxy`, and `additional_no_proxy` as following. Please make sure you've added all the nodes' ip addresses into the `addition... | ai_ref_knowledge | OPEA Documentation | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
You can change parameters in `inventory/mycluster/group_vars/all/all.yml` to set `http_proxy`,`https_proxy`, and `additional_no_proxy` as following. Please make sure you've added all the nodes' ip addresses into the `addition... | - http_proxy="http://proxy.fake-proxy.com:911" - https_proxy="http://proxy.fake-proxy.com:912"
You can change parameters in `inventory/mycluster/group_vars/all/all.yml` to set `http_proxy`,`https_proxy`, and `additional_no_proxy` as following. Please make sure you've added all the nodes' ip addresses into the `addition... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f7696e87-5f7d-4350-81fc-adfd9a90c975 | OPEA Documentation | file://datasets/opea-docs/guide/installation/k8s_install/k8s_install_kubespray.md | unknown | 1ebc04c4-1efd-4bbf-84af-881569c3db1b | 42 | opea-semantic-v1 | 358f35fd2245aac5 | And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the status by `kubectl get nodes`.
### How to scale Kubernetes cluster to add more nodes? | ai_ref_knowledge | OPEA Documentation | And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the status by `kubectl get nodes`.
### How to scale Kubernetes cluster to add more nodes? | And the follow [Step 4. Create kubectl configuration](#step-4-create-kubectl-configuration) to set up `kubectl`. You can check the status by `kubectl get nodes`.
### How to scale Kubernetes cluster to add more nodes? | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0c41f604-98e8-4c34-b04f-37746bba0011 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 6 | opea-semantic-v1 | 57c5cf88d0bbf8b7 | `main` branch of OPEA projects. It typically occurs two weeks before the scheduled OPEA release. After this point, first round release test will be triggered.
## Code/Doc Freeze, and Creating the RC Branch | ai_ref_knowledge | OPEA Documentation | `main` branch of OPEA projects. It typically occurs two weeks before the scheduled OPEA release. After this point, first round release test will be triggered.
## Code/Doc Freeze, and Creating the RC Branch | `main` branch of OPEA projects. It typically occurs two weeks before the scheduled OPEA release. After this point, first round release test will be triggered.
## Code/Doc Freeze, and Creating the RC Branch | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2c4c7ba5-fbce-45c9-bb46-73a798700404 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 7 | opea-semantic-v1 | 87bd072aa5b3c174 | ## Code/Doc Freeze, and Creating the RC Branch
This is the point in the OPEA release cycle to create the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered. | ai_ref_knowledge | OPEA Documentation | ## Code/Doc Freeze, and Creating the RC Branch
This is the point in the OPEA release cycle to create the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered. | ## Code/Doc Freeze, and Creating the RC Branch
This is the point in the OPEA release cycle to create the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
35aa4cef-cc7b-4ec6-9d55-91a42c016717 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 12 | opea-semantic-v1 | 8ff81d62e740685e | ## Cherry Pick Critical Code/Doc Fix Fixes for critical issues after code freeze must cherry-pick into the RC branch.
### How to do Cherry Picking
Critical issues found in the RC branch must be fixed in the `main` branch and then cherry-picked into the RC branch. Cherry-picking will be done manually by the CI/CD owner. | ai_ref_knowledge | OPEA Documentation | ## Cherry Pick Critical Code/Doc Fix Fixes for critical issues after code freeze must cherry-pick into the RC branch.
### How to do Cherry Picking
Critical issues found in the RC branch must be fixed in the `main` branch and then cherry-picked into the RC branch. Cherry-picking will be done manually by the CI/CD owner. | ## Cherry Pick Critical Code/Doc Fix Fixes for critical issues after code freeze must cherry-pick into the RC branch.
### How to do Cherry Picking
Critical issues found in the RC branch must be fixed in the `main` branch and then cherry-picked into the RC branch. Cherry-picking will be done manually by the CI/CD owner. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
367055d6-d985-470a-8767-b4b735f2f7d6 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 10 | opea-semantic-v1 | cd07fbcf993ba0c0 | ### Creating RC Branch The RC branch are typically created from the `main` branch. The branch name must follow the following format:
v{MAJOR}.{MINOR}rc | ai_ref_knowledge | OPEA Documentation | ### Creating RC Branch The RC branch are typically created from the `main` branch. The branch name must follow the following format:
v{MAJOR}.{MINOR}rc | ### Creating RC Branch The RC branch are typically created from the `main` branch. The branch name must follow the following format:
v{MAJOR}.{MINOR}rc | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
41a48fa2-e955-424d-8e37-e6e5873f2fb5 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 2 | opea-semantic-v1 | 9a154e11606a3e0f | | | 1.4 | Jul 2025 | | 1.5 | Oct 2025 | | 1.6 | Jan 2026 | | 1.7 | Apr 2026 |
## General Overview | ai_ref_knowledge | OPEA Documentation | | | 1.4 | Jul 2025 | | 1.5 | Oct 2025 | | 1.6 | Jan 2026 | | 1.7 | Apr 2026 |
## General Overview | | | 1.4 | Jul 2025 | | 1.5 | Oct 2025 | | 1.6 | Jan 2026 | | 1.7 | Apr 2026 |
## General Overview | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
41b4d44a-ba4b-46f6-8c69-09b2d448cc76 | OPEA Documentation | file://datasets/opea-docs/release_notes/RELEASE.md | unknown | b2ec92c4-07dc-4718-9d2d-793da944870e | 8 | opea-semantic-v1 | 7be2cc29869cdacc | the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered.
### Preparing Creating RC Branch
Following requirements needs to be met prior to creating the RC branch:
- Implement all features and functionalities targeting... | ai_ref_knowledge | OPEA Documentation | the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered.
### Preparing Creating RC Branch
Following requirements needs to be met prior to creating the RC branch:
- Implement all features and functionalities targeting... | the Release Candidate (RC) branch. It typically occurs one week before the scheduled OPEA release. After this point, final round release test will be triggered.
### Preparing Creating RC Branch
Following requirements needs to be met prior to creating the RC branch:
- Implement all features and functionalities targeting... | 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.