https://github.com/ironcore-dev/ironcore-in-a-box
IronCore IaaS in a Box
https://github.com/ironcore-dev/ironcore-in-a-box
iaas kind kubernetes
Last synced: 2 months ago
JSON representation
IronCore IaaS in a Box
- Host: GitHub
- URL: https://github.com/ironcore-dev/ironcore-in-a-box
- Owner: ironcore-dev
- License: apache-2.0
- Created: 2025-02-07T13:25:59.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2025-06-26T11:53:21.000Z (3 months ago)
- Last Synced: 2025-07-09T14:09:06.567Z (3 months ago)
- Topics: iaas, kind, kubernetes
- Language: Makefile
- Homepage:
- Size: 1.25 MB
- Stars: 8
- Watchers: 9
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ironcore-in-a-box
[](https://api.reuse.software/info/github.com/ironcore-dev/ironcore-in-a-box)
[](LICENSE)
[](https://makeapullrequest.com)
## Overview
**IronCore in a Box** is a project that brings up the IronCore stack inside a local [kind](https://kind.sigs.k8s.io/) cluster. It provides a local demo environment to illustrate the capabilities of IronCore.
This project supports **Linux**, **macOS**, and **Windows (via WSL2)** environments.
## Prerequisites
Ensure you have the following installed before running the project:
* [curl](https://curl.se/)
* [make](https://www.gnu.org/software/make/)
* [go](https://go.dev/)
* [docker](https://www.docker.com/) (recommended) or [podman](https://podman.io/) (refer to [podman user guidance](docs/podman.md))
### Linux Kernel Requirements
IronCore relies on specific Linux kernel features. Ensure your kernel has the following configurations enabled, at least as modules (=m):
* CONFIG_LWTUNNEL
* CONFIG_LWTUNNEL_BPF
* CONFIG_IPV6_TUNNEL
Most modern Linux distributions have these enabled by default. However, minimal installations or older versions might require a custom kernel build or module loading.
### Windows/WSL2 Requirements
**Important for Windows/WSL2 Users**
The default WSL2 kernel often lacks the Linux options. You will likely need to compile a custom kernel. Please ensure you have followed the [WSL2 Custom Kernel Guide](docs/windows_wsl2_kernel.md) *before* proceeding with the installation if the required kernel modules are missing.
### MacOS Requirements
When using docker, you cannot directly connect to container IPs attached to the docker network bridge. [docker-mac-net-connect](https://github.com/chipmk/docker-mac-net-connect) is a lightweight service daemon based on Wireguard which automatically maintains the appropriate routing tables on your macOS. This tool is able to make it possible to use the VIP to access provisioned VM directly from Mac's shell, without entering the docker virtual machine.
You can install and make it running each time when Mac is booted by using following commands. If you would like to start/stop this tool manually each time, simply run `sudo docker-mac-net-connect` after installation.
```bash
# Install via Homebrew
$ brew install chipmk/tap/docker-mac-net-connect
# Run the service and register it to launch at boot
$ sudo brew services start chipmk/tap/docker-mac-net-connect
```
## Installation
To set up and start the IronCore stack, run the following command from the root of this repository:
```sh
make up
```
This command will:
1. Create a local kind cluster (if it doesn't exist).
2. Deploy the IronCore stack components into the cluster.
## Examples
You can find examples of how to use the IronCore API in the [Examples](examples/) directory. You can spin up a VM in a [VPC / Overlay Network](https://en.wikipedia.org/wiki/Virtual_private_cloud) with a virtual IP. Using the command `kubectl get machine,network,nic,virtualip` to find out status and more information regarding the provisioned VM. By default, VMs enable password login for easy accessing and testing. The default username and password are `ironcore` and `best123`. Customized ignition can be also generated and used for other purposes.
Your local "datacenter" is at your fingertips to test. Ironcore API documentation can be found [here](https://ironcore-dev.github.io/ironcore/api-reference/overview/) which shows the whole capabilities of IronCore.
## Cleanup
To remove the kind cluster and all deployed resources, run:
```sh
make down
```
This will effectively stop and delete the entire local IronCore environment created by this project.
## License
[Apache-2.0](LICENSE)