Tags

coreoskuberneteskubespraynucudoometallbnginxcert-manageropenwrthaproxyoauth2-proxyhelmelasticsearchELK32biti586pulumipythonhelmsmansopshelm-secretshelm-whatupflatcarhypriotosk3s

coreos

kubernetes

kubespray

nuc

udoo

metallb

nginx

cert-manager

openwrt

haproxy

oauth2-proxy

helm

elasticsearch

  • 26 Dec 2019 elasticsearchelasticsearchELK32biti586

    Running ElasticSearch on 32-bit Linux machine

    I have an old piece of hardware with Atom D2700 CPU, which according to ARK is capable of running x64 OS. Vendor, however, never released a BIOS with x64 support, and I was unable to find it on an Internet.

    Aside this sad fact, that small PC have decent specs, including 4 gigs of RAM, which makes it a good candidate for a single-node ElasticSearch cluster. I have to collect logs from my Kubernetes cluster somewhere, right?

    Unfortunately, Elastic dropped an official i586 support long time ago, which totally makes sense from commercial perspective.

    Well, thanks to Debian and Java we still can run ElasticSearch on top of 32-bit Linux!

    This tutorial is written for ElasticSearch OSS v7.5.1, and might not work for newer versions, as source code might change!

ELK

  • 26 Dec 2019 elasticsearchelasticsearchELK32biti586

    Running ElasticSearch on 32-bit Linux machine

    I have an old piece of hardware with Atom D2700 CPU, which according to ARK is capable of running x64 OS. Vendor, however, never released a BIOS with x64 support, and I was unable to find it on an Internet.

    Aside this sad fact, that small PC have decent specs, including 4 gigs of RAM, which makes it a good candidate for a single-node ElasticSearch cluster. I have to collect logs from my Kubernetes cluster somewhere, right?

    Unfortunately, Elastic dropped an official i586 support long time ago, which totally makes sense from commercial perspective.

    Well, thanks to Debian and Java we still can run ElasticSearch on top of 32-bit Linux!

    This tutorial is written for ElasticSearch OSS v7.5.1, and might not work for newer versions, as source code might change!

32bit

  • 26 Dec 2019 elasticsearchelasticsearchELK32biti586

    Running ElasticSearch on 32-bit Linux machine

    I have an old piece of hardware with Atom D2700 CPU, which according to ARK is capable of running x64 OS. Vendor, however, never released a BIOS with x64 support, and I was unable to find it on an Internet.

    Aside this sad fact, that small PC have decent specs, including 4 gigs of RAM, which makes it a good candidate for a single-node ElasticSearch cluster. I have to collect logs from my Kubernetes cluster somewhere, right?

    Unfortunately, Elastic dropped an official i586 support long time ago, which totally makes sense from commercial perspective.

    Well, thanks to Debian and Java we still can run ElasticSearch on top of 32-bit Linux!

    This tutorial is written for ElasticSearch OSS v7.5.1, and might not work for newer versions, as source code might change!

i586

  • 26 Dec 2019 elasticsearchelasticsearchELK32biti586

    Running ElasticSearch on 32-bit Linux machine

    I have an old piece of hardware with Atom D2700 CPU, which according to ARK is capable of running x64 OS. Vendor, however, never released a BIOS with x64 support, and I was unable to find it on an Internet.

    Aside this sad fact, that small PC have decent specs, including 4 gigs of RAM, which makes it a good candidate for a single-node ElasticSearch cluster. I have to collect logs from my Kubernetes cluster somewhere, right?

    Unfortunately, Elastic dropped an official i586 support long time ago, which totally makes sense from commercial perspective.

    Well, thanks to Debian and Java we still can run ElasticSearch on top of 32-bit Linux!

    This tutorial is written for ElasticSearch OSS v7.5.1, and might not work for newer versions, as source code might change!

pulumi

python

  • 21 Apr 2020 kuberneteskubernetespulumipythonhelm

    Kubernetes state management with Pulumi and Python

    I like Kubernetes way of declarative workload configuration, but handling cluster state using dozens or hundreds of YAML files is impractical.

    Of course, one can just combine them all into a single uber-YAML :smile:. But the harsh reality is, despite the fact that Kubernetes by design can and will apply this configuration asynchronously, and eventually cluster state will achieve the desired state, this “eventually” might be equal to infinity.

    There are certain cases when order matters, for instance when new CRD definitions are added, and then new objects with that kind are declared.

    Another aspect is complexity, which can be encapsulated by tools such as Helm. While Helm is a good solution for the problem of installing third-party apps, it’s not necessary a right choice for your own services, or for lightweight overall cluster configuration.

    And one more thing. I enjoy the kubernetes architecture, even (and especially!) the fact that numerous abstractions are needed to “canonically” expose a single container to the rest of the world. But it doesn’t mean that I enjoy to break a DRY principle, and copy-paste-modify same YAMLs over and over.

    So… Pulumi to the rescue!

helmsman

sops

helm-secrets

helm-whatup

flatcar

hypriotos

k3s