kubernetes

A collection of 18 posts
SOLVED: rke2-agent-3 systemd[1]: Failed to start Rancher Kubernetes Engine v2 (agent) invalid kernel parameter
kubernetes

SOLVED: rke2-agent-3 systemd[1]: Failed to start Rancher Kubernetes Engine v2 (agent) invalid kernel parameter

root@:/etc/rancher/rke2# sudo systemctl status rke2-agent â—Ź rke2-agent.service - Rancher Kubernetes Engine v2 (agent) Loaded: loaded (/usr/local/lib/systemd/system/rke2-agent.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2023-11-29 13:37:29 CET; 1min 2s ago Docs: https://github.com/rancher/rke2#
— 2 min read
Helm install OpenSearch Cluster with persistence to local disk + Hunspell
kubernetes

Helm install OpenSearch Cluster with persistence to local disk + Hunspell

kubectl apply -f values.yaml values.yaml # Only create this for K8s 1.9+ apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: local-storage provisioner: kubernetes.io/no-provisioner volumeBindingMode: WaitForFirstConsumer # Supported policies: Delete, Retain reclaimPolicy: Retain --- apiVersion: v1 kind: PersistentVolume metadata: name: opensearch-agent-1 spec: accessModes: - ReadWriteOnce capacity: storage:
— 3 min read
kubernetes

Helm install Bitnami MariaDB Galera to hostPath

$ kubectl apply -f pvc.yaml --- kind: Namespace apiVersion: v1 metadata: name: mariadb-galera-new --- apiVersion: v1 kind: PersistentVolume metadata: name: mariadb-galera-new-pv namespace: mariadb-galera-new spec: storageClassName: manual # mountOptions: # - dir_mode=0777 # - file_mode=0777 capacity: storage: 40Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain hostPath: path: "/bitnami/mariadb-galera-new/" --- apiVersion: v1
— 3 min read
Redirect .env file to your Curriculum Vitae - simplest way to Ingress redirect via annotations in Kubernetes
kubernetes

Redirect .env file to your Curriculum Vitae - simplest way to Ingress redirect via annotations in Kubernetes

Redirect /.env file to your curriculum vitae via nginx.ingress.kubernetes.io/temporal-redirect annotation apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/ssl-redirect: "true" kubernetes.io/tls-acme: "true" nginx.ingress.kubernetes.io/from-to-www-redirect: "true" nginx.ingress.kubernetes.io/temporal-redirect: https://exploit.cz/content/images/2021/CV-KOLBL-PHP-2021-EN.pdf name:
— 1 min read
How to set REMOTE_ADDR from HTTP_X_ORIGINAL_FORWARDED_FOR header when going through EZOIC proxy cache
kubernetes

How to set REMOTE_ADDR from HTTP_X_ORIGINAL_FORWARDED_FOR header when going through EZOIC proxy cache

Prerequisites: * kubernetes ingress * your varnish proxy cache * Symfony PHP application 1. Edit your global Kubernetes Ingress Config Map in namespace ingress-nginx named nginx-configuration [https://rancher2.exploit.cz/p/local:p-mt7fw/config-maps/ingress-nginx:nginx-configuration] and add use-forwarded-headers: true 2. In your Varnish proxy in section sub vcl_recvadd if (req.http.
— 1 min read
How to autoreload Varnish Cache backends when Kubernetes Deployment changed
kubernetes

How to autoreload Varnish Cache backends when Kubernetes Deployment changed

You can use quay.io/spaces/kube-httpcache:stable - Github README [https://github.com/mittwald/kube-httpcache/blob/master/README.md] Necessary configuration when RBAC is enabled: * create ServiceAccount: kubectl --kubeconfig kube_config_cluster.yml -n web create serviceaccount varnish-watcher * create ClusterRole + ClusterRoleBinding: kubectl --kubeconfig kube_config_cluster.yml apply -f
— 2 min read