Skip to content
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

Adding statefulsets to inject #910

Merged
merged 1 commit into from
May 10, 2018
Merged

Conversation

grampelberg
Copy link
Contributor

No description provided.

Copy link
Member

@siggy siggy left a comment

Choose a reason for hiding this comment

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

by convention, add Fixes #907 to the end of your commit message, that way Github will resolve the original issue when this merges.

return err
}
obj = &statefulset
k8sLabels[k8s.ProxyDeploymentLabel] = statefulset.Name
Copy link
Member

@siggy siggy May 8, 2018

Choose a reason for hiding this comment

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

you'll need to create a new k8s.ProxyStatefulSetLabel.

taking this a bit farther, this implies some subsequent tasks (best done in future PRs, not this one):

it's possible that with this particular PR, we'll at least get stateful-set labels and metrics wired all the way through from inject -> pod -> destination service -> proxy -> prometheus, but i'm not totally sure. have you tried deploying a StatefulSet and seeing if metrics show up in Prometheus?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's just what I needed. I'll go look at those now and update this.

@grampelberg
Copy link
Contributor Author

grampelberg commented May 9, 2018

  • prometheus - getting all the metrics
  • grafana - dashboards are limited to deployments
  • stat - not working for statefulset, working fine for pod
  • tap - not working for statefulset, working fine for pod
  • dashboard - would need statefulset added

@siggy what do you think would be the best way to move forward. I see a couple options:

For this PR, purely from a scoping/focus perspective, it feels okay to leave it at injection and open up issues to track the others. It looks like we've missed implementing things like stat/tap for the other resource types as well (job, daemonset).

@grampelberg grampelberg force-pushed the grampelberg/statefulset-support branch 2 times, most recently from c2c315b to ac52d56 Compare May 9, 2018 16:40
Copy link
Member

@siggy siggy left a comment

Choose a reason for hiding this comment

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

thanks for all the updates.

i agree most of this work should be done in subsequent PRs, and we just focus on injection for this PR.

for this PR, there are a couple more places that i think we need to add StatefulSet support:

@grampelberg grampelberg force-pushed the grampelberg/statefulset-support branch from ac52d56 to fe1e828 Compare May 9, 2018 21:48
@grampelberg
Copy link
Contributor Author

Ah, the joys of learning a new codebase. Got that all updated, thank you!

Copy link
Member

@siggy siggy left a comment

Choose a reason for hiding this comment

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

@grampelberg
Copy link
Contributor Author

I grep'd for those, damnit! The underscore got me.

@grampelberg grampelberg force-pushed the grampelberg/statefulset-support branch from fe1e828 to 9ead4a6 Compare May 10, 2018 13:43
@grampelberg grampelberg force-pushed the grampelberg/statefulset-support branch from 9ead4a6 to 6dbc1bd Compare May 10, 2018 13:48
@grampelberg grampelberg merged commit 25d8b22 into master May 10, 2018
@grampelberg grampelberg deleted the grampelberg/statefulset-support branch May 10, 2018 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants