For the hazelcast install, run this instead: > kubectl create deployment myhazelcast --image=hazelcast/hazelcast --port=5701 Note "hazelcast/hazelcast" or else kubectl probably won't find the image (over at Docker I believe)
It most likely means there is or was a network issue when trying to pull the image. Or the URL to the image is incorrect, or the tag is not correct. At this point I don't know how to independently check on this, but likely it's not your minikube.
So Kubernetes is about container orchestration. Deploying large numbers of containers with the same functionality is a major capability. How does this exist with Eureka and its service registration and service discovery capabilities? Are they both doing similar things and therefore are they mutually exclusive?
Eureka and Kubernetes are primarily classified as "Open Source Service Discovery" and "Container" tools respectively. "Easy setup and integration with spring-cloud " is the primary reason why developers consider Eureka over the competitors, whereas "Leading docker container management solution" was stated as the key factor in picking Kubernetes. Eureka and Kubernetes are both open source tools. It seems that Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub has more adoption than Eureka with 7.98K GitHub stars and 2.2K GitHub forks.
For the hazelcast install, run this instead:
> kubectl create deployment myhazelcast --image=hazelcast/hazelcast --port=5701
Note "hazelcast/hazelcast" or else kubectl probably won't find the image (over at Docker I believe)
IIRC kubectl run is deprecated or at least not the best way. Use kubectl create deployment instead
Why is there ErrImagePull as state for hazelcast @8:40?
It most likely means there is or was a network issue when trying to pull the image. Or the URL to the image is incorrect, or the tag is not correct. At this point I don't know how to independently check on this, but likely it's not your minikube.
So Kubernetes is about container orchestration. Deploying large numbers of containers with the same functionality is a major capability.
How does this exist with Eureka and its service registration and service discovery capabilities? Are they both doing similar things and therefore are they mutually exclusive?
Eureka and Kubernetes are primarily classified as "Open Source Service Discovery" and "Container" tools respectively.
"Easy setup and integration with spring-cloud " is the primary reason why developers consider Eureka over the competitors, whereas "Leading docker container management solution" was stated as the key factor in picking Kubernetes.
Eureka and Kubernetes are both open source tools. It seems that Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub has more adoption than Eureka with 7.98K GitHub stars and 2.2K GitHub forks.
How does a client access these services? Is the code different from accessing one directly through knowing the IP address?
good course
HI, would you be interested in creating a written Kubernetes course for me?
Amazing and thanks for the nice tutorials
Why does he say "koobah" and not Kube like Queue-be ?
I can't stop focusing on this :)
interesting