Zak's Notes

Traefik Ingress for DNS Wildcard-Based Service Exposured on Kubernetes Kubernetes, an open-source platform for managing containerized workloads and services, offers amazing flexibility in deploying and scaling applications. A key aspect of this flexibility lies in Kubernetes’ network routing, especially when it comes to Ingress controllers like Traefik. In this blog post, we delve into the details of Traefik Ingress and discuss how it can be effectively leveraged to expose a service through DNS wildcard to services running on Kubernetes.

Here’s a basic example of a GitHub Action for creating a Kubernetes cluster in GCP using the gcloud CLI: name: Create Kubernetes Cluster in GCP on: [push] env: PROJECT_ID: <Your GCP Project ID> CLUSTER_NAME: <Your Kubernetes Cluster Name> ZONE: <Your GCP Zone> jobs: create-cluster: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v2 - name: Configure Google Cloud CLI uses: google-github-actions/configure-cloud-sdk@master with: project_id: ${{ env.PROJECT_ID }} - name: Create Kubernetes Cluster run: | gcloud config set project ${{ env.

Kubernetes is an open-source platform for automating deployment, scaling, and management of containerized applications. In this tutorial, you will learn how to install and set up a Kubernetes cluster using kubeadm. Before you start, make sure your system meets the following requirements: A Linux operating system, such as Ubuntu or CentOS. Docker installed and running on all nodes. Minimum of 2 GB of RAM and 2 CPU cores on each node.

Kubernetes is a powerful tool for deploying and managing containers, but with many containers running in a cluster, it can be difficult to keep track of logs and troubleshoot issues. Fluent Bit is a log shipper that can be used to collect and aggregate logs from your containers and make them available for analysis and troubleshooting. In this tutorial, we’ll demonstrate how to set up Fluent Bit in a Kubernetes cluster and use it to collect and aggregate logs from your containers.

Kubernetes admission controllers are a critical component of the Kubernetes API server. They are responsible for enforcing various policies on the resources being created or modified in the cluster. An admission controller intercepts a request to create or modify a resource in the cluster and either accepts or rejects the request based on the policies it implements. Annotations are metadata associated with a Kubernetes resource. They can be used to provide additional information about a resource, such as its purpose, ownership, or any other relevant information.