Replies: 2 comments 3 replies
-
|
Hi @Ongy, do you mind elaborating. I don't really understand the question |
Beta Was this translation helpful? Give feedback.
-
|
Due to $reason I want to run piko on a port/hostname combination that already runs other HTTP based services. Kubernetes ingress rules make this easy. There's various L7 attributes (path/header for the most part) that can be matched on to direct to the correct backend. |
Beta Was this translation helpful? Give feedback.
-
|
I still don't really understand Are you referring to how to configure your Kubernetes ingress rule to route traffic to the Piko server? |
Beta Was this translation helpful? Give feedback.
-
|
Yea, that's what I meant. I tested it by now and saw that the paths used on the upgrade requests are sufficiently unique for my use. |
Beta Was this translation helpful? Give feedback.
-
|
ok great |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Can the URL also contain PATH elements?
If not, is there an easy way to route the requests? E.g. by a unique enough header?
I guess worst case I could set a pseudo token as auth JWT and match on that instead of using it for auth?
Beta Was this translation helpful? Give feedback.
All reactions