TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Kubernetes ingress re-write for FEs

1 pointsby yonzover 1 year ago
What is the proper way to set rewrite rules that can handles requests after first load, For example &lt;HTML&gt; relative path requests for assets or hrefs?<p>Lets say you have homebase.com&#x2F;kubedash and homebase.com&#x2F;qdrant, what is the best practice for supporting these two services.<p>- homebase.com&#x2F;qdrant --&gt; qdrant:port&#x2F;<p>- homebase.com&#x2F;qdrant&#x2F;dashboard --&gt; qdrant:port&#x2F;dashboard<p>- homebase.com&#x2F;kubedash --&gt; kubernetes-dashboard:80&#x2F;<p>The problem i run into is that each of the services load an HTML with relative paths to the &#x27;re-written&#x27; request. In other words qdrant:port&#x2F;dashboard HTML will try to fetch `homebase.com&#x2F;dashboard&#x2F;assets` but your re-write rule would only handle it if its, `homebase.com&#x2F;qdrant&#x2F;dashboard&#x2F;assets`<p>There are many answers and suggestions but i&#x27;ve worked through most and have realized that either your href or your assets or something else will break it. The solution I have found is to use subdomains.<p>What is the right way to do this? This feels like the basic feature for ingress controller.

no comments

no comments