jspaleta

# First let's follow the hello world flatpak tutorial
# https://docs.flatpak.org/en/latest/first-build.html


# Create flatpak-test-repo  in location you can write to:
$ export REPO_BASE=${HOME}/scratch/
$ mkdir -p ${REPO_BASE}/flatpak-test-repo


# create a directory to hold test flatpak applications

jspaleta

[jspaleta@msi ~]$ cat kind-cluster.yaml 
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  image: kindest/node:v1.27.3@sha256:3966ac761ae0136263ffdb6cfd4db23ef8a83cba8a463690e98317add2c9ba72
- role: worker
  image: kindest/node:v1.27.3@sha256:3966ac761ae0136263ffdb6cfd4db23ef8a83cba8a463690e98317add2c9ba72
- role: worker
  image: kindest/node:v1.27.3@sha256:3966ac761ae0136263ffdb6cfd4db23ef8a83cba8a463690e98317add2c9ba72

jspaleta

Kind node container customizations

First drop into the kind-worker container

podman exec -ti kind-worker /bin/bash

install the wireguard-tools package without any of the additional recommended packages

root@kind-worker# apt-get install --no-install-recommends wireguard-tools 

jspaleta

Testing egress policy using dummy service

Assumes you have private network dummy service setup on workstation, and have confirmed that worker-node/workstation wg tunnel is working

Prepare k3s node with custom labels for egress gateway use

kubectl get nodes 
NAME STATUS ROLES AGE VERSION

jspaleta

---
apiVersion: v1
kind: Namespace
metadata:
  name: cilium-observability
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: prometheus-k8s

jspaleta

type: CheckConfig
api_version: core/v2
metadata:
  name: nginx-http-service-healthcheck
  annotations:
    # Required key: io.sensu.ansible.config.actions  
    #   Value: stringified json array of Job Template Requests
    #          all request attributes are optional
    # Each Job Template Request may consist of:
    #    Either template_name and/or template_id, with template_id taking precedence

jspaleta

# Example of Basic Sensu Go Load Balancer


# Load balancer for backend api
# Default port is 8080
upstream sensu_api {
    # Clients with the same IP are redirected to the same backend
    ip_hash;

    # Available backend servers

jspaleta

{
  "__inputs": [
    {
      "name": "DS_INFLUXDB",
      "label": "InfluxDB",
      "description": "",
      "type": "datasource",
      "pluginId": "influxdb",
      "pluginName": "InfluxDB"
    }

jspaleta

# Extend the sensu-agent service init to call the update_name.sh  script
# place this file in: /etc/systemd/system/sensu-agent.service.d


# With systemd you don't have to edit the vendor provided service init script.
# local admins can extend/override vendor settings by using correctly named extension directory structures
# Ex: /etc/systemd/system/sensu-agent.service.d/
# This .d directory will be parsed for systemd directives to extend/override the vendor supplied sensu-agent.service

# For now all we want to do is add an ExecStartPre directive, 

jspaleta

#!/bin/sh
#
#  check_status_as_metric.sh
#  optionally set measurement, field
#  Ex:
#   check_status_as_metric.sh measurement="${entity_name}" field="${check_name}.status"
#


event=$(cat /dev/stdin)