Merge branch 'master' into monitoring

.github/workflows/deploy.yaml

@@ -15,6 +15,10 @@ jobs:
         with:
           submodules: "true"
           lfs: true
+
+      - name: Check spelling
+        uses: crate-ci/typos@master
+
       - uses: julia-actions/setup-julia@latest
         with:
           version: 1.9.4

.github/workflows/pullrequest.yaml

@@ -0,0 +1,15 @@
+---
+name: Release drafter
+
+on:
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+

Makefile

@@ -1,5 +1,5 @@
 .DEFAULT_GOAL := build
-RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.18.2")
+RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.18.16")
 
 ifeq ($(CI),true)
 DOCKER_TTY_ARG=

_typos.toml

@@ -0,0 +1,8 @@
+[default.extend-words]
+# Don't correct the surname "Teh"
+CLOS = "CLOS"
+leafs = "leafs"
+nd = "nd"
+
+[files]
+extend-exclude = ["*.svg", "*.drawio", "allocate.yml"]

docs/src/development/contributing.md

@@ -40,7 +40,7 @@ This section contains language-agnostic topics that all metal-stack projects are
 
 The code base is owned by the entire team and every member is allowed to contribute changes to any of the projects. This is considered as collective code ownership[^1].
 
-As a matter of fact, there are persons in a project, which already have experience with the sources. These are defined directly in the repository's [CODEOWNERS](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) file. If you want to merge changes into the master branch, it is advisable to include code owners into the proecess of discussion and merging.
+As a matter of fact, there are persons in a project, which already have experience with the sources. These are defined directly in the repository's [CODEOWNERS](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) file. If you want to merge changes into the master branch, it is advisable to include code owners into the process of discussion and merging.
 
 ### Microservices
 

docs/src/development/proposals/MEP1/README.md

@@ -82,7 +82,7 @@ In order to replicate certain data which must be available across all partitions
   Postgres does not have a multi datacenter with replication in both directions, it just can make the remote instance store the same data.
 - CockroachDB
 
-  Is a Postgresql compatible database enginge on the wire. CockroachDB gives you both, ACID and geo replication with writes allowed from all connected members. It is even possible to configure [Follow the Workload](https://www.cockroachlabs.com/docs/stable/topology-follow-the-workload) and [Geo Partitioning and Replication](https://www.cockroachlabs.com/docs/v19.2/topology-geo-partitioned-replicas).
+  Is a Postgresql compatible database engine on the wire. CockroachDB gives you both, ACID and geo replication with writes allowed from all connected members. It is even possible to configure [Follow the Workload](https://www.cockroachlabs.com/docs/stable/topology-follow-the-workload) and [Geo Partitioning and Replication](https://www.cockroachlabs.com/docs/v19.2/topology-geo-partitioned-replicas).
 
 If we migrate all metal-api entities to be stored the same way we store masterdata, we could use cockroachdb to store all metal entities in one ore more databases spread across all partitions and still ensure consistency and high availability.
 

docs/src/development/proposals/MEP14/README.md

@@ -0,0 +1,25 @@
+# Independence from external sources
+
+In certain situations some customers may need to operate and create machines without making use of external services like DNS or NTP through the internet. To make this possible, all metal-stack components reaching external services need to be configurable with custom endpoints.
+
+So far, the following components have been identified as requiring changes:
+
+- pixiecore
+- metal-hammer
+- metal-images
+
+More components are likely to be added to the list during processing.
+
+## pixiecore
+
+A NTP server endpoint need to be configured on the pixiecore. This can be achieved by providing it through environment variables on start up.
+
+## metal-hammer
+
+If using a self-deployed NTP server, also the metal-hammer need to be configured with it. For backward compatibility, default values from `pool.ntp.org` and `time.google.com` are used.
+
+## metal-images
+
+Configurations for the `metal-images` are different for machines and firewalls.
+
+The implementation of this MEP will make metal-stack possible to create and maintain machines without requiring an internet connection.