v0.5.6

v0.5.6 (2023-04-11)

Fixes

• use old status for headless client (8c437dd)

v0.5.5

v0.5.5 (2023-04-11)

Breaking Changes

• Antistasi will no longer be installed on startup as a mission, since v3.x.x now is a full mod. This has been added to the mod-preset and will be installed automatically.
• antistasi mod-preset was updated with new mods. It is recommended to use your own if you don't want to use the list of provided mods.

Features

• remove Antistasi v2.x.x installation as v3.x.x has been converted to a full mod (82a2d49)
• cup terrains (3e8e2d9)
• use antistasi 3.0 mod (8968fc4)

Fixes

• use correct status for headless client (8cc8cc2)
• invalid yaml (2c56bde)
  v0.5.4 (2022-11-12)

v0.5.4

Fixes

• mapping key ARMA_LIMITFPS already defined at line 17
  (a762d0f)

v0.5.3

Features

• added podAntiAffinity
  (76b2e10)
• added experimental grafana dashboards
  (fca9152)(7989caa)
• lower max FPS to 60 to save power
  (b768b17)
• detection of server readiness
  (aad67f6)

Fixes

• unicodeDecodeError
  (b970e0b)

v0.5.2

Features

• add default-container
  (f29590d)
• added tunnel for headless clients and makefile
  (3450b16)
• added serviceMonitor
  (54be643)

Docs, CI and Developer Experience

• docs: updated development docs
  (f29590d)
• ci: update test values
  (f29590d)

v0.4.0 - Security first

The ARMA containers are now running:

• as a non-privileged user
• without capabilities
• with a read-only root filesystem

This is a breaking change to the previous release.

The rsync containers are still running as root, this will be adressed in following releases.

v0.2.0 Initial Release

Initial release for the ARMA3 Helm Chart.

The following features are working in a bare-metal environment:

• using metallb to expose the servers on a dedicated IP address
• installing Antistasi Missions on server startup (v2.5.5)
• an arbitary number of Headless Clients (actual supported number depends on the mission you are loading)
• one of the following storage setups
  • Server (ReadWriteOnce) and Headless Clients (ReadWriteMany) with rsync to synchronize changes from the server to the headless clients
  • Server (ReadWriteMany) and Headless Clients sharing the save RWX volume without rsync

The release has been tested using:

• Rancher v2.6.8
• Docker 20.10
• Helm 3
• FluxCD v0.30
• Longhorn v1.3.1

In a bare-metal home lab environment with:

• three master nods
• two worker nodes (AMD Ryzen 5/7 processors, 32GB of memory each, 1TB SSD storage)
• 1GBit/s network throughput