shit i like
    My road to self hosted kubernetes with k3s - Cert Manager

    cert-manager uses letsencrypt’s certificate authority to request/update keys/crts

    April 11, 2021 Read
    My road to self hosted kubernetes with k3s - logging with EFK

    Elasticsearch Fluent Kibana - we ll be using these three tools to setup a generic logging for our pods

    April 11, 2021 Read
    My road to self hosted kubernetes with k3s - distributed storage with ceph

    here we ll cover how to setup ceph storage and create a storage class which we can use in other deployments to store data persistent across the nodes

    April 11, 2021 Read
    My road to self hosted kubernetes with k3s - Bootstrap k3s cluster using ansible and k3sup on debian 10

    In this article we are going to setup k3s on 3 dedicated servers, we ll be using k3sup to do most of the work and trigger the setup by using an ansible playbook

    March 28, 2021 Read
    My road to self hosted kubernetes with k3s

    this is a farytale from a devops engineer from Berlin

    March 27, 2021 Read
    Kubernetes Cert Manager for Letsencrypt Based Certificates With Nginx Ingress

    Cert Manager cert manager stores certificates in kubernetes secret store and we can configure the nginx-ingress to use these certificates. cert-manager.yaml wget https://github.com/jetstack/cert-manager/releases/download/v0.15.1/cert-manager.yaml kubectl apply --validate=false -f cert-manager.yaml cert-manager.crds.yaml wget https://github.com/jetstack/cert-manager/releases/download/v0.15.1/cert-manager.crds.yaml kubectl apply --validate=false -f cert-manager.crds.yaml using the ClusterIssuer allows us to create certificates across all namespaces letsencrypt-issuer.yaml apiVersion: cert-manager.io/v1alpha2 kind: ClusterIssuer metadata: name: letsencrypt-prod spec: acme: # The ACME server URL server: https://acme-v02.api.letsencrypt.org/directory # Email address used for ACME registration email: loeken@internetz.

    June 13, 2020 Read
    Kubernetes Namespaces

    Kubernetes namespaces Imagine two teams build similar apps running in the same cluster. in order to avoid duplicated names etc and in order to group resources namespaces can be used to logically separate things. You could also use it to separate staging/production You could also use it if you want to run multiple different production environments. Notes: ConfigMap and Secrets can only be used inside a namespace Namespaces can be used to limit access to namespaces Namespaces can be used to limit resources to namespaces ( cpu / mem / storage ) the default namespaces kubectl get namespaces NAME STATUS AGE default Active 5d14h kube-system Active 5d14h kube-public Active 5d14h kube-node-lease Active 5d14h kubernetes-dashboard Active 5d14h manage namespaces via command line kubectl create namespace mynamespace namespace/mynamespace created kubectl get namespaces NAME STATUS AGE default Active 5d14h kube-system Active 5d14h kube-public Active 5d14h kube-node-lease Active 5d14h kubernetes-dashboard Active 5d14h mynamespace Active 6s kubectl delete namespace mynamespace namespace "mynamespace" deleted to use namespaces in yaml markup simply add:

    June 10, 2020 Read
    Kubernetes Create Images in Azure Container Registry

    Creating a Container registry @ azure For this we’ll be using the azure container registry, alternatively you can use docker.io or google/aws based services. I will name my registry demoregistry this guide will get you started dependencies for azure registry: now we login via the azure cli pacaur -S azure-cli az login az acr login --name demoregistry after the az login it will show now let’s package up the node app

    June 9, 2020 Read
    Navigation
    • Recent Posts
    • Projects
    • Experiences
    • Skills
    Contact Me
    • Email: loeken@internetz.me

    Toha
    © 2020 Copyright.
    go rocks!