mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-08-18 20:07:06 +00:00
Nubenetes Bot
4f5d93f271
- Added Anthropic 'Claude Code in Action' course to AI Agents and MCP sections. - Integrated '6 Levels of Claude Code' video to the V2 Video Hub. - Updated centralized inventory.yaml and regenerated V2 Elite Portal. - Deduplicated Claude Code references in V1 archive.
6.3 KiB
6.3 KiB
About Nubenetes
!!! info "Architectural Context" Detailed reference for About Nubenetes in the context of Architectural Foundations.
Standard Reference
- docs.ansible.com: kubernetes.core.k8s – Manage Kubernetes (K8s) objects [COMMUNITY-TOOL]
- cloudscaling.com: The History of Pets vs Cattle and How to Use the Analogy Properly [COMMUNITY-TOOL] — - In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, it’s all hands on deck. The CEO can’t get his email and it’s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, it’s taken out back, shot, and replaced on the line.
- ==Pets==: Servers or server pairs that are treated as indispensable or unique systems that can never be down. Typically they are manually built, managed, and “hand fed”. Examples include mainframes, solitary servers, HA loadbalancers/firewalls (active/active or active/passive), database systems designed as master/slave (active/passive), and so on.
- ==Cattle==: Arrays of more than two servers, that are built using automated tools, and are designed for failure, where no one, two, or even three servers are irreplaceable. Typically, during failure events no human intervention is required as the array exhibits attributes of “routing around failures” by restarting failed servers or replicating data through strategies like triple replication or erasure coding. Examples include web server arrays, multi-master datastores such as Cassandra clusters, multiple racks of gear put together in clusters, and just about anything that is load-balanced and multi-master.
- nextplatform.com: KUBERNETES EXPANDS FROM CONTAINERS TO INFRASTRUCTURE MANAGEMENT 🌟 [COMMUNITY-TOOL]
- Terraform Kubernetes Boilerplates 🌟 [COMMUNITY-TOOL]
- getpostman.com [COMMUNITY-TOOL]
- jinja 🌟 ⭐ 11634 [ENTERPRISE-STABLE]
- opensource.com: Using Ansible with REST APIs [COMMUNITY-TOOL]
- DZone: Defining Day-2 Operations [COMMUNITY-TOOL]
- opensource.com: GitOps vs. DevOps: What's the difference? 🌟 [COMMUNITY-TOOL]
- thenewstack.io: Kubernetes at Scale without GitOps Is a Bad Idea [COMMUNITY-TOOL]
- Jenkins Configuration as Code Plugin [COMMUNITY-TOOL]
- Jenkins CLI [COMMUNITY-TOOL]
- kube.careers: Kubernetes jobs market trends for 2021 (Q4) [COMMUNITY-TOOL]
- fairwinds.com: Never Should You Ever In Kubernetes: #1 Do K8S The Hard Way [COMMUNITY-TOOL]
- alexander-goida.medium.com: Thoughts about breaking silos of software engineering' teams 🌟 [COMMUNITY-TOOL]
- devdriven.by: Promotion Driven Development [COMMUNITY-TOOL]
- reddit.com: Promotion Driven Development [COMMUNITY-TOOL]
- en.wikipedia.org: Kiss up kick down [COMMUNITY-TOOL]
- https://swagger.io/ [COMMUNITY-TOOL]
Cloud Native
Kubernetes Development
Go Client-Go
Generics
- itnext.io: Generically working with Kubernetes objects in Go [ADVANCED LEVEL] [COMMUNITY-TOOL] — Curator Insight highlights the use of Go 1.18+ generics to drastically reduce boilerplate when interacting with various Kubernetes API types. Live Grounding confirms that while standard client-go uses dynamic clients or interface{} for generic operations, integrating Go generics allows for cleaner, type-safe custom controllers. This article provides practical patterns for wrapping standard clients to streamline resource manipulation.
Operations and Reliability
Site Reliability Engineering
Evolution
- thenewstack.io: How the SRE Experience Is Changing with Cloud Native 🌟 [ENTERPRISE-STABLE] — This high-density industry analysis examines how the rise of complex cloud-native architectures shifts SRE responsibilities. It addresses how microservices, service meshes, and dynamic scheduling require SREs to move from simple system monitoring to deep, code-level observability and platform design.
💡 Explore Related: Cheatsheets | Kubernetes | Demos