r/kubernetes • • Nov 13 '25

We get ~4 months to move off of Ingress NGINX ?

77 Upvotes

I thought that I had just missed the memo on retirement, till I looked closer and saw the publication date was literally yesterday.

Listen I get that this was a hard decision and that finding maintainers has been challenging.

But 4 months ... does anyone on the SIG actually run k8s for a living ? I really wonder sometimes what the ideal commercial K8s user looks like to CNF developers and how unattached from reality it must be.

Retirement of a service of this magnitude should be at minimal a year. Hell its going to take longer than 4 months to get all the documentation rewritten.

Rant over, I'm off to rewriter my Q1 roadmap and read up on gateway API.

PS: K8s contributors have a problem imo, everyone wants to work on new features, and no one wants to work on maintaince. The constant churn that is the K8s ecosystem makes me question is viability for small and medium companies.


r/kubernetes • • Sep 19 '24

PSA: Kubefirst is now Konstruct

0 Upvotes

Last week we flew our team out to Berlin to celebrate the release of a stealth 12-epic set of major changes that we just dropped:

  • 🧡 rebranded our company from Kubefirst to Konstruct

    • 💜 the Kubefirst product line and brand remains intact

  • 🦋 released the debut of Colony, an instant bare metal cluster and os provisioner

    • 🤯 check out our virtual demo data center to see it in action

  • 🪄 introduced Kubefirst Pro ✨

    • 🤝 the Kubefirst Platform remains free OSS just as it has for the last 5+ years

  • 👥 new account management dashboard

  • 💖 new marketing site

  • 📖 new docs site for Colony

  • 🎨 new logos for Konstruct, Colony, and Kubefirst Pro

  • 🌐 domain migration of our hosted charts

  • ✅ automated release improvements that we're dogfooding internally for eventual OSS

  • 🎬 brand shifts throughout the socials

  • 🎁 github migration of our open source github org: konstructio

  • ☁️ cloud migration of our production and management ecosystem

So proud of our brilliant, passionate, and kind team for making all of it happen so secretly and frictionlessly while supporting our public open source community. Something incredible is building at Konstruct.

If you have any questions about the shifts I'm here for you at reddit or hop in our community slack for the full team support.


r/kubernetes • • Jun 18 '24

The ticking supply chain attack bomb of exposed Kubernetes secrets

1 Upvotes

In this KubeFM episode, Yakir and Assaf from Aqua Security explore how a robust Kubernetes secrets strategy is necessary to prevent leaks and maintain a strong security posture.

You will learn:

  • How Kubernetes secrets are leaked, and what tools can you use to prevent that (Hint: Yakir and Assaf suggested using more than one.)

  • How shadow IT is a more significant threat you might think and why companies should monitor personal Github repositories.

  • What happens when a secret is leaked and how attackers exploit your resources (or further gain access to more).

Watch it here: https://kube.fm/exposed-secrets-yakir-assaf

Listen on:


r/kubernetes • • Aug 30 '22

STOP SETTING CPU LIMITS!

Thumbnail
shonlevran.medium.com
9 Upvotes

r/kubernetes • • Dec 18 '25

New Features We Find Exciting in the Kubernetes 1.35 Release

Thumbnail
metalbear.com
0 Upvotes

Hey everyone! Wrote a blog post highlighting some of the features I think are worth taking a look at in the latest Kubernetes release, including examples to try them out.


r/kubernetes • • Apr 14 '24

The hater’s guide to Kubernetes

Thumbnail
paulbutler.org
0 Upvotes

r/kubernetes • • Apr 25 '26

Controversial opinion; I am not letting go of ingress-nginx

45 Upvotes

Yes you heard it. I don’t care what everyone says.

I love nginx, it’s highly performant, rock solid and extremely flexible. The kind of stuff it can do has saved my ass countless times. Adding headers, removing headers, complicated routing, error handling, encryption, authentication, overriding complete responses, L4 proxying, streaming, caching, load balancing, compression, the list never ends.

I love ingress-nginx even more! It does all that but makes it dead simple. Need compression? One line. Need auth? Two lines and a secret. Need rate limiting? One line. Cache? That’ll be another line. And if it’s something more complicated? Go ahead, dive into the complexity and write your own snippet.

It is, yes “is” not “was”, a truly beautiful piece of software and I am not leaving it till you pry it out of my cold dead hands (or clusters).


r/kubernetes • • Jul 23 '24 Heart of Silver

Finally, a viable Helm Replacement

5 Upvotes

I have a love-hate relationship with Helm. It’s straightforward for simple use cases, but creating Helm charts can be quite complex. Despite its utility, Helm has limitations and well-known issues.

Nelm, a part of the Werf project, is emerging as a promising alternative to Helm. It is a fully backwards compatible reimplementation of Helm, with improvements aimed at making it more robust and feature-rich.

This doesn't address the main issue of helm charts and go templating syntax, but I think it's a move in the right direction.

https://medium.com/@piotrzan/finally-a-viable-helm-replacement-388d538f9e1f


r/kubernetes • • Apr 05 '21

Strange things you never knew about Kubernetes ConfigMaps on day one

1 Upvotes

Deploying on Kubernetes is one complex task, but dealing with surprises during maintenance is another. ConfigMaps and Secrets are often overlooked topics when it comes to Cloud Native Deployments. But they can add unforeseen challenges during application maintenance. Read more : https://blog.gopaddle.io/2021/04/01/strange-things-you-never-knew-about-kubernetes-configmaps-on-day-one/


r/kubernetes • • Dec 23 '25 Heartwarming

Kubernetes is Linux

Thumbnail medium.com
73 Upvotes

Google was running millions of containers at scale long ago

Linux cgroups were like a hidden superpower that almost nobody knew about.

Google had been using cgroups extensively for years to manage its massive infrastructure, long before “containerization” became a buzzword.

Cgroups, an advanced Linux kernel feature from 2007, could isolate processes and control resources.

But almost nobody knew it existed.

Cgroups were brutally complex and required deep Linux expertise to use. Most people, even within the tech world, weren’t aware of cgroups or how to effectively use them.

Then Docker arrived in 2013 and changed everything.

Docker didn’t invent containers or cgroups.

It was already there, hiding within the Linux kernel.

What Docker did was smart. It wrapped and simplified these existing Linux technologies in a simple interface that anyone could use. It abstracted away the complexity of cgroups.

Instead of hours of configuration, developers could now use a single docker run command to deploy containers, making the technology accessible to everyone, not just system-level experts.

Docker democratized container technology, opening up the power of tools previously reserved for companies like Google and putting them in the hands of everyday developers.

Namespaces, cgroups (control Groups), iptables / nftables, seccomp / AppArmor, OverlayFS, and eBPF are not just Linux kernel features.

They form the base required for powerful Kubernetes and Docker features such as container isolation, limiting resource usage, network policies, runtime security, image management, and implementing networking and observability.

Each component relies on Core Linux capabilities, right from containerd and kubelet to pod security and volume mounts.

In Linux, process, network, mount, PID, user, and IPC namespaces isolate resources for containers. Coming to Kubernetes, pods run in isolated environments using namespaces by the means of Linux network namespaces, which Kubernetes manages automatically.

Kubernetes is powerful, but the real work happens down in the Linux engine room.

By understanding how Linux namespaces, cgroups, network filtering, and other features work, you’ll not only grasp Kubernetes faster — you’ll also be able to troubleshoot, secure, and optimize it much more effectively.

By understanding how Linux namespaces, cgroups, network filtering, and other features work, you’ll not only grasp Kubernetes faster, but you’ll also be able to troubleshoot, secure, and optimize it much more effectively.

To understand Docker deeply, you must explore how Linux containers are just processes with isolated views of the system, using kernel features. By practicing these tools directly, you gain foundational knowledge that makes Docker seem like a convenient wrapper over powerful Linux primitives.

Learn Linux first. It’ll make Kubernetes and Docker click.


r/kubernetes • • Oct 14 '21

Try this short tutorial of Portainer and win a t-shirt #devops #kubernetes #kubecon https://portainer.qrd.by/unfck , feel the power unfucking Kubernetes by portainer

Post image
0 Upvotes

r/kubernetes • • Jul 11 '22

Helm Tutorial: A Better Way to Define K8s Objects

0 Upvotes

As the use of Kubernetes expands, we’ve learned that creating objects through yaml configuration isn’t very convenient. Creating objects and other yaml related configuration tasks gets messy when the amount of files grows, meaning that copying them back and forth isn’t a fun or efficient way of working.

By leveraging open source tools like Monokle, you can now preview, navigate, edit, and validate Helm Outputs while gaining visibility and control of the exact resources being deployed to your Kubernetes cluster via Helm charts.

https://kubeshop.io/blog/kubernetes-helm-tutorial-a-better-way-to-define-kubernetes-objects


r/kubernetes • • Jun 07 '20

Kubernetes how it works

0 Upvotes

"start slow start small and it will add up", little intro on Kubernetes, there are 2 articles you may be interested in, what and how Kubernetes works.

https://goglides.io/kubernetes-how-it-works/94/

https://goglides.io/what-is-kubernetes/529/


r/kubernetes • • Aug 22 '20

Then he asked me “Is Kubernetes right for us?”

Thumbnail
medium.com
0 Upvotes

r/kubernetes • • Oct 18 '25

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply

6 Upvotes

If your GitOps stack needs a GitOps stack to manage the GitOps stack… maybe it’s not GitOps anymore.

