-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Help accessing Eclipse Che with Minikube and KVM on external machine #16414
Comments
@tolusha will you be able to take a look at that one? |
That's very interesting task, but unfortunately I don't have an appropriate environment. |
@l0rd @davidfestal @benoitf maybe you can take a look at this setup and suggest smth |
At this point, KVM acceleration isn't important anymore. I believe the most productive way is to focus on a remote bare metal install. Example environments would be an AWS EC2 instance or Vultr which doesn't appear to offer a managed K8s solution. I would still use the setup pictured above, but I hope a tutorial that applies to a hosted bare metal server (without managed k8s) would also apply to a local machine. |
@gnoejuan would you like to try with crc(local openshift 4 ) there is a guide for it https://gist.github.com/tmckayus/8e843f90c44ac841d0673434c7de0c6a ? |
We use minikube running on a remote machine for our e2e tests. Maybe @rhopp @dmytro-ndp have some suggestions. |
Hello @gnoejuan, i've just finish to setup something i think similar to your needs, running completely inside a private network. This is the abstract, let me know if i can give you more informations:
Let me know if i can provide more insight. |
For this one, I'm stuck at But it looks like it should have been fixed here: SELinuxProject/selinux#81 (comment)
Here, I get so close. It had stopped right at "Starting Che." It times out, and gives a directory for the logs /tmp/chexxxxxxx. When I navigate to the dir, it doesn't exist. I'm curious if this is a problem with installing on Ubuntu 18.04.4 LTS for both solutions. I am working on downloading Ubuntu 16.04.6 LTS |
@gnoejuan could you get around the |
I was unable to get around the issue. It has been awhile since I was tackling CRC method to deploy a k8s cluster. My recollection was the recommended Ubuntu version at the time was lower than 18.04, but the KVM version that came with Ubuntu 16 was too old. Researching how to upgrade KVM only returned results on installing QEMU/KVM.
https://code-ready.github.io/crc/ After trying RancherOS (Supposedly due to be obsoleted rancher/os#3000 (comment)), k3OS never seemed to resolve an IP address, Fedora's CoreOS required learning another technology called Ignition. . . . After researching Kubernetes more thoroughly, it appears the fastest/easiest path to a local Kubernetes server is to use kubectl. Personally, I chose to use microk8s on the Microk8s guide: https://microk8s.io/docs/working-with-kubectl tl;dr: on k8s machine: Assuming you don't have a .kube in your home directory
put the config file from earlier in the .kube folder
where Minikube guide: https://medium.com/@kuljeetsinghkhurana/access-minikube-using-kubectl-from-remote-machine-2b0eeefad9cb In theory, Although this experience has dragged me into the world of Kubernetes kicking and screaming, I enjoyed the learning experience. |
I'm also looking for answer; |
Summary
tl;dr
This is my setup, what is the proper way of using Minikube (for KVM acceleration)? Or perhaps is Minikube the wrong approach? Should I deploy a different solution for k8s? I'm open to installing a new operating system on the k8s machine (such as k3os or any other k8s focused OS). I had already backed up all my data.
Things I've tried
Follow the K8s tutorial here: Exposing an External IP Address to Access an Application in a Cluster
kubectl --namespace che expose deployment/che --type="LoadBalancer " --name=che-service
Leads to an External IP always staying pending, so I followed the advice here: EXTERNAL-IP is always none and unable to reach to Service from Host machine #723 kubernetes/minikube#3966 (comment) and used `minikube tunnel'. This gave another internal IP address, although it was 10.x.x.x
Following KVM: Creating a bridged network with NetPlan on Ubuntu bionic, I appear to now be faced with minikube being unable to resolve k8s
! Node may be unable to resolve external DNS records ! VM is unable to access k8s.gcr.io, you may need to configure a proxy or set --image-repository
chectl doesn't thow any errors, but I'm not seeing any bandwidth activity.
I was able to quickly understand Docker, but with k8s, I feel like I'm way in over my head.
Relevant information
The text was updated successfully, but these errors were encountered: