- local https://github.com/kubernetes-sigs/kind (or just use minikube if it works for you)
- cloud https://cloud.google.com/kubernetes-engine (for PersistentVolume and Ingress, I needed to try the real deal)
- practice environment: https://github.com/arush-sal/cka-practice-environment
#!/bin/bash | |
# Script to create a namespace in Kubernetes and apply resource quota and network policies to it | |
# Created by Donni Triosa ([email protected]) | |
# Check if the namespace argument is provided | |
if [ -z "$1" ]; then | |
echo "Usage: $0 <namespace>" | |
exit 1 | |
fi |
This tutorial guides you through the process of creating Templates and Virtual Machines on Proxmox using cloud-based images from various Linux distributions. We provide clear instructions for Alma Linux 9, Amazon Linux 2, CentOS 9, Fedora 38, Oracle Linux 9, RHEL 9, Rocky Linux 9, and Ubuntu 23.04 Lynx Lobster.
Note: The instructions have been tested on Proxmox 8.0.4.
Let's begin by choosing the cloud-based image. If you already have your preferred Linux distribution, skip to the 1st step.
To assist in making informed choices when selecting a Linux distribution for your virtual machines, we've compiled a table showcasing key characteristics of each cloud image. This table provides a snapshot of important attributes, including kernel version, Python version, number of processes initialized after boot, number of packages installed, free memory after boot, VM disk size, root partition disk size, used size on t
prep: | |
helm repo add nvidia https://helm.ngc.nvidia.com/nvidia \ | |
&& helm repo update | |
install: | |
helm install --wait nvidiagpu \ | |
-n gpu-operator --create-namespace \ | |
--set toolkit.env[0].name=CONTAINERD_CONFIG \ | |
--set toolkit.env[0].value=/var/lib/rancher/k3s/agent/etc/containerd/config.toml \ | |
--set toolkit.env[1].name=CONTAINERD_SOCKET \ |
# Install prerequisites | |
sudo apt-get -y update | |
sudo apt-get -y install ca-certificates curl gnupg lsb-release | |
# Setup Docker's repository | |
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg | |
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/debian \ | |
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null | |
sudo apt-get -y update |
This is a writedown of how I installed my raspberry pi(s).
The base is a Proxmox, so I don't have to worry about reformat the SD card every time I wanna try out something new, as I can start VMs and LXC containers, as well as Docker containers once it's configured properly.
Note: Those files are versioned, so you can always look what changed from time to time.
- Pimox
Use your service account's key JSON file to get an access token to call Google APIs.
Good for seeing how things work, including the creation of JWT token.
To create a JWT token, you can replace create-jwt-token.sh
script with tools like step.
If you just want to get an access token for a service account,
Some random notes on trying (and failing) to get Proxmox as host with 5700G APU GPU PCI Passthrough to Ubuntu guest VM working:
References:
- Looks like this one claims to have this working (but I have not tested the method) :
- Others trying to get this working:
- https://forum.level1techs.com/t/got-my-ryzen-4750g-apu-igpu-to-pass-through-to-qemu-kvm-vm-but-display-output-is-pixelated-garbage-after-amd-apu-radeon-driver-install-from-amd-or-windows-update/169903
Prometheus is an open-source systems monitoring and alerting toolkit originally built at SoundCloud. Since its inception in 2012, many companies and organizations have adopted Prometheus, and the project has a very active developer and user community. It is now a standalone open source project and maintained independently of any company
In this guide we will use Debian based Linux distribution version 10 (Buster). If you are using an Cloud Instance like in Amazon Web Service you can use the default provided Ubuntu Amazon Machine Image (AMI) Debian 10 (Buster) 64-bit when you are provisioning it
""" | |
Create a Persistent Volume called log-volume. It should make use of a storage class name manual. It should use RWX as the access mode and have a size of 1Gi. The volume should use the hostPath /opt/volume/nginx | |
Next, create a PVC called log-claim requesting a minimum of 200Mi of storage. This PVC should bind to log-volume. | |
Mount this in a pod called logger at the location /var/www/nginx. This pod should use the image nginx:alpine. | |
""" | |
apiVersion: v1 | |
kind: PersistentVolume |