I wanted a simpler way to do GitOps without adding more moving parts, so I built gitops-lite.
No CRDs, no controllers, no cluster footprint. Just a CLI that links a Git repo to a cluster and keeps it in sync.

kubectl create namespace production --context your-cluster

gitops-lite link https://github.com/user/k8s-manifests \
  --stack production \
  --namespace production \
  --branch main \
  --context your-cluster

gitops-lite plan --stack production --show-diff
gitops-lite apply --stack production --execute
gitops-lite watch --stack production --auto-apply --interval 5

Why

  • No CRDs or controllers

  • Runs locally

  • Uses kubectl server-side apply

  • Works with plain YAML or Kustomize (with Helm support)

  • Explicit context and namespace, no magic

  • Zero overhead in the cluster

GitHub: https://github.com/adrghph/gitops-lite

It’s not trying to replace ArgoCD or Flux.
It’s just GitOps without the ceremony. Simple, explicit, lightweight.


r/kubernetes • • Aug 26 '21

#kubernetes

Post image
0 Upvotes

r/kubernetes • • Mar 03 '25

Help Please! Developing YAML files is hard.

2 Upvotes

To provide a bit of background and set the bar, I'm a software engineer with about 10 years experience of productive output, mostly in C/C++ and Python.

I typically don't have issues developing with technologies that I've been newly exposed to but I seem to really be struggling with K8s and need some help. For additional context, I'm very comfortable with creating multi-container docker compose yaml files and it's typically my goto. It's very frustrating that I can't create a simple multi-container web application in K8s without reading 20 articles and picking pieces of yaml files apart when I can create a docker-compose yaml file without looking at any documentation and the end result be roughly the same.

I've read many how-to's and gone through countless tutorials and something is not clicking when attempting to develop a simple web hosting environment. Too much "here's the yaml file" has me worried that much of the k8s ecosystem stems from copy-pasta examples because creating one is actually complicated. I would've appreciated more of "here's some API documentation" that can illuminate some key-value pair uncertainty. Also, the k8s ecosystem is flooded with reinvented wheels which is worrisome from multiple standpoints but foremost is vanilla k8s is inadequate and batteries are not included. More to the point, you're not doing an `apt install kubernetes` lol. Installation was a painful realization when I was surprised to find that there are more than 5 ways to install a dev environment and choosing the wrong one will be a complete waste of time. I don't know for certain if this is true or not but it's not a good sign when going in with a preconceived notion that you'll be productive. Many clues keeping stacking into a conclusion that I'm going to be in a world of hurt.

After some self-reflection and boiling my pain-points down, I think I have 2 main issues.

  1. API documentation is difficult to read and I don't think I'm comprehending it very well. Understanding what yaml keys are required vs optional is opaque and understanding how the api components fit into the picture of what you want your environment to look like are not explained very well. How do I know whether I need an `Ingress` or an `IngressClass`? ¯_(ツ)_/¯ I feel like the literal content of a typical yaml file is mostly for K8s declaration vs environment declaration which feeds into the previous comment. There doesn't appear to be a documented structure, you're at the whims of the API which also doesn't define the structure very well. `kubectl explain` is mostly useless and IMO shouldn't exist if the API being referenced provided the necessary information needed to explain its existence. I can describe what I want the environment to do, but I feel K8s wants them explained in an overly complicated way which allows me too much opportunity to shoot myself in the foot.

  2. Debugging a K8s environment is very frustrating. When you do finally get an environment that is up and running but is not working properly, figuring out what went wrong is a very tedious process of figuring out which part of the k8s component failed and understanding why it failed, especially with RBAC, and identifying which nested yaml file caused the issue. It doesn't help that reading old articles doesn't help when the APIs and tooling and change so frequently previous fixes aren't applicable anymore. Sometimes I feel like K8s is an operating system in itself but with an unstable API.

There are many more gripes but these are the main 2 issues. This isn't meant to be a rant, just a description for how I feel about working with it to find out if I'm the only one with these thoughts or if there's something obvious I'm missing.

I still feel that it's worth learning since its wide acceptance lends to its value and battle tested durability.
Any help is greatly appreciated.


r/kubernetes • • Nov 13 '20

Why we switched from fluent-bit to Fluentd in 2 hours - PrometheusKube

Thumbnail
prometheuskube.com
3 Upvotes

r/kubernetes • • Oct 02 '24

Moving Past Helm For K8s Deployments. Learnings from working with Kubernetes

Thumbnail
youtu.be
0 Upvotes

r/kubernetes • • Sep 10 '21

Setting and Rightsizing Kubernetes Resource Limits

Thumbnail
containiq.com
0 Upvotes

r/kubernetes • • Feb 23 '24

Where does kubernetes make sense for production

0 Upvotes

