<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oleksandr Kulbida</title>
    <link>https://okulbida.com/</link>
    <description>Recent content on Oleksandr Kulbida</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 05 Nov 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://okulbida.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes pod hardening: a container is still a Linux process</title>
      <link>https://okulbida.com/posts/kubernetes-pod-hardening-linux-kernel/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/kubernetes-pod-hardening-linux-kernel/</guid>
      <description>Start with a quick check on one of your clusters:
1 2  kubectl run probe --rm -it --restart=Never --image=busybox:1.37 -- \  grep -E &amp;#39;Seccomp:|CapEff&amp;#39; /proc/self/status   Unless someone has already changed the defaults, you&amp;rsquo;ll see something like this:
1 2  CapEff: 00000000a80425fb Seccomp: 0   Seccomp: 0 means no syscall filter at all. The process can ask the kernel for anything its capabilities allow, and that kernel is shared with every other pod on the node.</description>
    </item>
    
    <item>
      <title>Building Docker images with Nix: same inputs, same hash</title>
      <link>https://okulbida.com/posts/nix-docker-images-reproducible-builds/</link>
      <pubDate>Sun, 01 Nov 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/nix-docker-images-reproducible-builds/</guid>
      <description>Run docker build twice on the same Dockerfile, with no changes in between, and compare the results:
1 2  docker build -t app:v1 . &amp;amp;&amp;amp; docker save app:v1 | sha256sum docker build -t app:v2 . &amp;amp;&amp;amp; docker save app:v2 | sha256sum   The two hashes won&amp;rsquo;t match. Nothing in your code changed, but the image did. I&amp;rsquo;ve been building images with Nix for a while, and it fixes exactly this.</description>
    </item>
    
    <item>
      <title>Anthropic replaced git with its own source control: Scion</title>
      <link>https://okulbida.com/posts/anthropic-scion-source-control-replaced-git/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/anthropic-scion-source-control-replaced-git/</guid>
      <description>Anthropic doesn&amp;rsquo;t use git for its monorepo anymore. In five months they moved to their own version control system called Scion, and the reason is simple: agents write too much code for git to keep up.
The numbers In May 2026 about 2,500 changes a day were merged into Anthropic&amp;rsquo;s monorepo. By September it was over 30,000. Most of that growth comes from Claude writing code, not from people.
At that scale the repository itself becomes the problem:</description>
    </item>
    
    <item>
      <title>Five layers of LLM defense, and why activation guardrails won&#39;t save you alone</title>
      <link>https://okulbida.com/posts/llm-defense-layers-activation-guardrails/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/llm-defense-layers-activation-guardrails/</guid>
      <description>If you think LLM attacks are still caught with a list of regular expressions, you&amp;rsquo;re living in 2023. A lot has changed since then. Defenses now live everywhere from the training run to the production proxy in front of the model, and some of them reach right into the model&amp;rsquo;s hidden states while it&amp;rsquo;s thinking.
I find it useful to split all of this into five layers, from what&amp;rsquo;s baked into the weights to what happens around a deployed model:</description>
    </item>
    
    <item>
      <title>AX: Google&#39;s orchestrator for AI agents on Kubernetes</title>
      <link>https://okulbida.com/posts/google-ax-agent-executor-kubernetes/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/google-ax-agent-executor-kubernetes/</guid>
      <description>In 2014 Google released Kubernetes to manage lots of containers across lots of hosts. Today it&amp;rsquo;s the de facto standard for running workloads.
In 2026 Google released AX (Agent Executor) to manage lots of autonomous agents inside a Kubernetes cluster. Whether it becomes a standard too, only time will tell.
AX is infrastructure for running AI workloads. It runs on top of Kubernetes and Agent Substrate, which provides the sandboxed execution.</description>
    </item>
    
    <item>
      <title>k8s-aibom: finding out which AI workloads are actually running in your cluster</title>
      <link>https://okulbida.com/posts/k8s-aibom-runtime-ai-inventory/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/k8s-aibom-runtime-ai-inventory/</guid>
      <description>At some point someone from security or compliance asks the platform team a simple question: &amp;ldquo;Which models are we running in production, and where?&amp;rdquo; Usually nobody has a good answer. There&amp;rsquo;s a spreadsheet that was correct six months ago, a few Helm charts that mention vLLM, and that one team that deployed Ollama in a dev namespace &amp;ldquo;just to try something&amp;rdquo; and forgot about it.
k8s-aibom is an open source controller from Google Cloud that tries to answer this question by looking at the cluster itself.</description>
    </item>
    
    <item>
      <title>50 ChatGPT &#34;commands&#34; for learning faster from books, articles and lectures</title>
      <link>https://okulbida.com/posts/chatgpt-study-commands-learn-faster/</link>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/chatgpt-study-commands-learn-faster/</guid>
      <description>Most people use ChatGPT for reading the same way. Paste an article, type &amp;ldquo;summarize this&amp;rdquo;, get back a wall of text that&amp;rsquo;s about 70% as long as the original. Then you don&amp;rsquo;t read that either.
A while ago I came across a list of short &amp;ldquo;commands&amp;rdquo; that change what the answer looks like. Instead of &amp;ldquo;summarize&amp;rdquo;, you write /flashcards or /argumentmap or /actionplan, and the output comes back in a format you can actually use.</description>
    </item>
    
    <item>
      <title>Docker Sandbox Kits: a Dockerfile for what your agent is allowed to touch</title>
      <link>https://okulbida.com/posts/docker-sandbox-kit-spec/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/docker-sandbox-kit-spec/</guid>
      <description>Docker published the Sandbox Kit Specification, an open format for packaging an environment for an AI agent together with a list of what that environment needs from the outside world.
A Dockerfile tells you what&amp;rsquo;s inside the image. A Kit also says what the image will want from outside: network destinations, credentials, volumes, tools, and context for the agent. The Kit doesn&amp;rsquo;t grant any of it, though. It asks. The runtime decides what to give and enforces the limits.</description>
    </item>
    
    <item>
      <title>systemd-report: a new systemd subsystem and lower-level alternative to node_exporter</title>
      <link>https://okulbida.com/posts/systemd-report-fleet-reporting/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/systemd-report-fleet-reporting/</guid>
      <description>systemd has a new tool called systemd-report. It gathers facts and metrics about a machine, writes them into one timestamped JSON document, optionally signs it, and can upload it to a server you choose.
