-
Notifications
You must be signed in to change notification settings - Fork 327
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
refactoring: refactor Envoy config generators to be modular and composable #570
Conversation
380083e
to
b26055e
Compare
b26055e
to
11d0d55
Compare
11d0d55
to
b6c7868
Compare
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.
Nice work, I like it 👍
A couple of suggestions:
- Move all stuff connected with listeners to
pkg/xds/envoy/listeners
orpkg/xds/envoy/lds
- Move all stuff connected with clusters to
pkg/xds/envoy/clusters
. Just move without refactor to similar pattern. We can do it later if needed - Move all stuff connected with endpoints to
pkg/xds/envoy/endpoints
. Just move without refactor to similar pattern. - Move all TLS stuff to
pkg/xds/envoy/tls.go
This way we get rid of this envoy.go
file so it won't become this "envoy generation god file" that it was before.
What do you think?
pkg/xds/envoy/builder.go
Outdated
|
||
// ListenerBuilder is responsible for generating an Envoy listener | ||
// by applying a series of ListenerConfigurers. | ||
type ListenerBuilder interface { |
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 be really an interface
? I think struct
is enough
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.
changed
Done |
Summary