I've been messing with k3s in a homelab for awhile and I think the product is awesome, but I'm having trouble seeing the value in enterprise. I was wondering how you use the product?

With on-prem kubernetes it adds a lot of overhead in terms of maintenance and you need to have highly trained staff. It can even add instability if it's poorly configured. K3s updates are a bit of a hassle, and setting up a new node can be very frustrating. I also know these problems magnify when you move up to k8s.

With cloud kubernetes, azure and AWS both offer native products that do much of the same thing.

I'm sure it's extremely useful, I'm just having a hard time seeing it. Where does the complexity actually start to go down? How do you use kubernetes professionally?


r/kubernetes • • Sep 06 '26

I’m designing an on-prem Kubernetes reference architecture — please tear it apart

Thumbnail
github.com
0 Upvotes

I'm a junior engineer working on a project to define a production-oriented reference architecture for on-premises Kubernetes and implement it as reproducible Ansible code.

I'm not trying to build another "install K8s(RKE2) with Ansible" repository.

The idea is to start from the failure domains and operational requirements, define the architecture, and then encode those decisions into Ansible so that unsafe configurations can be detected before deployment.

Some of the assumptions I'm currently designing around:

  • Physical rack topology is part of HA — not just Kubernetes node labels.

  • etcd members are distributed across independent racks/failure domains.

  • Control-plane, etcd, ingress, egress, and worker nodes have separate roles and taints.

  • North-south traffic is handled through dedicated ingress nodes rather than exposing every Kubernetes node.

  • Cilium is used for eBPF networking, BGP, network policy, and Egress Gateway.

  • Traefik is used for operational/internal applications, while Istio is reserved for workloads that actually need traffic management such as canary/blue-green/weighted routing and mTLS.

  • Stateful HA is considered beyond pod distribution — PostgreSQL, Redis, object storage, etc. are treated as separate failure domains.

  • Ansible preflight checks should fail the deployment when the topology itself is unsafe, rather than simply documenting the recommended topology.

  • Failure scenarios such as node/rack failure, BGP convergence, egress gateway failure, and MTU behavior will be measured rather than assumed.

The architecture is currently documented in the README, along with the reasoning and references behind the major design decisions.

This is where I'd really like the Kubernetes community to challenge it.

What am I getting wrong?

In particular, I'd love feedback on:

  1. Are the rack-aware etcd assumptions actually valid for production environments?

  2. Where are the hidden failure domains or SPOFs in this design?

  3. Is the Traefik/Istio separation reasonable, or am I over-engineering it?

  4. Are there problems with the Cilium BGP + Egress Gateway approach that I'm overlooking?

  5. Which parts of this architecture would you change if you had to operate it at scale?

  6. What would make this architecture impractical in a real enterprise environment?

  7. In a large-scale production environment, is this kind of architecture actually likely to be used for failure isolation?

  8. I'm designing this around a multi-cluster architecture. If the environment generates a large volume of metrics, would Thanos be a reasonable choice for long-term storage and cross-cluster observability?

  9. Are there any other measurements or failure tests you would recommend performing before putting this architecture into production? I've documented the current measurement and validation targets in Section 6 of the repository. I'd especially appreciate suggestions based on real-world production experience.

I'm also planning to accept Issues and Pull Requests openly and incorporate useful feedback into the implementation.

The goal is eventually to have something like:

Architecture → Ansible → Preflight → Deploy → Failure Test → Community Review → Improve

rather than simply:

Ansible → kubectl get nodes → Done

I'm intentionally publishing this before considering the architecture "finished."

So please tear it apart. If you disagree with a design decision, I'd much rather have someone point it out now than discover it after deploying it in production.

Repository : [https://github.com/jjsair0412/On-Premise_kubernetes_best_architecture]


r/kubernetes • • Dec 23 '24

The Unidirectionality of Infrastructure as Code creates Asymmetry

0 Upvotes

Unidirectionality, exclusive actuation, and asymmetry are deeply entrenched in how we have used Infrastructure as Code for decades. It’s worth considering whether they are necessary and intrinsic to cloud resource management, or whether alternative approaches are feasible, and what benefits they could deliver. This post by Brian Grant explores this topic:



https://itnext.io/the-unidirectionality-of-infrastructure-as-code-creates-asymmetry-40c9f5eed959?source=friends_link&sk=66d5d9b3c74764b2e676f0754193a59b


r/kubernetes • • Oct 10 '24

3 fundamental security concepts for running Kubernetes in production

2 Upvotes

This article is the final part of a 6-part series on DigitalOcean Kubernetes best practices. It dives into three security concepts that are fundamental and fairly easy to adopt for a production Kubernetes environment -

🔐 Zero trust security

🔐 Least privilege

🔐 Encryption at Rest and Encryption in Transit

Read the blog post to learn more.