JavanXD

substitutions:
  name: esphome-ledaluc2
  friendly_name: ESPHome LEDA LUC2

esphome:
  name: ${name}
  friendly_name: ${friendly_name}
  min_version: 2023.6.0  # Use a stable ESPHome version for compatibility
  name_add_mac_suffix: false  # Prevent adding MAC suffix to the device name
  project:

mbafford

Rough guide to using my ruleswrapper.py class to hard-code certain rules in beancount-import.

See the example config - add the ruleswrapper as the data source, and specify the module to be wrapped as wrapped_module.

Any configuration parameters meant for the wrapped module should be added to the config passed to ruleswrapper.

Code may not compile exactly as-is - roughly edited to remove sensitive data.

TODO:

• split rules into standalone file, so ruleswrapper.py can be shared more easily

janeczku

Using Multus CNI in K3S

By default, K3S will run with flannel as the CNI and use custom directories to store CNI plugin binaries and config files(You can inspect the kubelet args K3S uses via journalctl -u k3s|grep cni-conf-dir). So you need to configure that properly When deploying Multus CNI.

For example given the official Multus manifests in https://github.com/intel/multus-cni/blob/36f2fd64e0965e639a0f1d17ab754f0130951aba/images/multus-daemonset.yml, the following changes are needed:

volumes:
 - name: cni