Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid kubectl #183

Open
rcbarke opened this issue Sep 11, 2024 · 0 comments
Open

Invalid kubectl #183

rcbarke opened this issue Sep 11, 2024 · 0 comments

Comments

@rcbarke
Copy link

rcbarke commented Sep 11, 2024

Following the O-RAN Near-Real Time RIC Installation Guide located here:
https://openaicellular.github.io/oaic/oran_installation.html

The below script contains an issue with its kubernetes install:
sudo ./k8s-1node-cloud-init-k_1_16-h_2_17-d_cur.sh

Dependencies:
This script depends on curl being installed (sudo apt-get install curl)

Issue:
During execution of the script kubectl will present several localhost:8080 connection refused errors
When the script is stopped, kubectl cluster-info reveals that kubernetes is not properly installed

Resolution

  1. Attempt the process within the O-RAN Near-Real Time RIC Installation Guide until the connection refused errors are encountered. Halt the ./k8s-1node-cloud-init-k_1_16-h_2_17-d_cur.sh script.

  2. Install the latest K8S via https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/

    • Ensure to follow the instructions to install K8S in ~/.local/bin, not your local user directory
  3. Restart kubelet with sudo systemctl restart kubelet

  4. Retry sudo ./k8s-1node-cloud-init-k_1_16-h_2_17-d_cur.sh

  5. The connection refused errors will be gone, K8S pods will appropriately deploy, and the remaining instructions can be followed to setup influxDB and deploy the OAIC RIC

Important: Order of operations is pertinent here. If K8S is pre-installed before the OIAC installation script is run, the OAIC installation script will begin throwing different TCPIP errors stating localhost cannot be resolved. These appear to be due to an invalid ~/.kube/config

--

Where is the error within ./k8s-1node-cloud-init-k_1_16-h_2_17-d_cur.sh creating this behavior?

Just to note, containerizing this environment with docker would drastically simply this installation procedure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant