<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on storck.io</title>
    <link>https://storck.io/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on storck.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2020 14:48:08 +0200</lastBuildDate>
    <atom:link href="https://storck.io/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying Ruby on Rails apps to Kubernetes from Gitlab CI</title>
      <link>https://storck.io/posts/deploying-ruby-on-rails-to-kubernetes-from-gitlab-ci/</link>
      <pubDate>Thu, 11 Jun 2020 12:18:00 +0200</pubDate>
      <guid>https://storck.io/posts/deploying-ruby-on-rails-to-kubernetes-from-gitlab-ci/</guid>
      <description>Gitlab CI allows you to create and manage Kubernetes clusters directly from the interface and easily deploy builds to your existing Kubernets infrastructure. Here&amp;rsquo;s how.</description>
    </item>
    <item>
      <title>Adding external hosts to a Prometheus Operator helm release</title>
      <link>https://storck.io/posts/prometheus-operator-external-host/</link>
      <pubDate>Wed, 03 Jun 2020 09:27:00 +0200</pubDate>
      <guid>https://storck.io/posts/prometheus-operator-external-host/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/coreos/prometheus-operator&#34;&gt;Prometheus Operator&lt;/a&gt; is the perfect cloud-native monitoring solution for Kubernetes. By deploying the &lt;a href=&#34;https://github.com/helm/charts/tree/master/stable/prometheus-operator&#34;&gt;Helm chart&lt;/a&gt; you get a preconfigured Prometheus and Grafana setup plus an array of CRDs to add monitoring your own services.&lt;/p&gt;&#xA;&lt;p&gt;Not everything necessarily lives in a Kubernetes cluster, though. So how would you add external targets to a Prometheus Operator setup? One could define an Endpoint, Service and ServiceMonitor for the external resource to have it picked up by Prometheus&amp;rsquo; Kubernetes service discovery, which works, but there is a better solution that is more in line with how Prometheus is used outside&#xA;of the Operator deployment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
