I would llike to try Istio on Openshift platform. Could somebody confirm if succesfully install Istio locally on Openshift on Windows 10 machine?
I am not able to run the newest Openshift (oc 3.11 or oc 3.10) because of error
error: cannot create volume share
And I can't run Istio on Openshift 3.9 because some Istio components won't start. Also on official page only Openshift version 3.10+ is mentioned.
Is it worth to try Istio with Openshift 3.9 ?
Currently, I think Istio is not stable to be Enterprise Ready, so Red Hat does not make it in its official supported list.
If you want just give a try with this, I highly recommend you to take a look at this https://learn.openshift.com/servicemesh/ to avoid the boring installation things.
Related
I'm trying to install istio on AKS and I came across some resources which required installing istio on my local machine first. I couldn't understand the local machine part.I did try installing istio on my local machine but ran into a networking error saying that the target machine does not respond. Can you please help me with any good step-by-step resource other than the official documentation for istio installation? Thank you.
On macOS there's Docker Desktop which comes with a kubectl, there's the Homebrew kubectl, then there's the gcloud kubectl.
I'm looking to use Minikube for local Kubernetes development and also GKE for production.
Which kubectl should I use? I'm thoroughly confused by all the various versions and how they differ from one another. Does it matter at all other than the version of the binary?
It doesn't really matter from where you get an executable as long as it is a trusted source. Although you have to use a supported version (documentation):
kubectl is supported within one minor version (older or newer) of kube-apiserver.
Example:
kube-apiserver is at 1.20
kubectl is supported at 1.21, 1.20, and 1.19
I'm going to upgrade my Kubernetes cluster to the version 1.8.7. Does anybody know which docker version is best compatible with it?
This is what I found on the Kubernetes official page, but I suppose it might be for the latest k8s release (1.9)?
On each of your machines, install Docker. Version v1.12 is
recommended, but v1.11, v1.13 and 17.03 are known to work as well.
Versions 17.06+ might work, but have not yet been tested and verified
by the Kubernetes node team.
Thank you!
According to the kubernetes v1.8.0 changelog
Continuous integration builds use Docker versions 1.11.2, 1.12.6, 1.13.1, and 17.03.2. These versions were validated on Kubernetes 1.8.
So any of these version should work fine.
I have a pod in which i have image ubuntu desktop i connect to this image via xrdp what i want to do is to add eclipse image to this pod in other words when i connect to this ubuntu desktop i can find eclipse.
I am going to create platform based on kubernetes with image catalog.
For example a profesor of java want only ubuntu desktop and eclipse. He gonna choose from catalog ubuntu and eclipse all backend i will do it myself.
So when a student connect he will find eclipse on ubuntu desktop.
You have to create an image from a dockerfile recipe that includes a command for installing the eclipse package.
Then you can use your own image for the deployment into the cluster (instead of the ubuntu image you are using today).
Please read up how to create a docker container and dockerfile documentation.
You can also take a look at an example dockerfile.
I want to run Cloudera using a Docker image (specifically, the cloudera/quickstart image).
However, on Docker Hub I can only find beta versions:
https://hub.docker.com/r/cloudera/quickstart/tags/
What's the correct way of getting a more up-to-date image?
Should I just download a beta image and then install parcels? Would I do that using Docker Compose? If so, can I find instructions for that online?
Or is there a completely different way to solve this?
To run Cloudera Quickstart within Docker, follow the instructions on that page:
https://www.cloudera.com/documentation/enterprise/latest/topics/quickstart_docker_container.html
Forget about your concerns regarding the "beta" tag. These tags are there, because the Docker image of Cloudera Quickstart is in beta mode. However, the CDH version in there is not.
You will find this out on your own, once you run the container and check the CDH version inside.