<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GCP on Ely Clover</title><link>https://stg.elyclover.com/categories/gcp/</link><description>Recent content in GCP on Ely Clover</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>kevin@elyclover.com (Kevin Holmes)</managingEditor><webMaster>kevin@elyclover.com (Kevin Holmes)</webMaster><copyright>© 2026 Kevin Holmes</copyright><lastBuildDate>Tue, 08 Aug 2023 10:00:00 +0000</lastBuildDate><atom:link href="https://stg.elyclover.com/categories/gcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Artifact Registry is replacing Container Registry</title><link>https://stg.elyclover.com/posts/gcr-to-gar-transition/</link><pubDate>Tue, 08 Aug 2023 10:00:00 +0000</pubDate><author>kevin@elyclover.com (Kevin Holmes)</author><guid>https://stg.elyclover.com/posts/gcr-to-gar-transition/</guid><description>&lt;p&gt;You may have seen the warnings in your Google Console recently: the Google Container Registry (GCR) product will be deprecated in May of 2023 in favor of &lt;a href="https://cloud.google.com/artifact-registry" target="_blank" rel="noreferrer"&gt;Google Artifact Registry&lt;/a&gt; (GAR.)&lt;/p&gt;
&lt;p&gt;Whenever I see these kinds of warnings as an engineer on a DevOps, Infrastructure, or Platform team (how many ways can we be classified?!), my heart tends to drop into my stomach a bit because it means a vendor has tossed another bundle of work onto what&amp;rsquo;s likely an already overloaded plate. Since we&amp;rsquo;re all trying to think more positively these days (I hope), let&amp;rsquo;s discuss why this can be a Good Thing (tm) for all of us, especially when considering DevSecOps and Cybersecurity principles within a Google Cloud environment.&lt;/p&gt;</description></item></channel></rss>