# About Nubenetes !!! info "Architectural Context" Detailed reference for About Nubenetes in the context of Architectural Foundations. ## Table of Contents 1. [Automation and Orchestration](#automation-and-orchestration) - [Templating Engine](#templating-engine) - [Jinja](#jinja) 1. [Cloud Native](#cloud-native) - [Kubernetes Development](#kubernetes-development) - [Go Client-Go](#go-client-go) - [Generics](#generics) 1. [Infrastructure as Code](#infrastructure-as-code) - [Kubernetes](#kubernetes) - [Terraform Boilerplates](#terraform-boilerplates) 1. [Kubernetes Tools](#kubernetes-tools) - [General Reference](#general-reference) ## The Nubenetes Engineering Manifest !!! quote "The Positive Sum Game" ==*"Open Source is most successful when is played as a positive sum game" (Sarah Novotny)*==
### πŸ›οΈ 1. The Genesis: Munich 2018 Nubenetes was forged in the internals of a massive Cloud Native transformation for a **major multinational car manufacturer** in Munich. Coordinating hundreds of microservices, thousands of developers, and millions of end-users taught us a fundamental truth: **Standardization, Automation, and GitOps are not "best practices"β€”they are survival requirements.** ### 🧠 2. Our Engineering Philosophy We reject technical obfuscation as a competitive advantage. Solutions that are "the hard way" by design do not scale and create fragile, person-dependent silos. !!! abstract "2.1. Correctness by Design" We believe in doing DevOps correctly through the **GitOps pattern**. Automation without correctness is just faster failure. This architectural rigor ensures enterprise-grade stability at scale. !!! abstract "2.2. The Scientific Method" We build bridges based on **evidence**, not politics or hype. If a solution cannot be empirically verified and automated, it is a liability. Engineers rely on evidence to solve problems. #### 2.3. Anti-Bikeshining: Abstractions over Reinvention We prioritize established frameworks and enterprise standards over ad-hoc, unmaintainable tooling. Reinventing the wheel is often a symptom of misaligned incentives in the IT sector. #### 2.4. Avoiding Engineering Anti-Patterns We combat the culture of **Promotion-Based Development (PBD)**, where complexity is manufactured for personal career visibility rather than business value. - [Promotion-Based Development: A Fast Track to Mediocrity](https://vadimkravcenko.com/shorts/promotion-based-development/) [GUIDE] β€” Dissects how rewarding "shiny new things" over battle-tested stability leads to fragile architectures. - [Reddit: The Reality of Promotion-Driven Development](https://www.reddit.com/r/ExperiencedDevs/comments/pw6vuv/promotion_driven_development) [COMMUNITY-TOOL] β€” A raw, evidence-based discussion from senior engineers on the industry's most common misaligned incentives. ### πŸ—οΈ 3. The Architectural North Star We advocate for decoupled, maintainable architectures that survive the test of time and organizational growth. - [Domain-Driven Design (DDD) for Microservices](https://learn.microsoft.com/en-us/azure/architecture/microservices/model/domain-analysis) [DE FACTO STANDARD] β€” The foundational blueprint for defining service boundaries based on business domains rather than technical layers. - [Hexagonal Architecture (Ports and Adapters)](https://medium.com/@sandeepsharmaster/modernize-your-cloud-microservices-apps-hexagonal-architecture-769696494c0) [GUIDE] β€” Decoupling the application core from external infrastructure (Databases, APIs, UI) to ensure high testability and vendor neutrality. ### πŸ“Š 4. Comparative Maturity Framework | Principle | Strategic Focus | Primary Toolset | Architectural Impact | | :--- | :--- | :--- | :--- | | **DevOps** | Automation & Frequency | CI/CD Pipelines | Operational Speed | | **GitOps** | ==Correctness & Drift Control== | Git + Kubernetes | ==Enterprise Stability== | | **SRE** | Reliability & Prevention | Observability | Scalable Quality | ### πŸ›‘οΈ 5. Strategic Standards & Cultural Shifts Engineering excellence is as much about **culture** as it is about code. These foundational resources define the strategic landscape of modern Cloud Native organizations: - [The Agile Manifesto](https://agilemanifesto.org) [DE FACTO STANDARD] β€” The primary root of modern iterative development and the shift away from monolithic planning. - [Google: SRE vs. DevOps β€” Competing Standards or Close Friends?](https://cloud.google.com/blog/products/gcp/sre-vs-devops-competing-standards-or-close-friends) [DE FACTO STANDARD] β€” An essential blueprint for understanding the symbiotic relationship between reliability engineering and delivery speed. - [The 4 Levels of GitOps Maturity](https://cloudnativenow.com/features/the-4-levels-of-gitops-maturity) [GUIDE] β€” A roadmap for evolving from manual deployments to a fully automated, self-healing state. - [Necessary Culture Change with GitOps](https://itnext.io/necessary-culture-change-with-gitops-2c63f4fe9604) [CASE STUDY] β€” Dissects the organizational friction and the necessary mindset shift required to adopt declarative infrastructure. ### πŸ“ˆ 6. Scaling with Evidence: DORA & Value Streams We advocate for data-driven engineering management to avoid the trap of "gut-feeling" decision making. - [Driving DevOps with Value Stream Management](https://www.infoq.com/articles/DevOps-value-stream) [DE FACTO STANDARD] β€” Dissects how to align microservice delivery with business outcomes through flow metrics. - [Better Metrics for Building High Performance Teams](https://www.infoq.com/articles/better-metrics-team-performance) [EMERGING] β€” Beyond LOC and commits: using DORA metrics to cultivate a culture of systemic stability. ### 🧩 7. Technical Leadership & The 'Glue' Factor True seniority is measured by the ability to hold teams together through communication and shared context. - [Being Glue](https://noidea.dog/glue) [DE FACTO STANDARD] β€” An industry-standard analysis of the essential, non-coding technical tasks that ensure project success. - [How Big Tech Runs Tech Projects](https://blog.pragmaticengineer.com/project-management-at-big-tech) [DE FACTO STANDARD] β€” A seminal critique of ceremonial Scrum versus result-oriented engineering pragmatism. - [Martin Fowler: Retrospectives Antipatterns](https://martinfowler.com/articles/retrospective-antipatterns.html) [DE FACTO STANDARD] β€” Essential guide for transforming team feedback loops from blame games into architectural improvement cycles. ### βš–οΈ 8. Meritocracy & Careers in 2026 We advocate for a technical sector where quality and evidence-based decisions take precedence over corporate politics. - [HBR: Stop Hiring for Culture Fit](https://hbr.org/2019/11/stop-hiring-for-culture-fit) [EMERGING] β€” A critical perspective on how "culture fit" often hides bias and hinders technical innovation. - [Defining Day-2 Operations](https://dzone.com/articles/defining-day-2-operations) [GUIDE] β€” Shifts the focus from the excitement of the first deployment to the long-term reality of maintaining production stability. ### πŸš€ 9. The 2026 Vision: Agentic Intelligence Nubenetes has evolved from a historical manual archive into an **Agentic Knowledge Graph**. #### 9.1. V1 Archive (Exhaustive) Preserves historical context, the original curator's voice, and every technically valid link discovered since 2018. It serves as the foundational truth for the entire ecosystem. #### 9.2. V2 Elite Portal (Distilled) An O'Reilly-style technical library where 18k+ resources are filtered, ranked by impact, and enriched with AI-driven architectural summaries for high-speed reference. > *"I am a big fan of the scientific method. Engineers do not build bridges from a right or left perspective... hello! I have a problem, can you help me? Engineers rely on evidence."* β€” **Mark Stevenson** --- ## Automation and Orchestration ### Templating Engine #### Jinja ??? note "jinja 🌟" **[Access Resource](https://github.com/pallets/jinja)** 🌟🌟🌟🌟🌟 | Level: Advanced The official repository for Jinja, the ubiquitous Python-based templating engine. Jinja underpins all dynamic evaluation structures inside Ansible, enabling programmatic infrastructure assembly. ## Cloud Native ### Kubernetes Development #### Go Client-Go ##### Generics - [itnext.io: Generically working with Kubernetes objects in Go](https://itnext.io/generically-working-with-kubernetes-resources-in-go-53bce678f887) [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. ## Infrastructure as Code ### Kubernetes #### Terraform Boilerplates - **(2024)** [Terraform Kubernetes Boilerplates 🌟](https://nubenetes.com/terraform/) [HCL CONTENT] [ADVANCED LEVEL] [COMMUNITY-TOOL] β€” A library of enterprise-stable Terraform templates configured specifically for modern Kubernetes environments (EKS, GKE, AKS). Includes pre-tested infrastructure specifications for VPC topologies, private nodes, and dynamic ingress setups. ## Kubernetes Tools ### General Reference - [DZone: Defining Day-2 Operations](https://dzone.com/articles/defining-day-2-operations) [COMMUNITY-TOOL] β€” A curated technical resource and architectural guide covering ==DZone: Defining Day-2 Operations== in the Kubernetes Tools ecosystem. - [alexander-goida.medium.com: Thoughts about breaking silos of software engineering' teams 🌟](https://alexander-goida.medium.com/thoughts-about-breaking-silos-of-software-engineering-teams-323d1f78ef68) [COMMUNITY-TOOL] β€” A curated technical resource and architectural guide covering alexander-goida.medium.com: Thoughts about breaking silos of software engineering' teams 🌟 in the Kubernetes Tools ecosystem. - [reddit.com: Promotion Driven Development](https://www.reddit.com/r/ExperiencedDevs/comments/pw6vuv/promotion_driven_development) [COMMUNITY-TOOL] β€” A curated technical resource and architectural guide covering reddit.com: Promotion Driven Development in the Kubernetes Tools ecosystem. - [en.wikipedia.org: Kiss up kick down](https://en.wikipedia.org/wiki/Kiss_up_kick_down) [COMMUNITY-TOOL] β€” A curated technical resource and architectural guide covering en.wikipedia.org: Kiss up kick down in the Kubernetes Tools ecosystem. --- πŸ’‘ **Explore Related:** [Demos](./demos.md) | [Kubernetes](./kubernetes.md) | [Cheatsheets](./cheatsheets.md)