DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deploy GitHub Pages

Browse source
This commit is contained in:
Travis Bot 2019-09-22 20:06:22 +00:00
parent a1da96983c
commit 1d78bdfa08
60 changed files with 1251 additions and 1157 deletions
Download patch file Download diff file Expand all files Collapse all files

14
user-guide/basic-usage/index.html
View file

@ -32,7 +32,7 @@
<meta name="lang:search.tokenizer" content="[\s\-]+">
<link rel="shortcut icon" href="../../assets/images/favicon.png">
<meta name="generator" content="mkdocs-1.0.4, mkdocs-material-4.4.1">
<meta name="generator" content="mkdocs-1.0.4, mkdocs-material-4.4.2">
@ -217,7 +217,7 @@
<li class="md-tabs__item">
<a href="../.." title="Welcome" class="md-tabs__link">
<a href="../.." class="md-tabs__link">
Welcome
</a>
@ -230,7 +230,7 @@
<li class="md-tabs__item">
<a href="../../deploy/" title="Deployment" class="md-tabs__link">
<a href="../../deploy/" class="md-tabs__link">
Deployment
</a>
@ -247,7 +247,7 @@
<li class="md-tabs__item">
<a href="../nginx-configuration/" title="User guide" class="md-tabs__link md-tabs__link--active">
<a href="../nginx-configuration/" class="md-tabs__link md-tabs__link--active">
User guide
</a>
@ -262,7 +262,7 @@
<li class="md-tabs__item">
<a href="../../examples/" title="Examples" class="md-tabs__link">
<a href="../../examples/" class="md-tabs__link">
Examples
</a>
@ -274,7 +274,7 @@
</div>
</nav>
<main class="md-main">
<main class="md-main" role="main">
<div class="md-main__inner md-grid" data-md-component="container">
@ -1149,7 +1149,7 @@
<h1 id="basic-usage-host-based-routing">Basic usage - host based routing<a class="headerlink" href="#basic-usage-host-based-routing" title="Permanent link">&para;</a></h1>
<p>ingress-nginx can be used for many use cases, inside various cloud provider and supports a lot of configurations. In this section you can find a common usage scenario where a single load balancer powerd by ingress-nginx will route traffic to 2 different HTTP backend services based on the host name.</p>
<p>ingress-nginx can be used for many use cases, inside various cloud provider and supports a lot of configurations. In this section you can find a common usage scenario where a single load balancer powered by ingress-nginx will route traffic to 2 different HTTP backend services based on the host name.</p>
<p>First of all follow the instructions to install ingress-nginx. Then imagine that you need to expose 2 HTTP services already installed: <code class="codehilite">myServiceA</code>, <code class="codehilite">myServiceB</code>. Let's say that you want to expose the first at <code class="codehilite">myServiceA.foo.org</code> and the second at <code class="codehilite">myServiceB.foo.org</code>. One possible solution is to create two <strong>ingress</strong> resources:</p>
<div class="codehilite"><pre><span></span><span class="n">apiVersion</span><span class="o">:</span> <span class="n">extensions</span><span class="o">/</span><span class="n">v1beta1</span>
<span class="n">kind</span><span class="o">:</span> <span class="n">Ingress</span>