This repository has been archived by the owner on Dec 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Minikube QuickStart Guide Feedback #894
Comments
This little guide is great as of May 2023. Within "deploy/kubernetes/manifests/03-carts-db-dep.yaml" and "deploy/kubernetes/manifests/13-orders-db-dep.yaml" Use an older mongo image. Such as mongo:5.0.11. Otherwise the cart and older pods will produce errors. |
The same issue with the mongo image can/should also be applied, if you are using the Also i found that the : combinations also work, if the address gotten from the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello Everyone :)
This post is an improvement suggestion based on what was my point of view as someone new trying to implement the quick start guide for minikube and the issues that i had to solve that the guide did not specifiy. (https://microservices-demo.github.io/deployment/kubernetes-minikube.html)
i added this env variable in the elasticsearch.yaml
The image version for the containers in elasticsearch.yaml and kibana.yaml does not work by default needed to change to
elasticsearch: 7.12.1
andkibana: 7.12.1
respectively.Depending on the kubernetes version being used by minikube the apiVersion for fluentd-cr.yaml and fluentd-crb.yaml may be deprecated (v 1.22 above is deprecated and need to be changed to
apiVersion: rbac.authorization.k8s.io/v1
)The tutorial mentions that after i deploy the manifests for logging i should be able to access the kibana dashboard.
"You should be able to see the Kibana dashboard at http://192.168.99.100:31601."
But that is not true for everyone. You need to create a tunnel to be able to access the service by opening a new shell and using
minikube service {service-name}
. or in my case when we are using the docker driver on Windows it needs to use port-forward of the kibana pod usingkubectl port-forward {Kibana-pod-name} -n kube-system 5601:5601
and with that i was able to access the dashboard.(More info on the topic here Pod not accessible on NodePort via the Windows 10 host machine. kubernetes/minikube#9499)
The command
kubectl create -f deploy/kubernetes/manifests/sock-shop-ns.yaml
has the wrong path since the file for the namespace is currently named 00-sock-shop-ns.yamlPoint 4 is repeated to access the sockShop itself has the service is a NodePort as well.
Hope it is clear, any doubts or different opinions please feel free to discuss 👍
The text was updated successfully, but these errors were encountered: