Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Contour ingress controller deployment #460

Open
micron1390 opened this issue Oct 22, 2021 · 0 comments
Open

Contour ingress controller deployment #460

micron1390 opened this issue Oct 22, 2021 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@micron1390
Copy link

Hello,

I can not connect contour with the ELB balancer, I registered a private address in loadBalancerIP: "192.168.0.10", but the balancer does not listening ports 80, 443
It is possible to bind ELB to kubespray ?

helm install contour bitnami/contour --namespace=kube-system -f values.yaml

NAME: contour
LAST DEPLOYED: Fri Oct 22 00:33:13 2021
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Get Contours's load balancer IP/hostname:
NOTE: It may take a few minutes for this to become available.
You can watch the status by running:
$ kubectl get svc contour-envoy --namespace kube-system -w
Once 'EXTERNAL-IP' is no longer '':
$ kubectl describe svc contour-envoy --namespace kube-system | grep Ingress | awk '{print $3}'
Configure DNS records corresponding to Kubernetes ingress resources to point to the load balancer IP/hostname found in step 1

Thank you!

@micron1390 micron1390 added the kind/bug Categorizes issue or PR as related to a bug. label Oct 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant