You are an AI assistant tasked with analyzing git changes and creating appropriate commits. Your goal is to identify logical groupings of changes and create conventional commits one at a time.
First, analyze the current state:
git status
# THIS LINUX SETUP SCRIPT HAS MORPHED INTO A WHOLE PROJECT: HTTPS://OMAKUB.ORG | |
# PLEASE CHECKOUT THAT PROJECT INSTEAD OF THIS OUTDATED SETUP SCRIPT. | |
# | |
# | |
# Libraries and infrastructure | |
sudo apt update -y | |
sudo apt install -y \ | |
docker.io docker-buildx \ | |
build-essential pkg-config autoconf bison rustc cargo clang \ |
i wanted to update swarm images whenever there is a new image available (even at the risk of breaking something)
it seems watchtower can't do this for swarm stacks/services - only one off containers.
I found this great container from https://github.com/djmaze/shepherd
Must be placed on a manager node.
This (and related gists) captures how i created my docker swarm architecture. This is intended mostly for my own notes incase i need to re-creeate anything later! As such expect some typos and possibly even an error...
Each major task has its own gist, this is to help with maitainability long term.
--- | |
version: "3.8" | |
services: | |
seed: | |
image: consul:latest | |
environment: | |
- "CONSUL_LOCAL_CONFIG={\"disable_update_check\": true}" | |
- "CONSUL_BIND_INTERFACE=eth0" | |
entrypoint: |
lang en_US | |
keyboard us | |
timezone Europe/Helsinki --isUtc | |
reboot | |
text | |
cdrom | |
bootloader --location=mbr --append="rhgb quiet crashkernel=auto" | |
zerombr | |
clearpart --all --initlabel | |
autopart |
WSL2 uses Hyper-V for networking. The WSL2 network settings are ephemeral and configured on demand when any WSL2 instance is first started in a Windows session. The configuration is reset on each Windows restart and the IP addresses change each time. The Windows host creates a hidden switch named "WSL" and a network adapter named "WSL" (appears as "vEthernet (WSL)" in the "Network Connections" panel). The Ubuntu instance creates a corresponding network interface named "eth0".
Assigning static IP addresses to the network interfaces on the Windows host or the WSL2 Ubuntu instance enables support for the following scenarios:
Sometime you need scrape prometheus metrics from external envoy that deploy not to kubernetes environment
You can use iptable or other stuff on external server to allow only trusted IP for scraping metrics - but for dynamic infrastructure some time it's hard to support it.
Envoy can expose this metrics more elegant style - using basic auth
Simple envoy.yaml
#!/bin/bash | |
PACKAGE=$(basename "$0") | |
# .----. _ .-. _ _ | |
# `--. ::_;: :.-. :_;:_; | |
# ,','.-.: `'.' .--. .-..-. | |
# .'.'_ : :: . `.' '_.': :: : | |
# :____;:_;:_;:_;`.__.': ::_; | |
# .-. : |