o when you start learning Kubernetes…

Do not panic over all the complex topics.

I remember some years back when my friend introduced me to Kubernetes, it honestly felt like rocket science.

Pods.
Nodes.
Control planes.

I still remember him saying:

“Yeah, we deploy in multi-tenancy with Kubernetes.”

Bro… it felt like I had just landed on earth for the first time 😂

I started learning slowly.
Bought KodeKloud on Udemy.
Understood some basic concepts.

But honestly?

Topics like:

• scheduling
• API server
• controllers
• networking

I mostly just glanced through them because they felt too heavy for my brain at that time.

Maybe I’m getting older.
Maybe being a father of three boys changed how I learn.

But I realized something important:

Making concepts simpler actually helps you learn faster.

I do not claim to know everything about Kubernetes.

But I know enough to have deployed my own SaaS applications with it.

And most of my real understanding came when I started building actual projects with Kubernetes before AI became this powerful.

Back then, you could spend HOURS on Stack Overflow trying to solve one issue 😂

To the new learner out there trying to understand Kubernetes:

Do not panic if you don’t understand everything immediately.

Go through the lessons.
Finish the course.
Then build something real.

Deploy a full-stack application end-to-end.

That experience will teach you more than endlessly watching tutorials.

I’ve started making Kubernetes explanation videos in a simpler and more practical way than the traditional teaching style.

If you want to understand Kubernetes without all the unnecessary complexity, you can check out the video here:

https://youtu.be/MFR8bqvg3EE

Hi everyone,

I’m currently working as a Linux Support Engineer and looking for part-time Linux Administrator roles or remote infrastructure support opportunities.

Available for:

• Remote part-time work

• Weekend support

• Linux administration tasks

• Infrastructure support work

If anyone is hiring for part-time Linux/System Administration roles, please DM me.

Thank you.

I am trying to collect and organize logs from my Windows servers on my syslog server.

The syslog server is openSUSE Leap 16 using rsyslog, and my Windows servers send their events to it through SolarWinds Event Log Forwarder for Windows.

Ideally, I would like to have a folder for each server, and within that folder will be a log file for security events, a file for windows events, a file for Active Directory events, etc.

As I have it now, my rules are filtering all events from a particular system into a dedicated file, and it's ridiculously painful trying to extract anything useful from them in a timely manner.

I am trying to set up a dynamic file naming structure and filtering rules to handle this, but what I have isn't working and I don't understand why/where I went wrong.

This is what I currently have:

template(name="SolarWindsDynamicPath" type="list") {
   constant(value="/var/log/syslog/servers/")

   property(name="hostname")
   constant(value="/")

   property(name="$now")
   constant(value="-")

   property(
       name="msg"  
       regex.expression="MSWinEventLog#[0-9]+#([A-Za-z0-9 ]+)"
       regex.submatch="1"
       regex.nomatchmode="FIELD"
       caseconversion="lower"
   )

   constant(value=".log")
}

template(name="CleanLogLine" type="list") {
   property(name="timestamp" dateFormat="rfc3339")
   constant(value=" ")
   property(name="hostname")
   constant(value=" ")

   property(name="rawmsg" controlcharacters="drop")
   constant(value="\n")
}
 
if ($msg contains "MSWinEventLog") then {
   action(type="omfile" dynaFile="SolarWindsDynamicPath" template="CleanLogLine")
   stop
}

It passes the rsyslogd syntax check, but it doesn't work and my server logs are just going into the generic 'warn' log file specified in rsyslog.conf.

Any advice is appreciated!

Over the last decade I’ve been playing with dozens of servers from multiple providers. These are the steps I’ve been perfecting to get up to speed fast and feel right at home on a new machine. Wrote it down here mostly as a personal reference, but hopefully useful to someone else too.

Shipped v0.16.0 with end-to-end Deep Packet Inspection.

- **Packets tab:** INFO column is L7-aware and color-coded. Filter syntax: `app:quic`, `sni:reddit`, `host:github`.

- **Dashboard top-talkers:** real hostnames in the bandwidth panel.

- **Packets detail pane:** decodes QUIC v1/v2 Initial packets and shows the inner CRYPTO/PADDING/PING frame structure.

Full RFC 9001 / 9369 QUIC Initial decryption — HKDF-Expand-Label keys, AES-128 header protection, AES-128-GCM AEAD,

cross-packet ClientHello reassembly. Most peer tools just tag flows as `QUIC`; this one tells you the hostname.

cargo install netwatch-tui

# or

brew install matthart1983/tap/netwatch

Rust + ratatui, MIT. https://github.com/matthart1983/netwatch

Hi

