Comments (12)
I've solved the issue by running minikube tunnel
and changing my hosts file entries to 127.0.0.1
instead of the minikube IP.
from helm3.
Hello, the ip address of your minikube node might have changed .. Please could you check what returns "minikube ip" command ?
from helm3.
It is as expected:
mark@minikube-vm:~/helm/lab7_helm_template_final/chart$ minikube ip
192.168.99.100
mark@minikube-vm:~/helm/lab7_helm_template_final/chart$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
demo-guestbook default 1 2020-09-07 15:30:43.612544026 +0000 UTC deployed guestbook-1.2.0 2.0
mark@minikube-vm:~/helm/lab7_helm_template_final/chart$ ping frontend.minikube.local
PING frontend.minikube.local (192.168.99.100) 56(84) bytes of data.
64 bytes from frontend.minikube.local (192.168.99.100): icmp_seq=1 ttl=64 time=1.17 ms
64 bytes from frontend.minikube.local (192.168.99.100): icmp_seq=2 ttl=64 time=0.308 ms
64 bytes from frontend.minikube.local (192.168.99.100): icmp_seq=3 ttl=64 time=0.539 ms
64 bytes from frontend.minikube.local (192.168.99.100): icmp_seq=4 ttl=64 time=0.381 ms
64 bytes from frontend.minikube.local (192.168.99.100): icmp_seq=5 ttl=64 time=0.339 ms
^C
--- frontend.minikube.local ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4074ms
rtt min/avg/max/mdev = 0.308/0.548/1.177/0.325 ms
mark@minikube-vm:~/helm/lab7_helm_template_final/chart$ wget http://frontend.minikube.local
--2020-09-08 14:59:39-- http://frontend.minikube.local/
Resolving frontend.minikube.local (frontend.minikube.local)... 192.168.99.100
Connecting to frontend.minikube.local (frontend.minikube.local)|192.168.99.100|:80... failed: Connection refused.
mark@minikube-vm:~/helm/lab7_helm_template_final/chart$
The minikube dashboard shows the application is running. The backend fails, but it is expected (I am on lab 7).
So, all works as you describe in the course, except I am unable to navigate the application itself. I suppose it has to do with some absent configuration on my fresh new linux VM.
from helm3.
A quick update. I installed wordpress as instructed in the last chapter and it worked.
I think the instructions to run the guestbook are lacking something.
from helm3.
Hello, could you check the ingress is enabled with minikube addons enable ingress
command ?
Are their any logs for the frontend pod with kubectl logs --previous
?
Make sure there is no old K8s ressources before installing again with Helm.
You could also try to set the frontend service to NodePort type and try to access it with the NodePort to see if it can be accessed.
from helm3.
That is what was missing - minikube addons enable ingress
.
Apparently, after recreating the VM I have not run this command.
Interesting though why it was not needed for the wordpress application?
from helm3.
OK I close the issue. Wordpress is not using the ingress but we access it using a Nodeport (as mentioned in the demo at 1'56")
from helm3.
Is there any configuration to enable the host minikube.local?
I cannot reach that host. Ingress is enables on minikube
from helm3.
Hello, you should resolve the frontend and backend dns names to the minikube ip in the hosts file (as showed in the course at the end of the environnement setup)
from helm3.
I'm having a similar issue. This is my manifest
# Source: guestbook/templates/frontend-service.yaml
apiVersion: v1
kind: Service
metadata:
labels:
name: frontend
name: frontend
spec:
ports:
- protocol: "TCP"
port: 80
targetPort: 4200
selector:
app: frontend
---
# Source: guestbook/templates/frontend.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: frontend
spec:
replicas: 1
selector:
matchLabels:
app: frontend
template:
metadata:
labels:
app: frontend
spec:
containers:
- image: phico/frontend:1.0
imagePullPolicy: Always
name: frontend
ports:
- name: frontend
containerPort: 4200
---
# Source: guestbook/templates/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: guestbook-ingress
spec:
rules:
- host: frontend.minikube.local
http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: frontend
port:
number: 80
- host: backend.minikube.local
http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: backend
port:
number: 80
I've added my minikube IP to the host file, but when I ping the address it times out:
Pinging frontend.minikube.local [192.168.49.2] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.49.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I've tried restarting minikube and kubernetes, as well as reinstalling the chart but to no effect. Please adivse!
from helm3.
This solution of replacing miikube ip with 127.0.0.1 in hosts works.. Thanks..
from helm3.
Should I change something for microk8s?
from helm3.
Related Issues (7)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from helm3.