Skip to content

Conversation

@liwenwu-amazon
Copy link
Contributor

Issue #16, if available:

Description of changes:

Here are detail

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@liwenwu-amazon liwenwu-amazon changed the title Support for Vanity Name and Bring Your Own Certificates (working-in-progress) Support for Vanity Name and Bring Your Own Certificates Feb 10, 2023
protocol = section.Protocol

if section.TLS != nil {
if *section.TLS.Mode == v1alpha2.TLSModeTerminate {

Choose a reason for hiding this comment

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

is it possible that section.TLS.Mode == nil?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point. Let me add a check to avoid crash.

const (
resourceIDListenerConfig = "ListenerConfig"

awsCustomCertARN = "application-networking.k8s.aws/certificate-arn"

Choose a reason for hiding this comment

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

is it possible to specify multiple certificates per gateway?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Today, Lattice only allow one certificate per lattice-service/HTTPRoute. Gateway can have multiple sections where each section has its own certificates ARN

Copy link

@M00nF1sh M00nF1sh left a comment

Choose a reason for hiding this comment

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

/lgtm
looks good to me from the code perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants