<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting started with vClusters on</title><link>/kosmos/devspaces/vclusters-management/</link><description>Recent content in Getting started with vClusters on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><atom:link href="/kosmos/devspaces/vclusters-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Setup Ingress with vcluster</title><link>/kosmos/devspaces/vclusters-management/setup-ingress-vcluster/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kosmos/devspaces/vclusters-management/setup-ingress-vcluster/</guid><description>Ingress overview # An Ingress is a Kubernetes API object that defines rules for routing external HTTP/HTTPS traffic to Services running inside a vCluster. An Ingress controller enforces these rules by processing incoming requests and directing them to the appropriate backend Service.
This page demonstrates how to configure a simple Ingress that routes requests to the kuard Service based on the HTTP request path.
Before you begin # To comply with Samsung’s security policy, this Ingress resource supports only a single TLS port and assumes TLS termination at the Ingress layer.</description></item></channel></rss>