Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
k8s-ingress
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
3
Merge Requests
3
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
uplex-varnish
k8s-ingress
Commits
efb6498a
Commit
efb6498a
authored
Jun 30, 2020
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Apply a BackendConfig in the example for ExternalName Services.
Ref gitlab issue #20
parent
08f6e38d
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
79 additions
and
0 deletions
+79
-0
backend-cfg.yaml
examples/externalname/backend-cfg.yaml
+75
-0
deploy.sh
examples/externalname/deploy.sh
+2
-0
undeploy.sh
examples/externalname/undeploy.sh
+2
-0
No files found.
examples/externalname/backend-cfg.yaml
0 → 100644
View file @
efb6498a
# Sample backend configurations
apiVersion
:
"
ingress.varnish-cache.org/v1alpha1"
kind
:
BackendConfig
metadata
:
name
:
tea-svc-cfg
spec
:
# The services array is required and must have at least one element.
# Lists the names of Services that act as Backends for an Ingress in
# the same namespace, and are configured as backends for a Varnish
# Service that implements the Ingress. This config is to be applied
# to the Varnish backends corresponding to the Services named in the
# array.
services
:
-
tea-external-svc
# For requests routed to tea-external-svc:
# - The Host header is set to cafe.example.com if it is missing from
# the request.
# - The connect timeout (for opening new connections to an Endpoint)
# is one second.
# - The first byte timeout (until the first byte of a backend response
# header is received) is two seconds.
# - The between bytes timeout (while a response is being received)
# is one second.
# - No more than 200 connections to an Endpoint may be opened.
host-header
:
cafe.example.com
connect-timeout
:
1s
first-byte-timeout
:
2s
between-bytes-timeout
:
1s
max-connections
:
200
probe
:
# Health probe requests for Endpoints of tea-external-svc:
# - Request URL path is /tea/healthz
# - Health probes are good when the response code is 200.
# - Five second timeout to receive responses.
# - Probes are sent every five seconds.
# - Two of three probes must be good for the Endpoint to count as
# healthy.
# - At startup, one probe is implicitly assumed to be good.
url
:
/tea/healthz
expected-response
:
200
timeout
:
5s
interval
:
5s
initial
:
1
window
:
3
threshold
:
2
---
apiVersion
:
"
ingress.varnish-cache.org/v1alpha1"
kind
:
BackendConfig
metadata
:
name
:
coffee-svc-cfg
spec
:
services
:
-
coffee-external-svc
# For requests routed to coffee-external-svc:
# - The first byte timeout is three seconds.
# - The between bytes timeout is two seconds.
first-byte-timeout
:
3s
between-bytes-timeout
:
2s
probe
:
# Health probe for coffee-external-svc:
# - Requests are send as shown in the request array.
# - Timeout three seconds.
# - Three of four good probes are required for the Endpoint to
# count as healthy.
request
:
-
GET /coffee/healthz HTTP/1.1
-
"
Host:
cafe.example.com"
-
"
Connection:
close"
timeout
:
3s
interval
:
3s
window
:
4
threshold
:
3
examples/externalname/deploy.sh
View file @
efb6498a
...
...
@@ -5,3 +5,5 @@ kubectl create -f ../hello/cafe.yaml
kubectl create
-f
ext-svcs.yaml
kubectl create
-f
cafe-ingress.yaml
kubectl apply
-f
backend-cfg.yaml
examples/externalname/undeploy.sh
View file @
efb6498a
#! /bin/bash -ex
kubectl delete
-f
backend-cfg.yaml
kubectl delete
-f
cafe-ingress.yaml
kubectl delete
-f
ext-svcs.yaml
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment