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
40276b20
Commit
40276b20
authored
May 22, 2020
by
Geoff Simmons
Committed by
Tim Leers
Jul 06, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update main README.md section Installation.
Mention the haproxy container, and the Helm charts folder.
parent
d6136f23
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
7 deletions
+11
-7
README.md
README.md
+11
-7
No files found.
README.md
View file @
40276b20
...
@@ -26,19 +26,23 @@ valuable at this early stage.
...
@@ -26,19 +26,23 @@ valuable at this early stage.
# Installation
# Installation
Varnish
for the purposes of Ingress and the controller that manages it
Varnish
and haproxy for the purposes of Ingress run together in a Pod,
a
re implemented in separate containers -- one controller can be used
a
nd the controller that manages them runs in a separate Pod -- one
to manage a group of Varnish instances. The Dockerfiles and other
controller can be used to manage a group of Pods implementing
files needed to build the two images are in th
e
Ingress. The Dockerfiles and other files needed to build the thre
e
[
``container/``
](
/container
)
folder, together with a Makefile that
images are in the
[
``container/``
](
/container
)
folder, together with a
encapsulates the commands for the build.
Makefile that
encapsulates the commands for the build.
The resulting images must then be pushed to a registry available to
The resulting images must then be pushed to a registry available to
the Kubernetes cluster.
the Kubernetes cluster.
The Ingress can then be deployed by any of the means that are
The Ingress can then be deployed by any of the means that are
customary for Kubernetes. The
[
``deploy/``
](
/deploy
)
folder contains
customary for Kubernetes. The
[
``deploy/``
](
/deploy
)
folder contains
manifests (YAMLs) for some of the ways to deploy an Ingress.
manifests (YAMLs) for some of the ways to deploy an Ingress, using
tools such as
[
``kubectl``
](
https://kubernetes.io/docs/reference/kubectl/overview/
)
. The
[
``charts/``
](
/charts
)
folder contains charts for
[
Helm
](
https://helm.sh/
)
deployments.
The deployment described in
[
``deploy/``
](
/deploy
)
targets a default
The deployment described in
[
``deploy/``
](
/deploy
)
targets a default
setup in which the controller runs in the
``kube-system``
namespace
setup in which the controller runs in the
``kube-system``
namespace
...
...
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