Regulatory Compliance in the Cloud Compliance is a critical aspect of any organization’s operations, particularly when it comes to data security and privacy. In the realm of cloud computing, compliance requirements can be complex and varied, depending on the industry and regulatory environment. This note provides an overview of the different tiers of compliance, including FISMA, FedRAMP, and HIPAA, and outlines the specific control areas that organizations must address to achieve compliance.

When to NOT use Kubernetes Have you ever wondered if using a Kubernetes for a small to medium scale application is worth the complexity and overhead? In many cases, the benefits might not outweigh the costs (financial or emotional) or the added complexity needed to maintain a Kubernetes platform, particularly when the applications require few resources and have low traffic volume. When does Kubernetes make sense for your application? Let’s take a look at some of the scenarios where Kubernetes may not be the best choice.

Pi Hole For a while I was running PiHole on a raspberry pi64. Installed docker, docker-compose, git Configured running raspberry pi with docker https://github.com/pi-hole/docker-pi-hole#readme docker-compose.yaml 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/Denver' PIHOLE_DNS_: 127.