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

Docs fix for rolling out config updates #182

Closed
MikeGoldsmith opened this issue Sep 28, 2021 · 2 comments
Closed

Docs fix for rolling out config updates #182

MikeGoldsmith opened this issue Sep 28, 2021 · 2 comments

Comments

@MikeGoldsmith
Copy link
Contributor

Originally raised by @pbiggar. I accidentally moved the issue to our internal docs repo which they could no longer see - sorry!

Re-creating this issue for visibility.

@mjingle
Copy link

mjingle commented Sep 28, 2021

@pbiggar Thank you for raising this issue. The Docs repo is currently private, which is why you can't find it, but our engineers will make sure any reported issue will get to the right location.

Original issue text:

I'm not sure the correct place to report this, as I can't find a repo for the docs.

At https://docs.honeycomb.io/getting-data-in/integrations/kubernetes/configuration/#uploading-a-configuration-file-to-a-cluster, I think (I'm not 100% sure) the command to restart the pods should be (as of k8s 1.15):

kubectl rollout restart ds/honeycomb-agent

instead of

kubectl delete pod --selector k8s-app=honeycomb-agent

@MikeGoldsmith
Copy link
Contributor Author

We are trimming our OSS backlog. We will be closing this issue as it is a low priority for us to fix. It is unlikely that we'll ever get to it, and so we'd like to set expectations accordingly.

If this issue is important to you, please feel free to ping here and we can discuss/re-open.

@MikeGoldsmith MikeGoldsmith closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants