github/awesome-kubernetes
1
0
Fork 0
mirror of https://github.com/nubenetes/awesome-kubernetes.git synced 2026-07-12 01:41:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'develop' into master

Browse Source
This commit is contained in:
Inaki Fernandez
2026-07-11 16:26:27 +02:00
parent 7385ab5e18 138bc28e87
commit f611c19ee0
3 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -142,7 +142,7 @@ Additionally, as of May 2026, Nubenetes has reached the **Platinum Operational T
| :--- | :--- |
| **Total Technical Resources (Links)** | **18657+** |
| **Specialized MD Pages** | **162** |
| **Total Commits** | **6596+** |
| **Total Commits** | **6599+** |
| **Primary AI Engine** | **Google Gemini (Agentic)** |
<!-- HEART_STATS_END -->
@@ -180,7 +180,7 @@ The growth of Nubenetes reflects the acceleration of the Cloud Native ecosystem.
| 6 | 2023 | 30 | 123 | Maintenance & Refinement |
| 7 | 2024 | 53 | 218 | Curation Strategy Pivot |
| 8 | 2025 | 5 | 20 | Stability & Research Phase |
| 9 | 2026 | 3037 | 12,542 | **Agentic AI Surge** (May 2026 Inception) |
| 9 | 2026 | 3040 | 12,555 | **Agentic AI Surge** (May 2026 Inception) |
<!-- ANNUAL_GROWTH_END -->
<!-- ANNUAL_CHART_START -->
@@ -196,8 +196,8 @@ xychart-beta
title "Nubenetes Annual Growth Metrics (2018–2026)"
x-axis ["2018", "2019", "2020", "2021", "2022", "2023", "2024", "2025", "2026"]
y-axis "Volume (Commits / Estimated New Refs)" 0 --> 13000
bar [1445, 586, 8449, 2193, 1660, 123, 218, 20, 12542]
bar [350, 142, 2046, 531, 402, 30, 53, 5, 3037]
bar [1445, 586, 8449, 2193, 1660, 123, 218, 20, 12555]
bar [350, 142, 2046, 531, 402, 30, 53, 5, 3040]
```
<!-- ANNUAL_CHART_END -->
@@ -208,7 +208,7 @@ xychart-beta
| 2026-04 | 25 | 103 | Active Curation |
| 2026-05 | 2101 | 8,677 | **Agentic Inception (Gemini Era)** |
| 2026-06 | 849 | 3,506 | Active Curation |
| 2026-07 | 62 | 256 | Active Curation |
| 2026-07 | 65 | 268 | Active Curation |
<!-- MONTHLY_SURGE_END -->
### 2.4. Content Distribution and Semantic Clustering

8
src/v2_optimizer.py
View File

@@ -1773,16 +1773,16 @@ class V2VisionEngine:
_body = _body.replace("### Configuration as Code\n\n", f"### Configuration as Code\n{dsl_injection}\n")
pipeline_code_injection = """
!!! info "Pipeline as Code with Jenkins: Architectural Core Principles"
!!! info "[Pipeline as Code with Jenkins: Architectural Core Principles](https://www.jenkins.io/solutions/pipeline)"
As defined in the official [Jenkins Pipeline Book](https://www.jenkins.io/doc/book/pipeline), Jenkins is fundamentally an automation engine that supports diverse delivery patterns. Modeling your delivery workflow as a **Pipeline** adds a powerful set of automation capabilities:
* **Code**: Pipelines are implemented directly in code (usually a `Jenkinsfile`) and checked into version control, enabling peer code reviews and auditability.
* **Durable**: Pipelines are built to survive both planned and unplanned restarts of the Jenkins controller.
* **Pausable**: Pipelines can pause execution to wait for human approval or input before proceeding to deployment.
* **Versatile**: They naturally support complex real-world CD topologies, including parallel execution, looping, and fork/join patterns.
* **Extensible**: The Pipeline DSL supports custom extensions (e.g., Shared Libraries) and integrations with external plugins.
* **Extensible**: The Pipeline [DSL](https://en.wikipedia.org/wiki/Domain-specific_language) supports custom extensions (e.g., Shared Libraries) and integrations with external plugins.
!!! info "Jenkins Pipeline Best Practices: Declarative, Scripted, and Shared Libraries"
!!! info "[Jenkins Pipeline Best Practices: Declarative, Scripted, and Shared Libraries](https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin)"
Based on CloudBees' strategic guide: [Top 10 Jenkins Pipeline Best Practices](https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin):
* **Prefer Declarative Syntax**: Declarative syntax (introduced in 2017) is the modern standard. Many advanced features—such as matrix builds—are exclusively available in Declarative. Avoid legacy Scripted syntax (2014) unless absolutely necessary.
@@ -1792,7 +1792,7 @@ class V2VisionEngine:
* **Declarative inside Shared Libraries**: **Shared-libraries with scripted pipeline syntax are not recommended** since more custom coding involves more maintenance issues. Use **Declarative Pipeline Syntax** as much as possible inside your libraries.
!!! info "Building Declarative Pipelines with OpenShift: Jenkinsfile as Code and Syntax Structures"
!!! info "[Building Declarative Pipelines with OpenShift: Jenkinsfile as Code and Syntax Structures](https://www.redhat.com/en/blog/building-declarative-pipelines-openshift-dsl-plugin)"
As detailed in Red Hat's engineering guide: [Building Declarative Pipelines with OpenShift DSL Plugin](https://www.redhat.com/en/blog/building-declarative-pipelines-openshift-dsl-plugin):
* **Jenkinsfiles as the De-Facto Standard**: Since Jenkins 2, Jenkinsfiles have quickly become the **de-facto standard for building continuous delivery pipelines**, allowing teams to track, review, audit, and manage the pipeline lifecycle inside source version control just like application code.

8
v2-docs/jenkins.md
View File

@@ -77,16 +77,16 @@ description: "Top Jenkins resources for 2026, AI-ranked: Jenkinsfile Runner, Exa
- **(2020)** [cloudbees.com: Troubleshooting Jenkins Performance: Kubernetes Edition - Part 1 (2020) 🌟](https://www.cloudbees.com/blog/apm-tools-jenkins-performance) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Part one of an engineering diagnostic series for hunting down master slowdowns in Kubernetes clusters. Focuses on setting up proper application performance monitoring and resolving severe disk-level I/O latency blocks.
## CICD Pipeline Architecture
!!! info "Pipeline as Code with Jenkins: Architectural Core Principles"
!!! info "[Pipeline as Code with Jenkins: Architectural Core Principles](https://www.jenkins.io/solutions/pipeline)"
As defined in the official [Jenkins Pipeline Book](https://www.jenkins.io/doc/book/pipeline), Jenkins is fundamentally an automation engine that supports diverse delivery patterns. Modeling your delivery workflow as a **Pipeline** adds a powerful set of automation capabilities:
* **Code**: Pipelines are implemented directly in code (usually a `Jenkinsfile`) and checked into version control, enabling peer code reviews and auditability.
* **Durable**: Pipelines are built to survive both planned and unplanned restarts of the Jenkins controller.
* **Pausable**: Pipelines can pause execution to wait for human approval or input before proceeding to deployment.
* **Versatile**: They naturally support complex real-world CD topologies, including parallel execution, looping, and fork/join patterns.
* **Extensible**: The Pipeline DSL supports custom extensions (e.g., Shared Libraries) and integrations with external plugins.
* **Extensible**: The Pipeline [DSL](https://en.wikipedia.org/wiki/Domain-specific_language) supports custom extensions (e.g., Shared Libraries) and integrations with external plugins.
!!! info "Jenkins Pipeline Best Practices: Declarative, Scripted, and Shared Libraries"
!!! info "[Jenkins Pipeline Best Practices: Declarative, Scripted, and Shared Libraries](https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin)"
Based on CloudBees' strategic guide: [Top 10 Jenkins Pipeline Best Practices](https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin):
* **Prefer Declarative Syntax**: Declarative syntax (introduced in 2017) is the modern standard. Many advanced features—such as matrix builds—are exclusively available in Declarative. Avoid legacy Scripted syntax (2014) unless absolutely necessary.
@@ -96,7 +96,7 @@ description: "Top Jenkins resources for 2026, AI-ranked: Jenkinsfile Runner, Exa
* **Declarative inside Shared Libraries**: **Shared-libraries with scripted pipeline syntax are not recommended** since more custom coding involves more maintenance issues. Use **Declarative Pipeline Syntax** as much as possible inside your libraries.
!!! info "Building Declarative Pipelines with OpenShift: Jenkinsfile as Code and Syntax Structures"
!!! info "[Building Declarative Pipelines with OpenShift: Jenkinsfile as Code and Syntax Structures](https://www.redhat.com/en/blog/building-declarative-pipelines-openshift-dsl-plugin)"
As detailed in Red Hat's engineering guide: [Building Declarative Pipelines with OpenShift DSL Plugin](https://www.redhat.com/en/blog/building-declarative-pipelines-openshift-dsl-plugin):
* **Jenkinsfiles as the De-Facto Standard**: Since Jenkins 2, Jenkinsfiles have quickly become the **de-facto standard for building continuous delivery pipelines**, allowing teams to track, review, audit, and manage the pipeline lifecycle inside source version control just like application code.