Office Hours, coming up on Wed, May 16

office-hours

#1

Just a reminder that our monthly office hours will be taking place this next Wednesday, May 16 on #office-hours on slack and http://youtube.com/c/KubernetesCommunity/live

Office hours is where we have Kubernetes developers take live questions from the audience and then answer them in the livestream, so if you’ve got a question that’s been bugging you that you really need an answer to drop by and give us a chance!

We’ll also have Kubernetes swag that we’ll be raffling off to participants - so if you’ve always yearned for a k8s tshirt or socks then this could be your chance!

Check this out for more info!

Video:


#2

Just a reminder that we’re going to be going live this Wednesday, if you want to ask questions in the slack channel or put them in this thread we’ll read your question live on the air!


#3

Question around ingress, what happens if the path of different ingress resources for same ingress controller and in same namespace are partly overlapping each other? Will both be functional? If not, which one will be used?

Example:
First ingress routes /hello
Second ingress routes /hello/message

What happens in request for…
/hello?
/hello/message?
/hello/message/send?


#4

We’re going live now! Join us on #office-hours on slack and http://youtube.com/c/KubernetesCommunity/live and feel free to post your questions here!


#5

What ingress controller are you using?

EDIT: Some background info: https://github.com/kubernetes/ingress-nginx/issues/555


#6

Using nginx


#7

Just to point out, the time of day related to UTC for Europe is wrong. Both London and Berlin are in summer time now, so London is UTC+1 and Berlin is UTC+2 currently (opposed to 2pm UTC in the office-hours.md).


#8

Thanks! I’ve submitted a fix.


#9

I looked at what the nginx ingress controller will generate for the paths, the location rules will be as follows

no rewrite target

location /hello/message/send {...}
location /hello/message {...}
location /hello {...}

rewrite target set to "/"

location ~* ^/hello/message/send\/?(?<baseuri>.*) {...}
location ~* ^/hello/message\/?(?<baseuri>.*) {...}
location ~* ^/hello\/?(?<baseuri>.*) {...}

#10

Thanks for digging into this, very much appreciated. Definitely clarifies things :slight_smile:


#11

@errordeveloper The list of recommendations was very insightful! At ~ 53rd minute, you recommend not to use scratch as a base for a go binary. Why is that?