Skip to content
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.

updated readme.md #173

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

updated readme.md #173

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5e53dc4
updated readme.md
pbisen Oct 1, 2020
8ab5f4f
Merge branch 'master' into readme-update
pbisen Oct 1, 2020
69665fe
Update README.md
pbisen Oct 1, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ How you provide access to the service is going to be dependent on your specific

A good starting point for yaml manifests for deploying to Kubernetes is in the [yaml](./yaml) directory.
This creates a namespace, configmap, deployment and service.
There is also an example ingress config that is set up to work with [Heptio Contour](https://github.com/heptio/contour), [JetStack cert-manager](https://github.com/jetstack/cert-manager) and [Let's Encrypt](https://letsencrypt.org/).
There is also an example ingress config that is set up to work with [Project Contour](https://github.com/projectcontour/contour), [JetStack cert-manager](https://github.com/jetstack/cert-manager) and [Let's Encrypt](https://letsencrypt.org/).
See [Dave Cheney's blog post](https://blog.heptio.com/how-to-deploy-web-applications-on-kubernetes-with-heptio-contour-and-lets-encrypt-d58efbad9f56) for an example of getting all of that configured.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe swap out Dave's link for this guide which is kept more up to date: https://projectcontour.io/guides/cert-manager/


You will probably have to adjust the service and ingress configs to match your environment as there is no one true way to reach services in Kubernetes that will work for everyone.
Expand Down Expand Up @@ -92,14 +92,14 @@ Run:
kubectl apply -f https://projectcontour.io/quickstart/contour.yaml
```

This will deploy Contour in the `heptio-contour` namespace, and expose it using a service of type `LoadBalancer`.
This will deploy Contour in the `projectcontour` namespace, and expose it using a service of type `LoadBalancer`.

### Configure DNS Record

Get the hostname of the ELB that Kubernetes created for the contour service:

```sh
kubectl get svc -n heptio-contour contour -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'
kubectl get svc -n projectcontour contour -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'
```

Create a wildcard CNAME record that aliases the domain under your control to the hostname of the ELB obtained above.
Expand Down