This is for people running fleets of servers. If you have one laptop, you&amp;rsquo;ll probably never touch it.
What goes into a report There are two kinds of data. The first is stuff that barely changes, which systemd calls &amp;ldquo;facts&amp;rdquo;:</description>
    </item>
    
    <item>
      <title>Moving a Kubernetes service to another namespace without downtime</title>
      <link>https://okulbida.com/posts/kubernetes-namespace-migration-externalname/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/kubernetes-namespace-migration-externalname/</guid>
      <description>CNCF published a nice write-up by George Sims: Migrating a critical Kubernetes deployment from the default namespace without any downtime. The story is about an auth service that lived in default for years, but the approach works for moving any service from one namespace to another. default is just the example.
The main idea is simple. You keep the old DNS name alive as a compatibility point. In the old namespace you leave a Service of type ExternalName that points to the service in its new namespace, and callers keep working without changing anything.</description>
    </item>
    
    <item>
      <title>Claude Code cloud sessions are out of preview, with a $100 / $250 credit to try them</title>
      <link>https://okulbida.com/posts/claude-code-cloud-sessions-ga/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/claude-code-cloud-sessions-ga/</guid>
      <description>Anthropic announced today that Claude Code cloud sessions are generally available and no longer a research preview. The one-line pitch: Claude Code keeps working even when your laptop is closed.
To get people to try it, existing Pro and Max subscribers get a one-time credit: $100 on Pro, $250 on Max.
What a cloud session is A normal Claude Code session runs on your machine. If the laptop goes to sleep, loses Wi-Fi, or you just close the lid to go home, the session stops with it.</description>
    </item>
    
    <item>
      <title>Claude Opus 5.5: faster, cheaper, and better at long agentic work</title>
      <link>https://okulbida.com/posts/claude-opus-5-5-release/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/claude-opus-5-5-release/</guid>
      <description>Anthropic released Claude Opus 5.5 today. It&amp;rsquo;s the new flagship, and the pitch is simple: it beats Opus 5 on most things while costing less and responding faster. Usually you only get one of those at a time.
What actually changed The biggest gains are in agentic coding, computer use, and general knowledge work. Anthropic also says the model holds up better on long-running tasks and large codebases, which is where earlier models tended to lose track of what they were doing a few hours in.</description>
    </item>
    
    <item>
      <title>SkillsMP: an Agent Skills marketplace for Claude Code and Codex</title>
      <link>https://okulbida.com/posts/skillsmp-agent-skills-catalog/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/skillsmp-agent-skills-catalog/</guid>
      <description>SkillsMP is a searchable catalog of Agent Skills for Claude Code and Codex
SkillsMP indexes Agent Skills pulled from public GitHub repositories and puts them behind a search box, a category browser, and per-skill cards that link back to the source repo
Its own FAQ says it has collected 200,000+ skills so far (marketing copy elsewhere on the site claims over 2 million, so treat exact counts loosely). Categories run from backend, machine-learning, and llm-ai to security, devops, and web3-tools — around 70 in total, plus browsing by occupation and a timeline view</description>
    </item>
    
    <item>
      <title>Agent Plugins: one folder for skills and MCP servers, minus Claude</title>
      <link>https://okulbida.com/posts/agent-plugins-open-standard-skills-mcp/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/agent-plugins-open-standard-skills-mcp/</guid>
      <description>If you&amp;rsquo;ve built an Agent Skill and wired it to an MCP server, you already know the annoying part isn&amp;rsquo;t the skill. It&amp;rsquo;s everything around it. The instructions travel fine as a markdown file. The MCP server config does not, because every client wants its own directory layout, its own manifest, its own way of saying &amp;ldquo;run this process and pass it these environment variables.&amp;rdquo;
Vercel, AWS, GitHub, Microsoft, OpenAI, and the Cursor team shipped Agent Plugins 1.</description>
    </item>
    
    <item>
      <title>GitHub Spec Kit: give the AI agent a spec, not a vibe</title>
      <link>https://okulbida.com/posts/github-spec-kit-spec-driven-development/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/github-spec-kit-spec-driven-development/</guid>
      <description>Ask Claude, Codex, or Gemini to &amp;ldquo;build me an ERP with auth, billing, a dashboard, and a mobile app&amp;rdquo; and you&amp;rsquo;ll get something that half works and is architecturally cursed in ways you won&amp;rsquo;t notice until week three. The model isn&amp;rsquo;t bad at writing code. It&amp;rsquo;s bad at simultaneously inventing the product, the architecture, and the implementation order while also writing the code. GitHub&amp;rsquo;s Spec Kit exists to split those apart.</description>
    </item>
    
    <item>
      <title>Kubernetes 1.37 (Garhwal): what&#39;s worth knowing</title>
      <link>https://okulbida.com/posts/kubernetes-1-37-garhwal-release/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/kubernetes-1-37-garhwal-release/</guid>
      <description>Kubernetes 1.37, codename Garhwal, shipped August 26, 2026 after a 15-week cycle. 67 enhancements: 16 graduating to Stable, 23 to Beta, 27 new in Alpha, one deprecation track. Full release notes here.