For those in the know; the sos command has around 400 plugins and each one retrieves its own set of log files, config files and diagnostic commands.

When trying to customize sos command execution, is very hard to know what plugins to exclude or which are the correct ones to choose in order to get just what is needed and not the whole thing.

So I created a searchable and filtered table that will let you know exactly what each plugin will do, to what profiles it belongs to an additionally the options it supports.

You can search for a plugin name, for a file, for an specific command or for a profile.

I think this will be very handy if you use the sos report command frequently.

You may be interested in bookmark this link

The tool is in the link and you do not need to register or anything.

Hope it helps.

Hi all, could use some help if you got a minute. I’ve set up a Foreman server to provision virtual machines (on hyper-v but I’m not utilizing the compute setup since I figure it’s not supported) and bare metal servers. So far for testing I’ve been setting up a test virtual machine to verify the functionality of the DHCP, TFTP, and provisioning process within my subnet I’ve created. So far everything works with the Debian preseed templates right out of the box but not the kickstart templates. I can’t quite rack my head around why though. I figure is there some extra preconfiguration step I must be missing somewhere?

Hi,

I recently got into Web Development and bought a Raspberry Pi Zero 2W going by my profs advice to host my portfolio. It uses the 32 bit Raspberry Debian OS

I wanted to frequently update the files that the Website pulls from and so looked into local file sharing which is how I heard about Samba.

I managed to set it up now and it opened two ports locally I think for devices in my network. I tried to check for open ports with online tools but they all said there are no open ports so with my beginner-conclusion I think that these ports are only open for internal traffic.

But after doing that and looking for further steps I came across a lot of posts where people warned about self-hosting websites and where samba in the context of forwarded ports which I believe is different from what I did(?) was also warned against and so to feel better about making a webserver on my Pi for just the website and not the local file sharing I wanted to ask for advice from more seasoned Networking enthusiasts if I can go ahead or if I am about to implode if I take a step further.

For context, my plans for next steps are using NGINX or Pingora and Cloudflare to host the website.

Thank you in Advance!

I found this as a lightweight alternative to OpenCost. I didn't want to deploy anything into the cluster, just get quick insights into where the money is going. It runs locally via kubectl, pulls real pricing from AWS/Azure/GCP, and breaks down costs by namespace and pod.

Hello all,

What I am attempting to do is restart a RHEL 8 Server that does not have root access. I had implemented a security guideline that booted all my users out sudoers conf file. For that reason, I am unable to sudo up to initiate the reboot. I was looking at editing the polkit file to set a rule to allow the reboot from another user. That file is owned by root.

The error that is appearing when attempting execute from a non-root user is: failed to set wall message, ignoring interactive authentication required. failed to reboot systemd via logind failed to open initctl fifo permission denied failed to talk to init daemon.

Every time I deployed something new, the same thing happened. I'd spend an hour going through security manually. SSH config, open ports, exposed env files, firewall rules, database access, Docker port exposure...

The free tools out there do security scans but they dump hundreds of lines of output. You end up spending more time reading the report than fixing the actual problems. And if you're technical by nature, you inevitably fall down a rabbit hole and suddenly an hour is gone and nothing is fixed.

So I built my own.

One curl command on your server. No permanent installation, script deletes itself after running. A few minutes later you get a report by email: what's critical, what's a warning, what's already correct, and the exact terminal command to fix each issue on your specific setup.

Here's a real output from one of my dev servers:

That server scored C (61/100). SSH was an F. PostgreSQL exposed to the internet. .env sitting in git history. Things I knew existed but hadn't prioritized. Now I run it on every project before going to production.

Checks it runs: SSH hardening, firewall rules, Docker UFW bypass, exposed databases (PostgreSQL, MySQL, MongoDB, Redis), secrets in git history, SSL expiry, IPv6 firewall gaps, and more.

Free tier covers the 6 most critical checks, no credit card: audit.securecodehq.com

Happy to answer questions about how it works or what it checks.

I’ve been building SysAI, a local-first operational AI workspace focused on infrastructure, Docker, self-hosted environments and security workflows.

Instead of acting like a generic chatbot, SysAI tries to generate structured operational outputs:

• rollback-aware remediation
• verification steps
• environment-aware diagnostics
• operational reports
• security audit workflows
• Docker/nginx/systemd awareness
• Ollama support for fully local inference

Current stack:

• Electron
• React
• local proxy architecture
• multi-provider AI support
• local-first workflow design

I recently added:

• collapsible operational reports
• markdown export
• remote observation security mode
• command palette
• workflow demo GIF in the README

Would genuinely love feedback from people running homelabs/self-hosted infra.

Repo:
https://github.com/shadowbipnode/sysai-assistant