TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

A Primer: Accessing Services in Kubernetes

41 点作者 alexellisuk超过 3 年前

4 条评论

debarshri超过 3 年前
We have been using inlets when it had just come out in 2020. It is super robust. It is a great way to peer various cluster for eg. Other usecases where we use it is to connect multi cluster by expose api server to our platform. We had to build lot of tooling before around the product. Now it looks like they have build a pretty good stack around inlet[1].<p>From my perspective, it is like ngrok but for kubernetes.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;inlets" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;inlets</a>
cpitman超过 3 年前
Does anyone use k8s clusters that don&#x27;t come with Ingress these days? This article exposes a lot of complexity for what should just be &quot;use ingress&quot;.<p>More advanced ways to get traffic into the cluster are only really needed for non-https traffic. It comes up, but way more rarely.
评论 #30220997 未加载
评论 #30223105 未加载
ozarkerD超过 3 年前
The author mentions ingresses don’t work for non-http TCP traffic. Is that true?
评论 #30221750 未加载
erikcw超过 3 年前
Has anyone had success using WireGuard to VPN into their cluster and have local access to pods via K8s DNS?
评论 #30223228 未加载
评论 #30222726 未加载