IronCore Project

Appearance

Project Design Principles ​

Declarative Kubernetes APIs ​

All functionality must be exposed via declarative Kubernetes APIs. Use Custom Resource Definitions (CRDs) or the API aggregation layer where appropriate. Services should model their state using Kubernetes resources.

Minimal API Surface ​

When introducing new features, expose only the essential fields. Avoid over-designing or leaking internal implementation details into the API.

Separation of Concerns ​

Clearly separate different problem domains. Do not mix unrelated concerns in a single API or component. Define strict API contracts between boundaries.

Kubernetes API Conventions ​

Follow official Kubernetes API conventions when designing or extending APIs. See the Kubernetes API Conventions Guide for details.

No Scripting for Deployment ​

Avoid Bash, Python, or other scripting languages for deployment tasks. All components must be declaratively deployable using Kubernetes manifests or tools like Helm or Kustomize.

EU and German government funding logos

Funded by the European Union – NextGenerationEU.

The views and opinions expressed are solely those of the author(s) and do not necessarily reflect the views of the European Union or the European Commission. Neither the European Union nor the European Commission can be held responsible for them.

Copyright © Linux Foundation Europe.

IronCore is a project of Linux Foundation Europe. For applicable policies including privacy policy, terms of use and trademark usage guidelines, please see https://linuxfoundation.eu. Linux is a registered trademark of Linus Torvalds.