So to begin This site runs on Gitlab Pages or that was the case until now Why change it? Gitlab Pages is impressive, they give you for free a place to run your SSG site without problems but all infrastructure fails sometimes gitlab others GCP infrastructure changes I have to say for the last past 2 years only 5 times the site was down!? I don’t remember exactly, and in most of the case the site was down only a couple of minutes Here is more information about all issues on gitlab pages if you want to trace them
Asumptions and Clarifications We are going to configure an existing two nsd server, one in powerpc mac mini and the other one in a vm with openbsd . We need to have one domain registered by us , in this case im using namecheap. I am not using nsd-control to administrate nsd, it is another option. Configuring Zones with dnssec You need to have a previous one without dnssec.
Asumptions and Clarifications We are going to configure an existing two nsd server, one in powerpc mac mini and the other one in a vm with openbsd . We need to have one domain registered by us , in this case im using namecheap. I am not using nsd-control to administrate nsd, it is another option. Configuring Zones without dnssec In this chapter we are going to configure a zone in both nodes and test it how i can trasnfer it and how i can make any query to the new zone.
Asumptions and Clarifications We are going to install a worker node You already installed a master node using first part as guide most of the steps are the same but we will repeat them just in case Installing 1. Preparing the node As we mentioned we are going to install Docker as Runtime for that we need several tools that are not included with the OS by default Install packages to allow apt to use a repository over HTTPS
What is Jitsi? Jitsi is a collection of Open Source projects which provide state-of-the-art video conferencing capabilities that are secure, easy to use and easy to self-host Here we are going to create a single VM with all the containers that Jitsi needs to work of course all this can be created in a different and more scalable way, but this is just a starting point Deploying a Jitsi server on GCP and create a dns record on cloudflare to publish the services Installing tools 1.
Creating a basic AKS(Kubernetes) cluster on Azure with Terraform Creating an AKS cluster on azure is really simple and you don’t need to know anything about it, well maybe some Azure but nothing complex Installing tools 1. Azure cli This terraform code uses the cli authentication so you will need to have installed the azure cli https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest you will need it to get some data nevertheless 2. Terraform If you still doesn’t have Terraform installed on your computer you can follow this link https://www.
Installing Openshift 4 on VMware Installing Openshift 4 on Vmware is complex with many things to consider and services to configure Troubleshooting an installation is more complex and usually all those errors comes from badly configured pre-requisites So in order to make it a little easier we created a helper node with all services needed: DNS Apache serving ignition files Haproxy for the load balancer Terraform and all the tools Ova template for the nodes DHCPD for booting the VMs with temporal IPs, fixed IPs will be configured after rebooting Let’s begin Installing Ansible and requisites yum install ansible python2-pyvmomi python-requests -y ansible-galaxy install robertdebock.
Openbsd and mac mini g4 I want to remember how to configure auto-boot after install openbsd in a mac mini g4. Configure OpenFirmware mac mini g4 Remember those steps !! Boot in bios pressing the button power and release it when you see the blank screen. setenv auto-boot? true setenv boot-device hd:,ofwboot reset-all If you want to get more info about post installation step please check t in openbsd notes for macppc.
Asumptions and Clarifications The main goal of this post is get hand on with kubeadm commands. This is not for production or any kind of specific process. Upgrade Master 1- Drain Node kubectl drain master –ignore-daemonsets ter $ kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready master 55m v1.16.0 node01 Ready <none> 55m v1.16.0 master $ kubectl drain master --ignore-daemonsets node/master cordoned WARNING: ignoring DaemonSet-managed Pods: kube-system/kube-proxy-jmwgk, kube-system/weave-net-xzrl6 evicting pod "coredns-5644d7b6d9-cjkkc" pod/coredns-5644d7b6d9-cjkkc evicted node/master evicted master $ kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready,SchedulingDisabled master 56m v1.
Asumptions and Clarifications Kubernetes will be installed on Debian 10 (buster) HA must be already configured on a Load Balancer unless you use only 1 master This process is to install 1 master following parts we will be adding new masters and workers We will install docker as Runtime for the containers, is the most used until now Next tutos we will install it using others Runtimes At least port 6433 must be open to communicate from the client to the master node in order to deploy apps on the kubernetes cluster
So to begin This site runs on Gitlab Pages Why? We wanted a site that is easy for us to write we are writing doc in markdown language everyday and we want to learn more about it Also we wanted to be distributed without any downtime if possible Gitlab infrastructure is GCP based not much to say all the features of a cloud provider at our hands Easy to migrate What more easy than migrating html static pages