<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mert Öngengil on Medium]]></title>
        <description><![CDATA[Stories by Mert Öngengil on Medium]]></description>
        <link>https://medium.com/@mertongngl?source=rss-e58f7de58d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mJDn0ItGdv9km2fOCCYgPQ.jpeg</url>
            <title>Stories by Mert Öngengil on Medium</title>
            <link>https://medium.com/@mertongngl?source=rss-e58f7de58d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:02:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mertongngl/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to migrate MongoDB Replica Set Cluster with zero downtime]]></title>
            <link>https://medium.com/bitaksi-tech/how-to-migrate-mongodb-replica-set-cluster-with-zero-downtime-910902ac3af0?source=rss-e58f7de58d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/910902ac3af0</guid>
            <category><![CDATA[bitaksi]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mert Öngengil]]></dc:creator>
            <pubDate>Fri, 18 Mar 2022 10:52:04 GMT</pubDate>
            <atom:updated>2022-03-18T10:58:03.987Z</atom:updated>
            <content:encoded><![CDATA[<p>Firstly, I want to say Merhaba to everyone. I’m working at BiTaksi as DevOps Engineer. BiTaksi is a hailing company in Turkey. MongoDB is one of the NoSQL database solutions at BiTaksi. I am going to show you how to migrate MongoDB Replica Set Cluster to new nodes in this article. Don’t worry :) I think you don’t need the installation guide for MongoDB since you already know. So, let’s check drawings about this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_sBPZXBXYc3tKwozuHvGA.png" /></figure><h4>Phase-1</h4><ul><li>Create new nodes that can reach old nodes over the network.</li><li>Add new nodes to the replica set as hidden.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/77a930952b416fb95656ab5eb2d70e4f/href">https://medium.com/media/77a930952b416fb95656ab5eb2d70e4f/href</a></iframe><h4>Phase-2</h4><ul><li>You can use the commands below for checking the data syncing process</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a6b166971d1ab1b687731d254bcdebda/href">https://medium.com/media/a6b166971d1ab1b687731d254bcdebda/href</a></iframe><ul><li>Change RS configurations for the new nodes</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a98b0513538e053f56286ed97a753cbe/href">https://medium.com/media/a98b0513538e053f56286ed97a753cbe/href</a></iframe><h4>Phase-3</h4><ul><li>Update the config of the application(s) that depends on MongoDB Cluster.</li></ul><p>Old Connection URI:</p><pre>mongodb://admin:super_strong_password@poc-mongo-01.bitaksi.com:27017,poc-mongo-02.bitaksi.com:27017,poc-mongo-03.bitaksi.com:27017/poc?replicaSet=poc&amp;readPreference=secondaryPreferred&amp;authSource=admin</pre><p>Temp Connection URI:</p><pre>mongodb://admin:super_strong_password@poc-mongo-01.bitaksi.com:27017,poc-mongo-new-01.bitaksi.com:27017,poc-mongo-new-02.bitaksi.com:27017,poc-mongo-new-03.bitaksi.com:27017/poc?replicaSet=poc&amp;readPreference=secondaryPreferred&amp;authSource=admin</pre><p>Then you can remove old secondaries from the RS.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3155806ff89bfbf0afb5e87ce5b962aa/href">https://medium.com/media/3155806ff89bfbf0afb5e87ce5b962aa/href</a></iframe><h4>Phase-4</h4><ul><li>Change the primary node</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d80738a0205cff0f1c3f8961d6bdeb84/href">https://medium.com/media/d80738a0205cff0f1c3f8961d6bdeb84/href</a></iframe><ul><li>Wait until the nodes are up-and-running</li></ul><pre>// you can check Replica Set status<br>rs.status()</pre><h4>Phase-5</h4><ul><li>Change your Connection URI in application configs again</li></ul><p>Temp Connection URI</p><pre>mongodb://admin:super_strong_password@poc-mongo-01.bitaksi.com:27017,poc-mongo-new-01.bitaksi.com:27017,poc-mongo-new-02.bitaksi.com:27017,poc-mongo-new-03.bitaksi.com:27017/poc?replicaSet=poc&amp;readPreference=secondaryPreferred&amp;authSource=admin</pre><p>New Connection URI</p><pre>mongodb://admin:super_strong_password@poc-mongo-new-01.bitaksi.com:27017,poc-mongo-new-02.bitaksi.com:27017,poc-mongo-new-03.bitaksi.com:27017/poc?replicaSet=poc&amp;readPreference=secondaryPreferred&amp;authSource=admin</pre><ul><li>And then, you can remove the old node from Replica Set</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4919b11bd96c526a5a5e545d06d2e5b7/href">https://medium.com/media/4919b11bd96c526a5a5e545d06d2e5b7/href</a></iframe><h3>Conclusion</h3><p>Why did we invent this process? It’s a good question. We had to migrate the cluster to a new network, so we need to trick for handling this migration without any outage.</p><h4>Benefits</h4><ul><li>You have zero downtime. If you carefully follow these steps.</li><li>Sometimes background index can corrupt the nodes. If you have any issue with the index, you can get rid of it.</li></ul><h4>Drawbacks</h4><ul><li>You have to change application configs twice</li><li>Following those steps may become prone to error. So, make sure you take them carefully.</li><li>You have to do too many Replica Set configuration changes.</li></ul><p>We didn’t find guidance like this. I wish it will help you. May the force be with you. 🚀</p><h3>Resources:</h3><ul><li><a href="https://docs.mongodb.com/v4.4/reference/method/rs.add/">https://docs.mongodb.com/v4.4/reference/method/rs.add/</a></li><li><a href="https://docs.mongodb.com/manual/tutorial/adjust-replica-set-member-priority/">https://docs.mongodb.com/manual/tutorial/adjust-replica-set-member-priority/</a></li><li><a href="https://docs.mongodb.com/v4.4/reference/method/rs.remove/">https://docs.mongodb.com/v4.4/reference/method/rs.remove/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=910902ac3af0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitaksi-tech/how-to-migrate-mongodb-replica-set-cluster-with-zero-downtime-910902ac3af0">How to migrate MongoDB Replica Set Cluster with zero downtime</a> was originally published in <a href="https://medium.com/bitaksi-tech">BiTaksi Product &amp; Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[awsx]]></title>
            <link>https://medium.com/@mertongngl/awsx-92687eb3be19?source=rss-e58f7de58d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/92687eb3be19</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Mert Öngengil]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 11:48:49 GMT</pubDate>
            <atom:updated>2020-04-03T11:48:49.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2baUd8NJ8aEY6dMFnyAnYg.png" /></figure><p>AWS kimliğinizi her seferinde değiştirmek zor geliyorsa awsx komut satırı aracını kullanacağınızda ve bu hikayeyi okuduğunuzda işinizi kolaylaştıracağına eminim :) . Öncelikle kendimden bahsedeyim. <a href="https://www.bestcloudfor.me/"><em>bestcloudfor.me</em></a> şirketinde Cloud Native Engineer Professional olarak çalışıyorum ve müşterilerimiz çoğunlukla bulut çözümü olarak AWS(Amazon Web Services) kullanıyorlar. Hal böyle olunca gün içerisinde onlarca kez aws kimliğinizi uçbirim üzerinde değiştirmeniz gerekiyor. Bu sürecin demosunu aşağıya ekledim :)</p><blockquote><a href="https://medium.com/@mertongngl/one-tool-to-rule-them-all-awsx-3e5f3ce5ec65">Read this post in English here</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*E3C6Urkm_iO6YnZWKHIcZw.gif" /></figure><p>Bu işlemi sürekli yaptığınızı bir düşünsenize, açıkçası bu utançla daha fazla yaşayamazdım.</p><p>O zamanlar kubernetes cluster’ları arasında gezmek içinkubetcx kullanıyordum. Buradan <a href="https://github.com/ahmetb"><em>Ahmet Alp Balkan</em></a><em>’a </em><em>kubectx</em> için teşekkürler. Aslında sorunumu çözmekte kubectx aracından çok ilham aldım. Fakat kubernetes konfigurasyon dosyası kadar kolay işlenebilir bir dosya olmadığı için elimde biraz zorladı. Home dizinimde .aws.configs isminde bir dizin oluşturdum. Bu dizinin hiyerarşisini aşağıda görebilirsiniz</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*-1FZRIkObjqpeYXgc86RPg.png" /></figure><p>AWS kimliklerini ve o an kullanılan AWS kimliğinin ismi gibi bilgileri bu dizinde tutuyorum.</p><p>Geliştirdiğim awsx aracını <a href="https://github.com/mertongngl/awsx"><strong><em>buradan</em></strong></a> indirebilirsiniz.</p><p>Güç sizinle olsun gönül dostları ! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92687eb3be19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One tool to rule them all | awsx]]></title>
            <link>https://medium.com/@mertongngl/one-tool-to-rule-them-all-awsx-3e5f3ce5ec65?source=rss-e58f7de58d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e5f3ce5ec65</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Mert Öngengil]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 11:46:59 GMT</pubDate>
            <atom:updated>2020-04-03T11:46:59.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2baUd8NJ8aEY6dMFnyAnYg.png" /></figure><p>If you need a powerful tool for switching AWS(Amazon Web Services) credentials, you will read this story and use my tool. Firstly, I’m a Cloud Native Engineer at <a href="https://www.bestcloudfor.me/"><em>bestcloudfor.me</em></a> and we have many clients are using AWS commonly. I had trouble with switching AWS credentials on my terminal. It was so uncomfortable way like the command below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*E3C6Urkm_iO6YnZWKHIcZw.gif" /></figure><p>Did you think you have to do these steps all the time? What a shame?</p><p>I was using kubectx for switching cluster configs and thanks for <a href="https://github.com/ahmetb"><em>Ahmet Alp Balkan</em></a> for kubectx. I was thinking on my issue and I inspired by kubectx . But I hadn’t clear config like kubectl and I was searching a workaround solution. I created a directory as .aws.configs in home directory and I put all configs like the command below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*-1FZRIkObjqpeYXgc86RPg.png" /></figure><p>I store credentials, current credential’s value on that directory and this directory fully-managed by tool.</p><p>You can get awsx from <a href="https://github.com/mertongngl/awsx"><strong><em>here</em></strong></a><em>.</em></p><p>May the force be with you !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e5f3ce5ec65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Travis CI + AKS(Azure Kubernetes Service)Zero DownTime Continuous Deployment Case Study]]></title>
            <link>https://medium.com/bestcloudforme/travis-ci-aks-azure-kubernetes-service-zero-downtime-continuous-deployment-case-study-26a87061443a?source=rss-e58f7de58d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/26a87061443a</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[bestcloudforme]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Mert Öngengil]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 09:46:08 GMT</pubDate>
            <atom:updated>2019-08-16T10:50:36.823Z</atom:updated>
            <content:encoded><![CDATA[<h3>Travis CI - Azure Kubernetes Service CI/CD Case Study(Zero Down Time Deployment)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fl-sexdxtvEqUqwoxmjcAw.jpeg" /></figure><blockquote><a href="https://medium.com/bestcloudforme/travis-ci-aks-azure-kubernetes-service-zero-downtime-continuous-deployment-case-study-eng-ee5d1de256f2?source=friends_link&amp;sk=f1af7c8c3b4b4ff55ca869a6d3b8999c">Read this post in English here</a></blockquote><p>Telekom ve ödeme sistemleri alanında global ölçekte olan müşterimiz için Travis-CI, AKS(Azure Kubernetes Service) alt yapılarını kullanarak başarılı bir şekilde gerçekleştirdiğimiz CI/CD projemizi sizlerle paylaşmaktan mutluluk duyuyoruz. Projede emeği geçen tüm arkadaşlarımıza katkılarından dolayı çok teşekkür ederiz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qS4nUkGXMqc2H3D5W3Ekvg.jpeg" /></figure><h3>Kilometre Taşları</h3><ul><li>Pipeline geliştirmelerinin Travis-CI için yapılması(Pipeline as a code).Helm chartlarının ACR(Azure Container Registry) e pushlanması</li><li>“<strong><em>Codestyle, Unit, Integration</em></strong>” testlerin Travis üzerinde paralel koşturulması.</li><li>Kubernetes için AKS(Azure Kubernetes Service) alt yapısının kullanılması.</li><li>Docker imajının versiyonlanıp Docker Hub’a pushlanması.</li></ul><h3>Kazanımlar</h3><ul><li>Sürüm çıkmanın 3 farklı otomasyon testinden geçirilerek oluşabilecek hatanın minimum seviyeye indirilmesi.</li><li>Commit’ten AKS(Azure Kubernetes Service)’ine kadar olan sürecin pipeline as a code felsefesi ile gerçekleşmesi.</li><li>Platform bağımsız deployment yapabilme esnekliği.</li><li>Continuous deployment.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26a87061443a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bestcloudforme/travis-ci-aks-azure-kubernetes-service-zero-downtime-continuous-deployment-case-study-26a87061443a">Travis CI + AKS(Azure Kubernetes Service)Zero DownTime Continuous Deployment Case Study</a> was originally published in <a href="https://medium.com/bestcloudforme">bestcloudforme</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Travis CI + AKS(Azure Kubernetes Service)Zero DownTime Continuous Deployment Case Study[ENG]]]></title>
            <link>https://medium.com/bestcloudforme/travis-ci-aks-azure-kubernetes-service-zero-downtime-continuous-deployment-case-study-eng-ee5d1de256f2?source=rss-e58f7de58d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee5d1de256f2</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[bestcloudforme]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Mert Öngengil]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 09:39:26 GMT</pubDate>
            <atom:updated>2019-08-16T10:12:00.564Z</atom:updated>
            <content:encoded><![CDATA[<h3>Travis CI - Azure Kubernetes Service CI/CD Case Study(Zero Down Time Deployment)[ENG]</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fl-sexdxtvEqUqwoxmjcAw.jpeg" /></figure><p>We gladly announce our success in a CI/CD project that we lead by using Travis-CI and AKS(Azure Kubernetes Service) infrastructures for one of our clients, which is a global Telecom and Digital Payment Company. We wish to thank all our colleagues who contributed to the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qS4nUkGXMqc2H3D5W3Ekvg.jpeg" /></figure><h3>Milestones</h3><ul><li>Pipeline improvements for Travis-CI (Pipeline as a code).Pushing Helm Charts to ACR (Azure Container Registry).</li><li>“Codestyle, Unit, Integration” tests are run on Travis in parallel.</li><li>Using AKS (Azure Kubernetes Service) infrastructure for Kubernetes.</li><li>Pushing Docker images with tags on Docker Hub</li></ul><h3>The Benefits</h3><ul><li>Errors are minimized by testing the deployment with 3 different automation tests.</li><li>The process from Commit to AKS(Azure Kubernetes Service) is done with the pipeline as a code.</li><li>The ability of flexible, platform-independent deployment.</li><li>Continuous deployment.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee5d1de256f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bestcloudforme/travis-ci-aks-azure-kubernetes-service-zero-downtime-continuous-deployment-case-study-eng-ee5d1de256f2">Travis CI + AKS(Azure Kubernetes Service)Zero DownTime Continuous Deployment Case Study[ENG]</a> was originally published in <a href="https://medium.com/bestcloudforme">bestcloudforme</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>