<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>gitops on ashikov.ru</title><link>https://ashikov.ru/en/tags/gitops/</link><description>Recent content in gitops on ashikov.ru</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ashikov.ru/en/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Preserve Engineering Knowledge from Tickets and Chats</title><link>https://ashikov.ru/en/notes/preserve-knowledge-from-tickets-and-chats/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/preserve-knowledge-from-tickets-and-chats/</guid><description>How to turn ticket histories and chat discussions into documentation, checks, and automation that engineers can reuse.</description></item><item><title>A Ready Node Can Still Drift from Its Baseline</title><link>https://ashikov.ru/en/notes/kubernetes-node-configuration-drift/</link><pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/kubernetes-node-configuration-drift/</guid><description>A practical case where Kubernetes reported healthy nodes while their actual kubelet configuration differed from the GitOps baseline.</description></item></channel></rss>