Kjell Hysjulien

I deployed this portfolio site to gain hands-on experience with real AWS infrastructure and modern DevOps practices. The site is hosted on S3, served securely through CloudFront, and mapped to my custom domain using Route 53. I manage the setup with Terraform, and the deployment process is automated using GitHub Actions with OIDC authentication.

This project gave me practical experience with DNS configuration, TLS certificates, CI/CD pipelines, and infrastructure as code. It also taught me how to secure deployments using temporary credentials and keep infrastructure reproducible.

• Infrastructure as Code: Used Terraform to define and manage S3, CloudFront, Route 53, and ACM resources
• CI/CD Automation: Configured GitHub Actions to sync changes to S3 and invalidate CloudFront cache on every push
• OIDC Authentication: Set up GitHub’s OpenID Connect provider to assume an IAM role without storing AWS credentials
• Custom Domain & TLS: Managed DNS records and provisioned a certificate through ACM for HTTPS access

View the code + full setup guide

I deployed a DNS filtering and ad-blocking system using Pi-hole in Docker on a Raspberry Pi 3 running Raspberry Pi OS Lite. This project gave me hands-on experience with containerization, Linux networking, persistent storage, and home network integration.

I started by flashing Raspberry Pi OS Lite with custom SSH, locale, and hostname settings, then installed Docker and Docker Compose. I created a containerized Pi-hole setup using network_mode: host for full DNS compatibility, mounted persistent config volumes, and locked down the system for privacy and stability. Finally, I configured my ASUS router to route all DNS traffic through the Pi-hole instance and tested full functionality across devices.

• Raspberry Pi Prep: Flashed 32-bit Pi OS Lite with custom SSH access, static hostname, and key-based auth
• Dockerized Setup: Ran Pi-hole in Docker Compose using host networking and mounted persistent volumes
• Network Integration: Configured ASUS router to use the Pi-hole as primary DNS for WAN and DHCP
• Privacy & Access Control: Disabled upstream fallback, limited logging, secured web UI, and verified admin-only access

View the code + full setup guide

I built a working Kubernetes cluster using Multipass, Kubeadm, and Flannel CNI on my macOS system. The goal was to get real experience standing up a multi-node cluster, configuring container runtimes, managing networking, and learning cluster lifecycle tasks end to end.

The setup included one control plane node and one worker node, each running in its own Ubuntu 24.04 VM. I used Kubeadm for initialization, installed Containerd as the runtime, and configured system settings manually to support pod networking. I also deployed a test workload, backed up cluster resources, and scripted a full teardown process using Multipass.

• Multi-Node Cluster: Launched and configured isolated VMs with Multipass to simulate real node behavior
• Kubeadm Setup: Initialized the cluster with pod CIDR, Flannel CNI, and a secure node join process
• Container Runtime: Installed and configured Containerd with systemd cgroups for production parity
• Backup & Teardown: Backed up cluster manifests and practiced teardown

View the code + full setup guide