<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Cloudowski DevOps Expert</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/tags/containers/</link><description>Recent content in Containers on Cloudowski DevOps Expert</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://63db89d1.hugo-coudowski-website.pages.dev/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>From CI/CD to CI&amp;CD: A Modern Deployment Strategy with GitOps</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/from-cicd-to-ci-and-cd-a-modern-deployment-with-gitops/</link><pubDate>Mon, 10 Mar 2025 00:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/from-cicd-to-ci-and-cd-a-modern-deployment-with-gitops/</guid><description>&lt;p>Continuous Integration and Continuous Delivery (CI/CD) has become an indispensable cornerstone of modern software development, enabling teams to automate the build, test, and deployment processes. However, the traditional CI/CD pipeline, where a single system orchestrates both building and deploying, can become a bottleneck, especially in complex, cloud-native environments. This article examines the limitations of this monolithic approach and introduces a more robust and scalable alternative: separating the CI process from the CD process and leveraging GitOps principles. We&amp;rsquo;ll delve into the benefits of this evolved strategy, including improved resource utilization, enhanced rollback capabilities, a declarative approach that aligns with modern infrastructure, and enhanced security.&lt;/p></description></item><item><title>Premiera kursu “Kontenery po polsku”</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/pl/dlaczego-utworzylem-bezplatny-kurs-kontenery-po-polsku/</link><pubDate>Tue, 20 Feb 2024 06:30:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/pl/dlaczego-utworzylem-bezplatny-kurs-kontenery-po-polsku/</guid><description>&lt;p>W końcu mogę to ogłosić - właśnie publikuję mój nowy kurs &lt;strong>“Kontenery po polsku” 🎉&lt;/strong>&lt;br>
To kolejny po &lt;a href="https://kubernetespopolsku.pl/">“Kubernetes po polsku”&lt;/a> kurs wideo, ale tym razem zupełnie &lt;strong>bezpłatny&lt;/strong>.&lt;br>
Jest to kurs dostępny online dla wszystkich, którzy chcą porządnie poznać kontenery. Specjalnie kurs nazwałem “Kontenery po polsku”, a nie “Docker po polsku”, ponieważ mój kurs pomaga zrozumieć koncepty działania i wykorzystywania kontenerów.&lt;/p></description></item><item><title>Newsletter #88 - Renesans środowisk on-prem</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/88/</link><pubDate>Tue, 21 Nov 2023 09:11:02 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/88/</guid><description>&lt;p>Na początku mam dwa ogłoszenia, a w dalszej części dzielę się spostrzeżeniami dotyczącymi budowy środowisk na on-prem.&lt;/p>
&lt;h3 id="ogłoszenie-1---nowy-odcinek-podcastu">Ogłoszenie 1 - nowy odcinek podcastu&lt;/h3>
&lt;p>Po dłuższej przerwie wracam do nagrywania podcastu. Tym razem usiadłem sam ze sobą i nagrałem odcinek, w którym opowiadam jak tworzyłem mój kurs Kubernetes po polsku i czego się z tego nauczyłem.&lt;/p></description></item><item><title>Newsletter #87 - Jak aktualizować klastry?</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/87/</link><pubDate>Tue, 14 Nov 2023 09:07:19 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/87/</guid><description>&lt;p>Łatwo jest postawić wiele klastrów z Kubernetesem, zapuścić kilka manifestów, dograć Helm Charty i odtrąbić sukces.&lt;br>
W codziennym, szarym życiu liczy się bardziej to co dzieje się później. W użytkowaniu platformy bardzo duży wpływ ma dostępność nowych wersji Kubernetesa oraz łatanie dziur i podatności. To jak obsługiwana jest platforma dla aplikacji jest widoczne bardziej dla organizacji i jej klientów niż jakieś nowinki technologiczne.&lt;br>
Tym razem przyjrzę się tematowi aktualizacji klastrów.&lt;/p></description></item><item><title>Newsletter #86 - Ile klastrów tak naprawdę potrzebujesz?</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/86/</link><pubDate>Tue, 07 Nov 2023 08:58:54 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/86/</guid><description>&lt;p>Ile klastrów Kubernetesa to za mało, a ile za dużo? To pewnie zależy pod zastosowań, wielkości organizacji, jej struktury, polityki i wielu innych czynników.&lt;br>
Ja postanowiłem tym razem przyjrzeć się bliżej temu tematowi i pomóc Ci w odpowiednim wyborze przy projektowaniu lub rozbudowie Twojego środowiska.&lt;/p></description></item><item><title>Newsletter #85 - Zmiany, zmiany, zmiany</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/85/</link><pubDate>Tue, 31 Oct 2023 08:58:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/85/</guid><description>&lt;p>No i koniec tego dobrego - wracam z nowymi siłami i energią do pracy.&lt;br>
Miałem trochę czasu na przemyślenie kilku ważnych dla mnie rzeczy czego efektem są poważne zmiany. O nich dzisiaj chcę Ci opowiedzieć.&lt;/p></description></item><item><title>Newsletter #83 - Jak HashiCorp namieszał z Terraform</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/83/</link><pubDate>Tue, 29 Aug 2023 07:58:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/83/</guid><description>&lt;p>Ale się porobiło! Może nie jest to pierwszy, ani ostatni raz, ale HashiCorp sporo namieszał swoją ostatnią decyzję o zmianie licencji dla projektu Terraform.&lt;br>
Przyjrzyjmy się temu bliżej, bo to może mieć duży wpływ na to jak będziemy w przyszłości zarządzać naszymi środowiskami.&lt;/p></description></item><item><title>Newsletter #81 - Skończyłem</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/81/</link><pubDate>Tue, 08 Aug 2023 07:54:42 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/newsletter-archive/81/</guid><description>&lt;p>W końcu. To już koniec. Udało się.&lt;br>
Po niemalże pół roku od rozpoczęcia przedsprzedaży ukończyć w całości kurs “Kubernetes po polsku”.&lt;br>
W środę tydzień temu opublikowałem część PRO dla szczęśliwców, którzy mi zaufali i kupili go w przedsprzedaży. Inni będą mogli do nich dołączyć już &lt;strong>6 września&lt;/strong> podczas jego oficjalnej premiery.&lt;br>
A dzisiaj podzielę się kilka spostrzeżeniami po pół roku pracy nad kursem.&lt;/p></description></item><item><title>A recipe for a bespoke on-prem Kubernetes cluster</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/a-recipe-for-a-bespoke-on-prem-kubernetes-cluster/</link><pubDate>Thu, 08 Apr 2021 11:46:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/a-recipe-for-a-bespoke-on-prem-kubernetes-cluster/</guid><description>&lt;p>So you want to build yourself a Kubernetes cluster? You have your reasons. Some may want to utilize the hardware they own, some may not fully trust these fancy cloud services or just simply want to have a choice and build themselves a hybrid solution.
There are a couple of products available that I’ve &lt;a href="https://63db89d1.hugo-coudowski-website.pages.dev/articles/which-kubernetes-for-on-prem/">reviewed&lt;/a>, but you’ve decided to build a platform from scratch. And again, there are a myriad of reasons why it might be a good idea and also many that would convince you it’s not worth your precious time. In this article, I will focus on providing a list of things to consider when starting a project building a Kubernetes-based platform using only the most popular open source components.&lt;/p></description></item><item><title>Which Kubernetes distribution to choose for on-prem environments?</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/which-kubernetes-distribution-to-choose-for-on-prem-environments/</link><pubDate>Sat, 30 Jan 2021 12:47:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/which-kubernetes-distribution-to-choose-for-on-prem-environments/</guid><description>&lt;p>Most people think that Kubernetes was designed to bring more features and more abstraction layers to cloud
environments. Well, I think the biggest benefits can be achieved in on-premise environments, because of the big gap
between those environments and the ones that can be easily created in the cloud. This opens up many excellent
opportunities for organizations which for some reasons choose to stay outside of the public cloud.
In order to leverage Kubernetes using on-premise hardware, one of the biggest decisions that needs to be made which
software platform to use for Kubernetes. According to the &lt;a href="https://kubernetes.io/partners/#conformance">official&lt;/a> listing of available Kubernetes distributions,
there are dozens of options available. If you look closely at them, however, there are only a few viable ones, as
many of them are either inactive or have been merged with other projects (e.g. Pivotal Kubernetes Service merged
with VMware Tanzu). I expect that 3-5 of these distributions will eventually prevail in the next 2 years and they
will target their own niche market segments.
Let’s have a look at those that have stayed in the game and can be used as a foundation for a highly automated
on-premise platform.&lt;/p></description></item><item><title>How to modify containers without rebuilding their image</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-modify-containers-without-rebuilding-their-image/</link><pubDate>Sat, 26 Sep 2020 11:47:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-modify-containers-without-rebuilding-their-image/</guid><description>&lt;p>Containers are a beautiful piece of technology that ease the development of modern applications and also the maintenance of modern environments. One thing that draws many people to them is how they reduce the time required to set up a service, or a whole environment, with everything included. It is possible mainly because there are so many container images available and ready to use. You will probably need to build your own container images with your applications, but many containers in your environment will use prebuilt images prepared by someone else. It’s especially worth considering for software that is provided by the software vendor or a trusted group of developers like it has been done in the case of “official” images published on Docker Hub. In both cases, it makes your life easier by letting someone else take care of updates, packaging new versions, and making sure it works.
But what if you want to change something in those images? Maybe it’s a minor change or something bigger that is specific for your particular usage of the service. The first instinct may tell you to rebuild that image. This, however, brings some overhead - these images will have to be published, rebuilt when new upstream versions are published, and you lose most of the benefits that come with those prebuilt versions.
There is an alternative to that - actually, I found four of them which I will describe below. These solutions will allow you to keep all the benefits and adjust the behaviour of running containers in a seamless way.&lt;/p></description></item><item><title>4 ways to manage Kubernetes resources</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/4-ways-to-manage-kubernetes-resources/</link><pubDate>Sat, 14 Mar 2020 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/4-ways-to-manage-kubernetes-resources/</guid><description>&lt;h2 id="kubectl-is-the-new-ssh">Kubectl is the new ssh&lt;/h2>
&lt;p>When I started my adventure with linux systems the first tool I had to get to know was ssh. Oh man, what a wonderful and powerful piece of software it is! You can not only log in to your servers, copy files, but also create vpns, omit firewalls with SOCKS proxy and port-forwarding rules, and many more. With Kubernetes, however, this tool is used mostly for node maintenance provided that you still need to manage them and you haven’t switched to CoreOS or another variant of the immutable node type. For any other cases, you use &lt;em>kubectl&lt;/em> which is the new ssh. If you don’t use API calls directly then you probably use it in some form and you feed it with plenty of yaml files. Let’s face it - this is how managing Kubernetes environment looks like nowadays. You create those beautiful, lengthy text files with the definitions of the resources you wish to be created by Kubernetes and then magic happens and you’re the hero of the day. Unless you want to create not one but tens or hundreds of them with different configurations. And that’s when things get complicated.&lt;/p></description></item><item><title>How to build CI/CD pipelines on Kubernetes</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-build-cicd-pipelines-on-kubernetes/</link><pubDate>Wed, 23 Oct 2019 20:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-build-cicd-pipelines-on-kubernetes/</guid><description>&lt;h2 id="kubernetes-as-a-standard-development-platform">Kubernetes as a standard development platform&lt;/h2>
&lt;p>We started with single, often powerful, machines that hosted many applications. Soon after came virtualization, which didn’t actually change a lot from a development perspective but it did for the field of operations. So developers became mad, and that’s when the public cloud emerged to satisfy their needs instead of operations guys’. Now, this pendulum has moved once again and we have something that is beneficial for both sides - Kubernetes platform. I keep saying and will repeat it here again - I think it’s one of the best projects that have emerged in the last decade. It has completely changed the perspective of how we deliver applications and also how we manage platforms for them.
This time I want to focus on the delivery process and how it can be built and what the real benefits of using Kubernetes for that purpose are.&lt;/p></description></item><item><title>Maintaining big Kubernetes environments with factories</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/maintaining-big-kubernetes-environments-with-factories/</link><pubDate>Sun, 21 Jul 2019 20:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/maintaining-big-kubernetes-environments-with-factories/</guid><description>&lt;p>People are fascinated by containers, Kubernetes and cloud native approach for different reasons. It could be enhanced security, real portability, greater extensibility or more resilience. For me personally, and for organizations delivering software products for their customers, there is one reason that is far more important - it’s the speed they can gain. That leads straight to decreased Time To Market, so highly appreciated and coveted by the business people, and even more job satisfaction for guys building application and platforms for them.&lt;/p></description></item><item><title>How to increase container security with proper images</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-increase-container-security-with-proper-images/</link><pubDate>Sun, 26 May 2019 20:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/how-to-increase-container-security-with-proper-images/</guid><description>&lt;p>Security is a major factor when it comes to a decision of whether to invest your precious time and resources in new technology. It’s no different for containers and Kubernetes. I’ve heard a lot of concerns around it and decided to write about the most important factors that have the biggest impact on the security of systems based on containers running on Kubernetes.&lt;br>
This is particularly important, as it’s often the only impediment blocking potential implementation of container-based environment and also taking away chances for speeding up innovation. That’s when I decided to help all of you who wants strengthen security of their containers images.&lt;/p></description></item><item><title>Three levels of highly available apps on Kubernetes</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/three-levels-of-highly-available-apps-on-kubernetes/</link><pubDate>Mon, 21 Jan 2019 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/three-levels-of-highly-available-apps-on-kubernetes/</guid><description>&lt;h2 id="beautiful-but-useless-systems">Beautiful but useless systems&lt;/h2>
&lt;p>Hundreds of applications, thousands of users and millions of requests - that is often a landscape of a modern IT environment. However, problems are still the same.&lt;/p></description></item><item><title>Why managing container images on OpenShift is better than on Kubernetes</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/why-managing-container-images-on-openshift-is-better-than-on-kubernetes/</link><pubDate>Sat, 15 Sep 2018 20:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/why-managing-container-images-on-openshift-is-better-than-on-kubernetes/</guid><description>So you’ve decided to go with Kubernetes and started building your container images. Now the question is where to push them and how to manage them properly?</description></item><item><title>Myths around containers. Part 3: Speed</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-3-speed/</link><pubDate>Thu, 22 Feb 2018 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-3-speed/</guid><description>Containers are considerably faster than virtual machines - at least that’s what most people say. But do they actually bring more speed to overall development and deployment process? Let’s find out in the third part of my article series.</description></item><item><title>Myths around containers. Part 2: Portability</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-2-portability/</link><pubDate>Sun, 28 Jan 2018 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-2-portability/</guid><description>Is it true that after so many years we finally have real, portable format for all applications? It seems that we’ve come very close to that goal and it’s time to find out more about portability that comes with container revolution.</description></item><item><title>Myths around containers. Part 1: Security</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-1-security/</link><pubDate>Sun, 07 Jan 2018 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/myths-around-containers-part-1-security/</guid><description>We had many revolutions in IT infrastructure world over past 20 years or so. Virtualization promised hardware abstraction, private cloud promised lower costs and flexibility and containers keep adding more to that pile creating a vision of perfect world.</description></item><item><title>10 reasons why Kubernetes has won</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/why-kubernetes-has-won/</link><pubDate>Sat, 16 Dec 2017 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/why-kubernetes-has-won/</guid><description>We’ve been falling for the containers hype for the past few months and Kubernetes has emerged as a leader among container orchestrator to help build solutions on a bigger scale than your own laptop.
Here are 10 reason why it’s won the war and become first choice for container orchestrator.</description></item></channel></rss>