After setting the CNAME record that points to my -con load balancer, the ingress rules should resolve and send traffic.
Actual Behavior
Nothing happens
Reproduction Steps
I don't know if this is the correct way to do this on AWS, please correct me if am wrong
Create a deployment, expose it as a NodePort service,
Create an Ingress pointing to the NodePort service, a typical Address will be shown for all ingress services created (is it normal that all ingresses have the same address?)
Go to Route53 create a CNAME record that points to the ELB that ends with -con
Wait for new domain to resolve
Other Information
Feature Request
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic?
AWS
Desired Feature
Can we have a simple way to allocate Elastic IPs to the services, like a section in the dashboard maybe with a list of IPs and services bond to them
patrickmuhi
commented
6 years ago
Issue Report Template
Tectonic Version
1.8.9-tectonic.2
Environment
AWS
Expected Behavior
After setting the CNAME record that points to my
-conload balancer, the ingress rules should resolve and send traffic.Actual Behavior
Nothing happens
Reproduction Steps
I don't know if this is the correct way to do this on AWS, please correct me if am wrong
-conOther Information
Feature Request
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic? AWS
Desired Feature
Can we have a simple way to allocate Elastic IPs to the services, like a section in the dashboard maybe with a list of IPs and services bond to them
Other Information