<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ingress on Support Tools</title><link>https://support.tools/categories/ingress/</link><description>Recent content in Ingress on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 16 Oct 2024 01:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/ingress/index.xml" rel="self" type="application/rss+xml"/><item><title>Enabling ModSecurity in the Kubernetes Ingress-NGINX Controller</title><link>https://support.tools/modsecurity-kubernetes-ingress-nginx/</link><pubDate>Wed, 16 Oct 2024 01:00:00 -0500</pubDate><guid>https://support.tools/modsecurity-kubernetes-ingress-nginx/</guid><description>&lt;h2 id="enabling-modsecurity-in-the-kubernetes-ingress-nginx-controller"&gt;Enabling ModSecurity in the Kubernetes Ingress-NGINX Controller&lt;/h2&gt;&#10;&lt;p&gt;The Kubernetes Ingress-NGINX controller allows you to enable &lt;strong&gt;ModSecurity&lt;/strong&gt;, a powerful open-source Web Application Firewall (WAF). This post will guide you through the process of enabling and configuring ModSecurity with Ingress-NGINX to protect your applications from various types of web attacks.&lt;/p&gt;</description></item><item><title>Change Default Ingress Port to HTTP for Bitnami/nginx in Kubernetes</title><link>https://support.tools/change-default-ingress-port-http-bitnami-nginx-kubernetes/</link><pubDate>Fri, 11 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/change-default-ingress-port-http-bitnami-nginx-kubernetes/</guid><description>&lt;p&gt;When setting up &lt;strong&gt;Bitnami/nginx&lt;/strong&gt; as your Ingress controller in a Kubernetes environment, the default configuration may use HTTPS (port 443). However, there are cases where you might want to change the default Ingress port to &lt;strong&gt;HTTP (port 80)&lt;/strong&gt;, especially if you&amp;rsquo;re dealing with non-HTTPS traffic or need to expose services through standard HTTP.&lt;/p&gt;&#10;&lt;p&gt;In this post, we will walk through how to modify the default Ingress port for Bitnami/nginx in Kubernetes to use &lt;strong&gt;HTTP (port 80)&lt;/strong&gt; instead of HTTPS, allowing you to handle non-encrypted traffic effectively.&lt;/p&gt;</description></item><item><title>Kubernetes Ingress vs Service Mesh</title><link>https://support.tools/post/kubernetes-ingress-vs-service-mesh/</link><pubDate>Thu, 14 Jul 2022 23:22:00 -0500</pubDate><guid>https://support.tools/post/kubernetes-ingress-vs-service-mesh/</guid><description>&lt;p&gt;Getting your network up and running in Kubernetes is no easy task. No matter if you work on the operations or application side, you need to think about networking. Whether it is connecting clusters, control planes, and workers, or connecting Kubernetes Services and Pods, ensuring connectivity is a task that requires attention and effort.&lt;/p&gt;&#10;&lt;p&gt;You will learn what a service mesh is, what ingress is, and why you need both in this post.&lt;/p&gt;</description></item></channel></rss>