-
Notifications
You must be signed in to change notification settings - Fork 324
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
Rename lifecycle-sidecar command to consul-sidecar #428
Conversation
e9b2152
to
376a659
Compare
Oh yeah right because after upgrade new pods will just use the new command
name. Nevermind!
…On Mon, Feb 1, 2021, 12:25 PM Nitya Dhanushkodi ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In commands.go
<#428 (comment)>:
> @@ -35,8 +35,8 @@ func init() {
return &cmdInjectConnect.Command{UI: ui}, nil
},
- "lifecycle-sidecar": func() (cli.Command, error) {
- return &cmdLifecycleSidecar.Command{UI: ui}, nil
+ "consul-sidecar": func() (cli.Command, error) {
Oh interesting, yeah! Would that mean just having lifecycle-sidecar return
the consul-sidecar command, i.e:
"lifecycle-sidecar": func() (cli.Command, error) {
return &cmdConsulSidecar.Command{UI: ui}, nil
Hmm, this command is only called by the pod-mutating-webhook, right? So
wouldn't nobody but our own code be calling consul-sidecar? If that's the
case, I feel like we wouldn't need to create the alias since within the
webhook handler we just change which command gets run for the sidecar. Its
not exposed in any way through the helm chart.
There are also some inject-connect flags, like
lifecycle-sidecar-cpu-request that have been renamed, so I was thinking the
helm values would accept
global.lifecycleSidecarContainer.resources.requests.cpu and
global.consulSidecarContainer.resources.requests.cpu but both would point
to the consul-sidecar-cpu-request flag in consul-k8s.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#428 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH4RPPYNOFG4REG4TPHASLS44E25ANCNFSM4WZ35Z2Q>
.
|
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.
Looking good. A couple places for lifecycle were missed that I could see. Do a quick grep in case I missed some others.
4a335df
to
5f25800
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.
Excellent work here @ndhanushkodi !! Have a few consul
-> Consul
suggestions. Also, threw in my opinion on the name of the sidecar.
8a1a355
to
a872106
Compare
a872106
to
c06a80f
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.
Excellent work!!
Originally, the lifecycle-sidecar's functionality was to register the Connect service with Consul. This sidecar will in the near future support merged metrics functionality, so this renaming supports that.
c06a80f
to
18a84d8
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.
🌀
Changes proposed in this PR:
Connect service with Consul. This sidecar will in the near future
support merged metrics functionality, so this renaming supports that.
NOTE: will wait to merge until the corresponding consul-helm change to change any calls to flags with "lifecycle-sidecar" in the name.
How I've tested this PR:
How I expect reviewers to test this PR:
Checklist: