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

allow specifying installation namespace in script #335

Merged
merged 6 commits into from
Jan 20, 2021

Conversation

rfratto
Copy link
Member

@rfratto rfratto commented Jan 19, 2021

PR Description

Allows a custom installation namespace in the Kubernetes install scripts through replacing an environment variable.

This also tweaks errors to the sigv4 script found when testing out #334.

Which issue(s) this PR fixes

Closes #319

Notes to the Reviewer

PR Checklist

  • CHANGELOG updated
  • Documentation added
  • Tests updated

@rfratto rfratto marked this pull request as ready for review January 20, 2021 13:43
@rfratto rfratto merged commit e99a0d2 into grafana:master Jan 20, 2021
@rfratto rfratto deleted the install-script-namespaces branch February 22, 2021 15:39
@mattdurham mattdurham mentioned this pull request Sep 7, 2021
3 tasks
mattdurham pushed a commit that referenced this pull request Nov 11, 2021
* allow specifying installation namespace in script

* specify ARN and add to ServiceAccount annotation

* fix NAMESPACE typo

* add namespace to serviceaccount

* add region

* update changelog, docs
@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Apr 17, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Agent installation on Kubernetes Envirnment
2 participants