bureaucraten, interfacemoderatoren, Beheerders (Semantic MediaWiki), Curatoren (Semantic MediaWiki), Redacteuren (Semantic MediaWiki), toezichthouders, beheerders
205
bewerkingen
→Accessing a Deployment using an Ingress
| Regel 838: | Regel 838: | ||
Having this set up should cause <code>http://kubetest.sjorsgielen.nl/</code> to end up within Traefik. It will give a "404 page not found" result, as Traefik doesn't know about any Ingresses yet to forward your request to. | Having this set up should cause <code>http://kubetest.sjorsgielen.nl/</code> to end up within Traefik. It will give a "404 page not found" result, as Traefik doesn't know about any Ingresses yet to forward your request to. | ||
You can check the Traefik dashboard to see that it's up. Currently, we'll need a port-forward for that: | |||
<code> | |||
$ kubectl port-forward -n kube-system deployment/traefik-ingress 8080:8080 | |||
Forwarding from [::1]:8080 -> 8080 | |||
Forwarding from 127.0.0.1:8080 -> 8080 | |||
</code> | |||
Now, visit <code>http://localhost:8080/</code> and you should see the Traefik dashboard. It will show no frontends and no backends, as we haven't created any Ingresses yet for it to route. So let's create one for our Nginx service: | |||
<code> | |||
$ cat ingress.yaml | |||
apiVersion: extensions/v1beta1 | |||
kind: Ingress | |||
metadata: | |||
name: nginx-ingress | |||
annotations: | |||
traefik.frontend.rule.type: PathPrefixStrip | |||
spec: | |||
rules: | |||
- host: kubetest.sjorsgielen.nl | |||
http: | |||
paths: | |||
- path: /nginx | |||
backend: | |||
serviceName: nginx-service | |||
servicePort: 80 | |||
$ kubectl apply -f nginx.yaml | |||
ingress.extensions/nginx-ingress created | |||
</code> | |||
So what does this mean? | |||
* It's an Ingress type, meaning it's a message to the cluster/Traefik that we want to have a Service externally accessible over HTTP. | |||
* The service will be reachable on the Host <code>kubetest.sjorsgielen.nl</code> -- this acts like a sort of virtual server in Apache, where different hosts can serve different content. | |||
* The request Path must begin with <code>/nginx</code>; the <code>traefik.frontend.rule.type: PathPrefixStrip</code> annotation will cause the <code>/nginx</code> prefix to be stripped off before the request is forwarded. | |||
* The requests will be forwarded to the <code>nginx-service</code> service on port 80. | |||
In other words, http://kubetest.sjorsgielen.nl/nginx/index.html will be forwarded to http://nginx-service/index.html. And indeed, it shows the same Nginx page again! Also, if you go to the Traefik dashboard again, you'll see the frontend and backend have appeared and also you'll be able to see the average response time on the Health tab. | |||
= Creating your own images = | = Creating your own images = | ||