The API surface itself tells a tighter story than the enhancement count does. I traced the actual version history of every API resource that changed in 1.37, back to 1.34, instead of trusting a changelog summary:
 .kv-wrap{margin:1.5rem 0;border:1px solid #e3e3e6;border-radius:10px;padding:2px;overflow-x:auto} .</description>
    </item>
    
    <item>
      <title>Kyverno threat model: the defaults that make enforcement optional</title>
      <link>https://okulbida.com/posts/kyverno-threat-model-hardening-guide/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/kyverno-threat-model-hardening-guide/</guid>
      <description>Fail open, by default Audit mode is not enforcement PolicyException: the quiet bypass Kyverno doesn&amp;rsquo;t watch its own namespace What Kyverno can never protect Sign and verify, not either Turning the admission controller into an SSRF probe Summary   Kyverno released a threat model and hardening guide in April 2026, produced by the security consultancy ControlPlane in partnership with the CNCF and reviewed by Kyverno&amp;rsquo;s own maintainers (Jim Bugwadia and Shuting Zhao among them).</description>
    </item>
    
    <item>
      <title>Terraform to OpenTofu: is it worth migrating?</title>
      <link>https://okulbida.com/posts/terraform-to-opentofu-migration/</link>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/terraform-to-opentofu-migration/</guid>
      <description>A reader sent me a question I&amp;rsquo;ve been getting more often lately: they&amp;rsquo;re running Terraform 1.5, S3 backend, no Terraform Cloud, no HCP. Is it worth moving to OpenTofu?
Short answer: probably yes, and this setup happens to be close to the easiest case there is. Here&amp;rsquo;s why.
The fork point matters OpenTofu forked from Terraform 1.5.x, the last version released under the MPL license before HashiCorp switched to BSL. So if you&amp;rsquo;re still on 1.</description>
    </item>
    
    <item>
      <title>Kubernetes tools</title>
      <link>https://okulbida.com/posts/kubernetes_tools/</link>
      <pubDate>Sat, 27 Jun 2026 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/kubernetes_tools/</guid>
      <description>This list is being updated on regular basis
General info  https://kubernetesreadme.com/  UI / Desktop Clients  K9s — terminal UI for navigating clusters, resources, events, logs, and metrics https://k9scli.io/ Freelens — free and open-source IDE for Kubernetes (community fork of Lens, no account required) https://github.com/freelensapp/freelens Lens — full-featured Kubernetes desktop IDE with workload, metrics, and troubleshooting views https://k8slens.dev/ Headlamp — web-based Kubernetes UI, good for remote admin https://headlamp.dev/ Kubevious — maps cluster relationships and highlights configuration issues visually https://kubevious.</description>
    </item>
    
    <item>
      <title>AWS Lambda MicroVMs: stateful sandboxes with full lifecycle control</title>
      <link>https://okulbida.com/posts/aws-lambda-microvms-stateful-sandboxes/</link>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/aws-lambda-microvms-stateful-sandboxes/</guid>
      <description>AWS just shipped something that reframes what &amp;ldquo;serverless&amp;rdquo; can mean. Lambda MicroVMs are not Lambda Functions with a bigger timeout. They are a fundamentally different primitive: stateful, VM-level isolated environments with an explicit lifecycle you control.
The key shift: instead of getting a recycled process for 15 minutes, you get a dedicated Firecracker microVM that lives up to 8 hours. You decide when it starts, suspends, resumes, and terminates.
 What Lambda MicroVMs actually are Regular Lambda Functions are stateless by design.</description>
    </item>
    
    <item>
      <title>AI agents in practice: self-learning, knowledge bases, and why fewer agents is better</title>
      <link>https://okulbida.com/posts/ai-agents-knowledge-base-obsidian-local-llm/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/ai-agents-knowledge-base-obsidian-local-llm/</guid>
      <description>Building AI agents sounds fun until you actually build one. Then a different set of problems shows up — ones nobody writes about.
Here is what I have learned running agent systems in production: self-improvement conflicts with git, most knowledge bases hit a wall sooner than expected, and adding more agents almost never helps.
 The self-improvement problem One of the selling points of agents like Hermes is that they can self-reflect and improve, updating their own rules based on experience.</description>
    </item>
    
    <item>
      <title>Supply Chain Attacks in 2026: How to Harden Your Pipeline</title>
      <link>https://okulbida.com/posts/axios-npm-supply-chain-min-release-age/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/axios-npm-supply-chain-min-release-age/</guid>
      <description>npm min-release-age Use npm ci, not npm install Lock down npm with .npmrc Hardening GitHub Actions Summary   In late March 2026, compromised axios builds briefly appeared on the npm registry (for example 1.14.1 and 0.30.4 on affected release lines). Attackers added a malicious dependency and used lifecycle scripts so a plain npm install could pull down far more than an HTTP client. This is a pattern seen before in registry incidents, not a bug in axios’ normal code.</description>
    </item>
    
    <item>
      <title>Terraform at scale: GitOps tools and the long apply problem</title>
      <link>https://okulbida.com/posts/terraform-gitops-state-management-alternatives/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/terraform-gitops-state-management-alternatives/</guid>
      <description>If you&amp;rsquo;ve been using Terraform Cloud for a while, you&amp;rsquo;ve probably hit at least one of these: the pricing model changed and suddenly it&amp;rsquo;s expensive, applies take 10+ minutes, or the state files have grown into something nobody wants to touch. You&amp;rsquo;re not alone. This comes up a lot in Terraform discussions lately.
This post covers the main tools people are using to solve these problems in 2025–2026, with a focus on two separate issues that often get conflated: GitOps orchestration (who triggers plans, who approves applies) and state management at scale (why applies are slow and what to do about it).</description>
    </item>
    
    <item>
      <title>urllib3 2.4.0 &#43; Python 3.13 breaks SSL against Kubernetes: what you need to know</title>
      <link>https://okulbida.com/posts/eks-python-urllib3-ssl-certificate-verify-failed/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/eks-python-urllib3-ssl-certificate-verify-failed/</guid>
      <description>Bumped to Python 3.13 and suddenly your Kubernetes automation stopped working? Here&amp;rsquo;s the error you&amp;rsquo;re probably seeing:
1 2 3 4 5  urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host=&amp;#39;xxxx.gr7.us-east-1.eks.amazonaws.com&amp;#39;, port=443): Max retries exceeded with url: /version/ (Caused by SSLError(SSLCertVerificationError(1, &amp;#39;[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)&amp;#39;)))   Nothing changed on the cluster side. The problem is on your machine — specifically the combination of Python 3.13 and urllib3 2.4.0. Tracked in kubernetes-client/python#2394.</description>
    </item>
    
    <item>
      <title>Harden-Runner: visibility into what your CI runner does on the network</title>
      <link>https://okulbida.com/posts/harden-runner-github-actions-egress-monitoring/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/harden-runner-github-actions-egress-monitoring/</guid>
      <description>Most teams have no idea what their CI runners connect to during a build. Packages get installed, scripts run, network calls go out — and none of it is logged. That is a real blind spot.
Harden-Runner from StepSecurity is a GitHub Action that monitors and optionally blocks outbound network connections at the runner level, in real time. Think of it as an EDR for your CI pipeline.
It caught the axios supply chain attack in real time — any connection to sfrclak.</description>
    </item>
    
    <item>
      <title>PromQL cheat sheet</title>
      <link>https://okulbida.com/posts/prom-cheat-sheet/</link>
      <pubDate>Fri, 17 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/prom-cheat-sheet/</guid>
      <description>Key functions — rate, irate, increase, histogram_quantile, absent, absent_over_time, delta, predict_linear, age Aggregations — sum, count, topk, by/without, quantile_over_time, bool, offset Label manipulation — label_replace, label_join Useful queries — CPU %, pod restarts, error rate, SLO, memory, network by AZ, nodegroup, cardinality Relabeling tricks — drop metrics, series, labels Pre-commit validation — promtool, pint Architecture — agent mode, VictoriaMetrics, Thanos, Mimir Tools   Key functions rate vs irate</description>
    </item>
    
    <item>
      <title>AWS S3 Files: mount S3 bucket as file system</title>
      <link>https://okulbida.com/posts/aws-s3-files-mount-bucket-as-filesystem/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/aws-s3-files-mount-bucket-as-filesystem/</guid>
      <description>AWS quietly launched S3 Files - a way to mount an S3 bucket and work with it like a regular file system. No custom SDK, no aws s3 cp, just standard file operations on top of S3.
How it works You mount the bucket via a managed endpoint and get a POSIX-compatible interface on EC2, Lambda, EKS, and ECS. Your existing tools and applications don&amp;rsquo;t need to know it&amp;rsquo;s S3 underneath.</description>
    </item>
    
    <item>
      <title>Hardening Claude Code: permissions, hooks, and custom commands</title>
      <link>https://okulbida.com/posts/claude-code-hardening-permissions-hooks-commands/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/claude-code-hardening-permissions-hooks-commands/</guid>
      <description>Claude Code is a powerful local agent. By default it can read most files on your machine. Here is how to lock it down and extend it for your workflow.
 Block access to credential files Put this in your global Claude settings at ~/.claude/settings.json. Claude will refuse to read any of these paths — even if you accidentally ask it to.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20  { &amp;#34;permissions&amp;#34;: { &amp;#34;deny&amp;#34;: [ &amp;#34;Read(~/.</description>
    </item>
    
    <item>
      <title>GuardDuty, phishing URLs, and SSRF: what DNS alerts really mean</title>
      <link>https://okulbida.com/posts/guardduty-phishing-url-resolution-ssrf/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/guardduty-phishing-url-resolution-ssrf/</guid>
      <description>Click to enlarge      GuardDuty screams about a phishing domain. The node looks fine — no malware, no stolen creds. Often the real story is simpler: your app looked up a URL someone pasted in a message, and that hostname is on a threat list. The alert is still “true” (DNS to a bad name happened), but it&amp;rsquo;s not a hacked cluster.
The uncomfortable part: if you resolve or fetch any user URL with no checks, you also open the door to SSRF — for example a link to 169.</description>
    </item>
    
    <item>
      <title>Ingress-NGINX is retiring — here&#39;s how to migrate (and what to migrate to)</title>
      <link>https://okulbida.com/posts/ingress2gateway-1-0-migrating-from-ingress-nginx/</link>
      <pubDate>Wed, 25 Mar 2026 10:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/ingress2gateway-1-0-migrating-from-ingress-nginx/</guid>
      <description>If you&amp;rsquo;re running Ingress-NGINX in production, you&amp;rsquo;ve probably seen the writing on the wall. The retirement was announced back in November 2025, and as of March 2026, it&amp;rsquo;s happening. The Ingress API isn&amp;rsquo;t going away overnight, but active development on Ingress-NGINX is done. Time to move.
The good news: SIG Network just shipped Ingress2Gateway 1.0, a migration tool that actually works now.
What Changed in 1.0 Previous versions were barely usable — they supported only three Ingress-NGINX annotations.</description>
    </item>
    
    <item>
      <title>How container filesystem works: building one from scratch</title>
      <link>https://okulbida.com/posts/how-container-filesystem-works/</link>
      <pubDate>Thu, 12 Mar 2026 22:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/how-container-filesystem-works/</guid>
      <description>One of the superpowers of containers is their isolated filesystem view. From inside a container it looks like a full Linux distro, often different from the host. Run docker run nginx, and Nginx lands in its familiar Debian userspace no matter what Linux flavor your host runs. But how is that illusion built?
In this post, we&amp;rsquo;ll walk through how to assemble a tiny but realistic container using only stock Linux tools: unshare, mount, and pivot_root.</description>
    </item>
    
    <item>
      <title>The future of software engineering: key takeaways from Martin Fowler&#39;s retreat</title>
      <link>https://okulbida.com/posts/future-of-software-engineering-thoughtworks-2026/</link>
      <pubDate>Thu, 12 Mar 2026 21:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/future-of-software-engineering-thoughtworks-2026/</guid>
      <description>Martin Fowler published a fascinating report from a February 2026 retreat where senior engineering practitioners from major tech companies gathered to discuss how AI is reshaping software development. It&amp;rsquo;s dense, so here&amp;rsquo;s what stood out to me.
Where Does the Rigor Go? The biggest question of the retreat: if AI writes the code, where does the engineering discipline move? The answer is that it doesn&amp;rsquo;t disappear, it migrates:
 Upstream to specs: bad specs produce bad code at scale.</description>
    </item>
    
    <item>
      <title>16 GitHub repos every AI engineer should know in 2026</title>
      <link>https://okulbida.com/posts/ai-engineer-repos-2026/</link>
      <pubDate>Thu, 12 Mar 2026 20:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/ai-engineer-repos-2026/</guid>
      <description>If you&amp;rsquo;re building AI systems in production — or just getting started — these repos are worth bookmarking.
LLM Serving &amp;amp; Inference vLLM (66k+ stars) — The industry standard for high-throughput LLM serving. Continuous batching and maximum GPU utilization. If you&amp;rsquo;re serving LLMs in production, this is probably what you should be using.
Ollama (162k+ stars) — The easiest way to run LLMs locally. Great for fast experimentation before you commit to a cloud setup.</description>
    </item>
    
    <item>
      <title>AWS SQS: when a &#39;cheap&#39; queue runs up a huge bill</title>
      <link>https://okulbida.com/posts/aws-sqs-cost-surprises-short-polling/</link>
      <pubDate>Sun, 28 Dec 2025 20:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-sqs-cost-surprises-short-polling/</guid>
      <description>SQS is cheap until it isn’t. Real example from the wild: $500k in a weekend, and Amazon reportedly asked the team not to delete everything at once in certain regions, as it could impact the service. The usual culprit isn’t message volume; it’s how often you call ReceiveMessage when the queue is empty.
How SQS Billing Works  You pay per request (SendMessage, ReceiveMessage, DeleteMessage, etc.), not per message. Standard queue: about $0.</description>
    </item>
    
    <item>
      <title>AWS billing transfer</title>
      <link>https://okulbida.com/posts/aws-billing-transfer-session-summary/</link>
      <pubDate>Sun, 28 Dec 2025 18:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-billing-transfer-session-summary/</guid>
      <description>AWS Billing Transfer is a new feature (GA since November 2025) that lets you manage billing across multiple AWS Organizations from one account. It helps companies and channel partners who manage multiple Organizations by enabling centralized billing while keeping security and autonomy decentralized for business units or end customers.
Key Challenges Addressed  Multiple Organizations – Separate logins for billing and cost management across Organizations increase operational overhead No Central View – Hard to get a single, holistic view of spend across business units or customers Confidential Pricing – Protecting pricing data when billing and security roles are separated (e.</description>
    </item>
    
    <item>
      <title>VolSync: asynchronous data replication for Kubernetes volumes</title>
      <link>https://okulbida.com/posts/volsync-kubernetes-volume-migration/</link>
      <pubDate>Sun, 28 Dec 2025 16:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/volsync-kubernetes-volume-migration/</guid>
      <description>VolSync is a Kubernetes operator that asynchronously replicates persistent volumes between clusters using rsync or rclone. It also supports creating backups of persistent volumes via restic.
Installation:
Install VolSync via Helm:
1 2  helm repo add backube https://backube.github.io/helm-charts/ helm install --create-namespace -n volsync-system volsync backube/volsync   Migrating Data into Kubernetes:
VolSync provides a CLI tool (kubectl-volsync) for migrating data from external storage into Kubernetes PersistentVolumes.
Step 1: Install VolSync CLI</description>
    </item>
    
    <item>
      <title>Terraform best practices: code organization and structure</title>
      <link>https://okulbida.com/posts/terraform-code-organization-best-practices/</link>
      <pubDate>Sun, 28 Dec 2025 14:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/terraform-code-organization-best-practices/</guid>
      <description>Essential Terraform best practices for organizing and structuring your infrastructure code:
1. Separate Configuration Files
Instead of putting all code in main.tf, distribute it across multiple files:
 main.tf: Calls modules, locals, and data sources to create all resources variables.tf: Contains variable declarations used in main.tf. Place required variables at the top and optional ones at the bottom, separated by a comment line for better readability outputs.tf: Contains outputs from resources created in main.</description>
    </item>
    
    <item>
      <title>AWS Control Tower Landing Zone 4.0 is out! After 8 years of multi-account pain, we can FINALLY set up everything programmatically</title>
      <link>https://okulbida.com/posts/aws-control-tower-landing-zone-4.0/</link>
      <pubDate>Sat, 27 Dec 2025 13:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-control-tower-landing-zone-4.0/</guid>
      <description>AWS Control Tower Landing Zone 4.0 introduces a flexible Controls-Only experience, allowing full programmatic setup and customization of multi-account environments.
Key Changes:
Optional Service Integrations - Choose which integrations to enable:
 AWS Config AWS CloudTrail Security Roles AWS Backup  Dedicated Resources - Better isolation with separate resources per service:
 Separate S3 buckets for AWS Config and CloudTrail Individual SNS topics for each service  Flexible Organization Structure - Removed previous requirements:</description>
    </item>
    
    <item>
      <title>How GitHub engineers tackle platform problems</title>
      <link>https://okulbida.com/posts/github-platform-engineering-approaches/</link>
      <pubDate>Sat, 27 Dec 2025 00:30:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/github-platform-engineering-approaches/</guid>
      <description>GitHub&amp;rsquo;s platform engineering team on how they tackle infrastructure problems at scale:
Understanding your domain:
 Talk to neighboring teams with more experience Investigate old issues to understand system limitations Read documentation to build foundational knowledge  Platform-specific skills:
 Network fundamentals (TCP, UDP, L4 load balancing, debugging tools) Operating systems and hardware selection for scalability and cost Infrastructure as Code (Terraform, Ansible, Consul) Distributed systems understanding (failures are inevitable, need failover/recovery)  Impact radius considerations:</description>
    </item>
    
    <item>
      <title>ACM finally automates certificate management for Kubernetes</title>
      <link>https://okulbida.com/posts/acm-automated-certificate-management-kubernetes/</link>
      <pubDate>Sat, 27 Dec 2025 00:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/acm-automated-certificate-management-kubernetes/</guid>
      <description>AWS Certificate Manager (ACM) now supports automated certificate management for Kubernetes workloads through AWS Controllers for Kubernetes (ACK).
Previously, using ACM certificates in Kubernetes required manual steps: exporting certificates via API, creating Kubernetes Secrets, and manually updating them at renewal. With ACK, you can define certificates as Kubernetes resources, and the controller automates the complete lifecycle - requesting, exporting, creating Secrets, and auto-updating at renewal.
This works for both public certificates (ACM exportable certificates) and private certificates (AWS Private CA), enabling automated certificate management for:</description>
    </item>
    
    <item>
      <title>How Cloudflare secures Terraform state at scale</title>
      <link>https://okulbida.com/posts/cloudflare-terraform-state-security/</link>
      <pubDate>Tue, 23 Dec 2025 16:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/cloudflare-terraform-state-security/</guid>
      <description>Managing Terraform state securely is one of those things that seems simple until you&amp;rsquo;re dealing with hundreds of accounts and thousands of resources. Cloudflare, being their own Customer Zero, had to solve this problem at enterprise scale.
The interesting part? They built a custom solution called tfstate-butler - a Go program that acts as an HTTP backend for Terraform state storage.
The Security Problem When you&amp;rsquo;re managing infrastructure at Cloudflare&amp;rsquo;s scale, a single compromised state file could be catastrophic.</description>
    </item>
    
    <item>
      <title>AWS in 2025: things you think you know that are actually wrong</title>
      <link>https://okulbida.com/posts/aws-2025-things-you-think-you-know/</link>
      <pubDate>Tue, 23 Dec 2025 14:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-2025-things-you-think-you-know/</guid>
      <description>You know what&amp;rsquo;s wild? AWS is almost twenty years old now. That&amp;rsquo;s both cool and kind of terrifying at the same time. I&amp;rsquo;ve been working with AWS for a while, and honestly, I still catch myself thinking about things the way they used to be, not how they actually work today.
The problem is that AWS changes constantly, but a lot of the foundational stuff has evolved in ways that aren&amp;rsquo;t super obvious.</description>
    </item>
    
    <item>
      <title>AWS re:Invent 2025 recap: key announcements for cloud practitioners</title>
      <link>https://okulbida.com/posts/aws-reinvent-2025-recap/</link>
      <pubDate>Tue, 23 Dec 2025 10:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-reinvent-2025-recap/</guid>
      <description>Another year, another AWS re:Invent has come and gone. I&amp;rsquo;ve been following the announcements closely, and there&amp;rsquo;s a lot to cover.
The Big Picture This year&amp;rsquo;s re:Invent felt a bit different. The pre:Invent announcements started later than usual (mid-November instead of early October), and the keynote felt more focused on GenAI than infrastructure improvements. That said, there are still plenty of practical enhancements that can make our lives easier.
Security Features That Matter AWS Security Agent (Preview) This one caught my attention.</description>
    </item>
    
    <item>
      <title>AWS finally built a browser for S3 (and why it took 20 years)</title>
      <link>https://okulbida.com/posts/aws-s3-storage-browser-access-grants/</link>
      <pubDate>Wed, 20 Nov 2024 18:00:00 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-s3-storage-browser-access-grants/</guid>
      <description>It&amp;rsquo;s 2024, and AWS finally built a browser-based S3 viewer. Twenty years after S3 launched, you can now browse your buckets directly in the browser. It&amp;rsquo;s still in alpha, but hey, better late than never, right?
You might be thinking - wait, weren&amp;rsquo;t there options before? Like S3Fox? Yeah, there were some third-party tools, but AWS itself never had an official browser interface. So what took so long?
Real Problem: Access Control Turns out, building a simple file browser wasn&amp;rsquo;t the hard part.</description>
    </item>
    
    <item>
      <title>12 Factors vs kubernetes world</title>
      <link>https://okulbida.com/posts/12-factors/</link>
      <pubDate>Wed, 08 May 2024 14:37:18 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/12-factors/</guid>
      <description>Disclaimer: here you might not find something new if you know 12 factors app.
The 12-factor app methodology 12factor.net, is a set of principles designed to enable applications to be built with portability and resilience when deployed to the web. These principles focus on declarative formats for automation, clean contracts with the operating system, and suitability for deployment on modern cloud platforms, thus minimizing divergence between development and production, enabling continuous deployment for maximum agility.</description>
    </item>
    
    <item>
      <title>AWS vs Elasticsearch licensing</title>
      <link>https://okulbida.com/posts/aws-elasticsearch-licensing/</link>
      <pubDate>Sun, 21 Apr 2024 21:25:08 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-elasticsearch-licensing/</guid>
      <description>Recent elasticsearch licensing change ensures that the Beats modules are sending data to an officially supported versions of Elasticsearch and Kibana where Elastic can attest to the quality and scale of the products. Does AWS have any plans to fork a version filebeat?
https://www.elastic.co/guide/en/beats/libbeat/current/breaking-changes-7.13.html
https://www.reddit.com/r/aws/comments/nn95aq/elastic_has_broken_filebeat_as_of_713_it_no/
What are the alternatives?
 Host elasticsearch on EC2 instances, why not? CloudWatch, slow&amp;hellip; https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_ES_Stream.html Kubernetes options like ECK or helm chart deployments&amp;hellip;tricky for production usage Loki?</description>
    </item>
    
    <item>
      <title>k8s 1.30 version</title>
      <link>https://okulbida.com/posts/k8s-130-version/</link>
      <pubDate>Sun, 21 Apr 2024 14:42:59 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/k8s-130-version/</guid>
      <description>Reasons to upgrade to k8s 1.30 Container resource based autoscaling Container resource based autoscaling is now promoted to stable https://github.com/kubernetes/enhancements/issues/1610 Horizontal Pod Autoscaler examines the total resource usage of the entire pod i.e. sum of all containers and scale pods based on average CPU or memory usage. Container resource based autoscaling feature allows HPA to scale workloads based on the resource usage of individual containers within a pod, instead of the aggregated usage of all containers in the pod</description>
    </item>
    
    <item>
      <title>k8s InPlacePodVerticalScaling</title>
      <link>https://okulbida.com/posts/k8s-new-features/</link>
      <pubDate>Sat, 20 Apr 2024 23:25:05 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/k8s-new-features/</guid>
      <description>Kubernetes InPlacePodVerticalScaling feature
Kubernetes v1.27 introduces InPlacePodVerticalScaling, allowing pod resource resizing without restarts
This eliminates the downtime and potential data loss caused by pod restarts. It also helps avoid overprovisioning, since InPlacePodVerticalScaling lets you allocate resources precisely as needed
In this example for pod memory resources configuration, the resizePolicy indicates that changes to the memory allocation require a restart of the container, and for CPU resources the restart is not necessary during resizing.</description>
    </item>
    
    <item>
      <title>Terraform best practices</title>
      <link>https://okulbida.com/posts/terraform-best-practices/</link>
      <pubDate>Sat, 23 Mar 2024 19:11:15 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/terraform-best-practices/</guid>
      <description>Collaboration  Use remote state and state locking  For certain backends like AWS S3, enable versioning to make it easier to recover your state if needed   Agree on naming convention Use meaningful tags to easily identify resources: environment, owner, project keys are must  You can also add cloud-custdodian for components which are out of terrarfom/IaC tools, which could automatically tag your manually created resources with Owner Creator based on CloudTrail events    Don&amp;rsquo;t reinvent the wheel Use existing shared and community modules.</description>
    </item>
    
    <item>
      <title>EKS with instance-store nitro-based node-group</title>
      <link>https://okulbida.com/posts/eks-instance-store/</link>
      <pubDate>Sat, 16 Mar 2024 17:00:51 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/eks-instance-store/</guid>
      <description>Userdata is compatible with the standard AWS EKS Terraform module, the only recommendation is to use a custom AMI. To use instance-store you also need to install local-static-provisioner - https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner
Terraform example:
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 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94  eks-dev-instance-store = { instance_types = [&amp;#34;r6id.</description>
    </item>
    
    <item>
      <title>Simple RDS access</title>
      <link>https://okulbida.com/posts/simple-rds-access/</link>
      <pubDate>Sat, 23 Dec 2023 16:37:19 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/simple-rds-access/</guid>
      <description>There are plenty of ways to access private RDS instances, and most need careful design. The one I use sometimes is simple: deploy it as a Helm chart inside a k8s cluster. Access to the RDS then depends on having access to the k8s cluster with the right RBAC. It&amp;rsquo;s not perfect, but it&amp;rsquo;s secure, quick to set up, and needs almost no maintenance. Here&amp;rsquo;s the basic idea:
1  socat TCP4-LISTEN:8888,fork TCP4:xxxxxxxx.</description>
    </item>
    
    <item>
      <title>Resolving Helm issues after kubernetes upgrade</title>
      <link>https://okulbida.com/posts/helm-fix-after-k8s-upgrade/</link>
      <pubDate>Sat, 23 Dec 2023 16:27:22 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/helm-fix-after-k8s-upgrade/</guid>
      <description>After upgrading Kubernetes (k8s), you might encounter errors such as no matches for kind &amp;quot;Deployment&amp;quot; in version &amp;quot;apps/v1beta1&amp;quot;. These errors typically indicate that certain resources have become deprecated. To resolve these issues without the need to delete your Helm chart, you can follow this simple solution:
1 2 3  helm plugin install https://github.com/helm/helm-mapkubeapis helm mapkubeapis &amp;lt;releasename&amp;gt; helm upgrade &amp;lt;releasename&amp;gt;   You may still need to update your Helm chart templates, especially if there have been structural changes between versions.</description>
    </item>
    
    <item>
      <title>EKS expose pods through cross-account load balancer</title>
      <link>https://okulbida.com/posts/eks-expose-pods-through-cross-account-lb/</link>
      <pubDate>Sat, 23 Dec 2023 15:44:19 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/eks-expose-pods-through-cross-account-lb/</guid>
      <description>Expose Amazon EKS pods through cross-account load balancer
 https://aws.amazon.com/blogs/containers/expose-amazon-eks-pods-through-cross-account-load-balancer/  </description>
    </item>
    
    <item>
      <title>EKS simplified access</title>
      <link>https://okulbida.com/posts/eks-access/</link>
      <pubDate>Sat, 23 Dec 2023 15:40:22 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/eks-access/</guid>
      <description>Simplified EKS access
 https://aws.amazon.com/about-aws/whats-new/2023/12/amazon-eks-controls-iam-cluster-access-management/ https://aws.amazon.com/blogs/containers/a-deep-dive-into-simplified-amazon-eks-access-management-controls/ https://github.com/hashicorp/terraform-provider-aws/issues/34982  </description>
    </item>
    
    <item>
      <title>Loki S3 dynamodb</title>
      <link>https://okulbida.com/posts/loki-s3-dynamodb/</link>
      <pubDate>Wed, 26 Oct 2022 12:45:36 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/loki-s3-dynamodb/</guid>
      <description>While using Loki with S3 and Dynamodb it&amp;rsquo;s mandatory to add provision_config details as default might affect your budget https://grafana.com/docs/loki/latest/configuration/#provision_config
1 2 3 4 5  [provisioned_write_throughput: &amp;lt;int&amp;gt; | default = 3000] # DynamoDB table default read throughput. # CLI flag: -&amp;lt;prefix&amp;gt;.read-throughput [provisioned_read_throughput: &amp;lt;int&amp;gt; | default = 300]   </description>
    </item>
    
    <item>
      <title>k8s security best practices</title>
      <link>https://okulbida.com/posts/k8s-security-best-practices/</link>
      <pubDate>Sun, 07 Aug 2022 01:04:09 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/k8s-security-best-practices/</guid>
      <description>Keep the cloud provider platform secure
 Least privilege Secure traffic into cluster    Run security test in development environments
 Mirror environments    Cluster authentication &amp;amp; authorization
 Leverage OIDC for k8s authentication RBAC - define roles    In cluster network/security/micro segmentation
 Prevent namespace-to-namespace communication Network policy    Policy &amp;amp; Governance
  k8s admission controllers
 Read only Non-privileges ports    Runtime security &amp;amp; monitoring</description>
    </item>
    
    <item>
      <title>Bigdata comparison within AWS,Azure,GCP</title>
      <link>https://okulbida.com/posts/bigdata-comparison-cloudproviders/</link>
      <pubDate>Wed, 21 Jul 2021 00:13:41 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/bigdata-comparison-cloudproviders/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Database comparison within AWS,Azure,GCP</title>
      <link>https://okulbida.com/posts/db-cloudproviders/</link>
      <pubDate>Wed, 21 Jul 2021 00:12:44 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/db-cloudproviders/</guid>
      <description></description>
    </item>
    
    <item>
      <title>AWS removes NAT Gateway’s dependence on Internet Gateway for private communications</title>
      <link>https://okulbida.com/posts/aws-nat-gateway-no-need-igw/</link>
      <pubDate>Thu, 17 Jun 2021 12:15:17 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-nat-gateway-no-need-igw/</guid>
      <description>You can now launch NAT Gateways in your VPC without associating an internet gateway to your VPC. Internet Gateway is required to provide internet access to the NAT Gateway. However, some customers use their NAT Gateways with Transit Gateway or virtual private gateway to communicate privately with other VPCs or on-premises environments and thus, do not need an internet gateway attached to their VPCs.
More details: https://aws.amazon.com/about-aws/whats-new/2021/06/aws-removes-nat-gateways-dependence-on-internet-gateway-for-private-communications/</description>
    </item>
    
    <item>
      <title>What’s new in Grafana v8.0</title>
      <link>https://okulbida.com/posts/grafana-8-released/</link>
      <pubDate>Tue, 08 Jun 2021 23:09:58 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/grafana-8-released/</guid>
      <description>What’s new in Grafana v8.0
  Grafana includes built-in support for Prometheus Alertmanager. Once you add it as a data source, you can use the Grafana alerting UI to manage silences, contact points as well as notification policies. A drop down option in these pages allows you to switch between Grafana and any configured Alertmanager data sources. https://grafana.com/docs/grafana/latest/datasources/alertmanager/
  Prometheus metrics browser https://grafana.com/docs/grafana/latest/datasources/prometheus/#metrics-browser
  More details: https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v8-0/</description>
    </item>
    
    <item>
      <title>AWS Load Balancer Controller version 2.2 now available with support for NLB instance targeting</title>
      <link>https://okulbida.com/posts/aws-lb-controller-nlb-support/</link>
      <pubDate>Mon, 24 May 2021 16:16:34 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-lb-controller-nlb-support/</guid>
      <description>https://aws.amazon.com/about-aws/whats-new/2021/05/aws-load-balancer-controller-version-2-2-available-support-nlb-instance/</description>
    </item>
    
    <item>
      <title>Amazon EC2 Auto Scaling introduces predictive scaling as a native scaling policy</title>
      <link>https://okulbida.com/posts/aws-ec2-predictive-autoscaling/</link>
      <pubDate>Mon, 24 May 2021 16:14:25 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-ec2-predictive-autoscaling/</guid>
      <description>Amazon EC2 Auto Scaling now natively supports Predictive Scaling so you can proactively scale out your Auto Scaling group to be ready for upcoming demand. Predictive Scaling can help you avoid the need to over-provision capacity, resulting in lower EC2 cost, while ensuring your application’s responsiveness. (Previously, Predictive Scaling was only available via AWS Auto Scaling Plans.)
https://aws.amazon.com/about-aws/whats-new/2021/05/amazon-ec2-auto-scaling-introduces-predictive-scaling-native-scaling-policy/</description>
    </item>
    
    <item>
      <title>EKS add-ons now supports CoreDNS and kube-proxy</title>
      <link>https://okulbida.com/posts/awsekscoredns/</link>
      <pubDate>Mon, 24 May 2021 16:05:58 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/awsekscoredns/</guid>
      <description>Amazon Elastic Kubernetes Service (Amazon EKS) now supports using the Amazon EKS console, CLI, and API to install and manage CoreDNS and kube-proxy in addition to existing support for the Amazon VPC CNI networking plugin.
https://aws.amazon.com/about-aws/whats-new/2021/05/eks-add-ons-now-support-coredns-kube-proxy/
https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html</description>
    </item>
    
    <item>
      <title>Kubecon2021</title>
      <link>https://okulbida.com/posts/kubecon2021/</link>
      <pubDate>Sat, 15 May 2021 23:45:23 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/kubecon2021/</guid>
      <description>Full list of videos from KubeCon 2021 Europe
https://www.youtube.com/playlist?list=PLj6h78yzYM2MqBm19mRz9SYLsw4kfQBrC</description>
    </item>
    
    <item>
      <title>AWS CloudFront functions</title>
      <link>https://okulbida.com/posts/aws-cloudfront-functions/</link>
      <pubDate>Fri, 07 May 2021 01:09:56 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-cloudfront-functions/</guid>
      <description>AWS CloudFront functions is a nice alternative to Lambda@Edge
https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/</description>
    </item>
    
    <item>
      <title>EC2 root volume replacing</title>
      <link>https://okulbida.com/posts/ec2-root-volume-replacing/</link>
      <pubDate>Fri, 30 Apr 2021 11:44:11 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/ec2-root-volume-replacing/</guid>
      <description>Amazon EC2 enables you to replace the root EBS volume for a running instance
Limitations:  You can&amp;rsquo;t replace the root volume if it is an instance store volume. You can&amp;rsquo;t replace the root volume for metal instances.  More details: https://aws.amazon.com/about-aws/whats-new/2021/04/ec2-enables-replacing-root-volumes-for-quick-restoration-and-troubleshooting/
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html#replace-root</description>
    </item>
    
    <item>
      <title>AWS Secrets CSI for EKS</title>
      <link>https://okulbida.com/posts/aws-secrets-csi/</link>
      <pubDate>Tue, 27 Apr 2021 19:11:13 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/aws-secrets-csi/</guid>
      <description>How to use AWS Secrets &amp;amp; Configuration Provider with your Kubernetes Secrets Store CSI driver. One more example of kubernetes secrets management among vault, external-secrets and 1password operator 😅
https://aws.amazon.com/blogs/security/how-to-use-aws-secrets-configuration-provider-with-kubernetes-secrets-store-csi-driver/</description>
    </item>
    
    <item>
      <title>Grafana license</title>
      <link>https://okulbida.com/posts/grafana-license/</link>
      <pubDate>Tue, 27 Apr 2021 11:11:59 +0300</pubDate>
      
      <guid>https://okulbida.com/posts/grafana-license/</guid>
      <description>Grafana was relicensed to AGPLv3
https://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/</description>
    </item>
    
    <item>
      <title></title>
      <link>https://okulbida.com/categories/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://okulbida.com/categories/</guid>
      <description></description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://okulbida.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://okulbida.com/about/</guid>
      <description>about</description>
    </item>
    
    <item>
      <title>Archive</title>
      <link>https://okulbida.com/archive/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://okulbida.com/archive/</guid>
      <description>archive</description>
    </item>
    
    <item>
      <title>Search</title>
      <link>https://okulbida.com/search/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://okulbida.com/search/</guid>
      <description>search</description>
    </item>
    
  </channel>
</rss>
