- Go 96.3%
- Makefile 2.2%
- Shell 0.8%
- Smarty 0.4%
- Dockerfile 0.3%
a9a3b328ecSigned-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Andreas Fritzler <andreas.fritzler@sap.com> |
||
|---|---|---|
| .github | ||
| api/core/v1alpha1 | ||
| apimachinery | ||
| apinetlet | ||
| client-go | ||
| cmd | ||
| config | ||
| docs | ||
| gen | ||
| hack | ||
| internal | ||
| LICENSES | ||
| metalnetlet | ||
| models-schema | ||
| networkid | ||
| utils | ||
| .gitignore | ||
| .golangci.yaml | ||
| CODEOWNERS | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| README.md | ||
| REUSE.toml | ||
ironcore-net
Overview
ironcore-net provides networking functions across multiple
peers.
ironcore-net conceptually consists of a control-plane and
Nodes. The API of ironcore-net is realized by an aggregated API
server. The controller-manager reconciles state of these objects.
The scheduler (currently built into the controller-manager)
assigns functions to Nodes.
A Node is currently implemented via metalnetlet, an agent
using a metalnet cluster run the payload functions on. A
metalnetlet creates Node objects corresponding to all
Nodes inside the metalnet custer.
The integration to ironcore is realized via the apinetlet,
an agent using an ironcore-net cluster to realize ironcore
objects like LoadBalancers, VirtualIPs and more.
Documentation about the concepts of ironcore-net can be found
in the concepts directory.
Contributing
We'd love to get feedback from you. Please report bugs, suggestions or post questions by opening a GitHub issue.