discordianfish

Run DIAMBRA Engine without CLI

Agents connect via network using gRPC to DIAMBRA Engine running in a Docker container. The diambra CLI's run command starts the DIAMBRA Engine in a Docker container and sets up the environment to make it easy to connect to the Engine. For troubleshooting it might be useful to run the Engine manually, using hostnetworking.

Creating the ~/.diambra and ~/.diambra/credentials is only needed when you never ran the diambra cli before. Otherwise this step can be skipped.

Start Engine

Linux/MacOS:

discordianfish

#!/bin/bash

ECS_CONTEXT_FILE=~/.ecs/context

# Check if the ECS context file exists
if [ -f "$ECS_CONTEXT_FILE" ]; then
    # Read the active cluster from the ECS context file
    ECS_CLUSTER=$(cat "$ECS_CONTEXT_FILE")
fi

discordianfish

#!/bin/bash
set -euo pipefail
BIN=$1
TARGET=$2
mkdir -p "$TARGET"

bundle() {
	lib="$1"
    target="$2"

discordianfish

My k3s server is running on 192.168.1.1 in my LAN. While I can expose the TLS endpoint to the public internet, my IP is dynamic. This doesn't play well with Kubernetes since when kubelet is connecting to the TLS endpoint, it retrieves a list of apiservers and tries to connect to them directly. So instead I add the apiserver's private IP to the loopback interface and run an ssh tunnel to forward it.

So with the unit file above, you can join a node with:

curl -sfL https://get.k3s.io | K3S_URL=https://192.168.1.1:6443 K3S_TOKEN=mynodetoken sh -

discordianfish

#!/bin/bash
set -euo pipefail

declare -A paths
declare -A ids

for f in /dev/disk/by-path/*; do
	[[ "$f" == *"-part"* ]] && continue
	paths[$(readlink -f "$f")]+="$(basename "$f") "
done

discordianfish

daemon            off;

events {}

error_log /dev/stdout info;

http {
    include /usr/local/etc/nginx/mime.types;
    access_log /dev/stdout;
    server {

discordianfish

Guten Tag,

vor einiger Zeit haben Sie auf unserer Petitionsplattform WeAct einen Appell
unterzeichnet. Nach dem Unterzeichnen wollten Sie allerdings nicht weiter über
WeAct oder einzelne Petitionen informiert werden. Es tut uns leid, dass wir Sie
heute dennoch anschreiben müssen.

Leider ist es nämlich auf WeAct zu einem Daten-Problem gekommen, von dem auch
Sie betroffen sind. Wir sind daher nach den Vorgaben der
Datenschutzgrundverordnung dazu verpflichtet, Ihnen diese Mail zu senden.

discordianfish

#!/bin/bash
set -euo pipefail

TMP=$(mktemp -d)
trap "rm -r '$TMP'" EXIT

cd "$TMP"
NAMESPACE=custom-metrics
NAME=custom-metrics-apiserver.$NAMESPACE

discordianfish

{
  "data": {
    "type": "match",
    "id": "64cd06de-00a2-4a20-8537-45ff72fa45c0",
    "attributes": {
      "createdAt": "2018-04-03T22:50:59Z",
      "duration": 1948,
      "gameMode": "duo-fpp",
      "patchVersion": "",
      "shardId": "pc-eu",

discordianfish

Convert deployment manifest env to secret ref

cat deployment.yaml | yaml2json \
  | jq '.spec.template.spec.containers[0].env|map(.key = .name)|map(.valueFrom = { "secretKeyRef": { "name": "secret-name", "key": .key|ascii_downcase }}|del(.value))' \
  | json2yaml

Convert deployment manifest env to secret data mapping:

cat deployment.yaml | yaml2json \