-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tls: executing pod termination (PROJQUAY-2428) #517
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one question
} | ||
if quayComponentLabel == "quay-app-route" { | ||
rt.Spec.Port = &route.RoutePort{ | ||
TargetPort: intstr.Parse("https"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I 100% understand this, intstr.Parse()
is going to create an object whose String()
method will return "https"
and whose IntValue()
method will return 0
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it is a struct (intstr.IntOrString
) used by k8s when a field may be an int or a string (like the port).
fieldGroup := &hostsettings.HostSettingsFieldGroup{ | ||
ExternalTlsTermination: true, | ||
ExternalTlsTermination: terminateExternally, | ||
PreferredUrlScheme: "https", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this also be switched on whether or not we are terminating externally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we checked, it seems like we don't need it to be switched to http.
If TLS is unmanaged we expect the user to provide its own cert and key. This PR changes the route to 'passthrough' and mounts the certificates inside quay pod if TLS is unmanaged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If TLS is unmanaged we expect the user to provide its own cert and key.
This PR changes the route to 'passthrough' and mounts the certificates
inside quay pod if TLS is unmanaged.