-
Notifications
You must be signed in to change notification settings - Fork 543
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
Added ruler.tls-enabled
configuration for alertmanager client
#3432
Added ruler.tls-enabled
configuration for alertmanager client
#3432
Conversation
pkg/ruler/notifier.go
Outdated
} | ||
|
||
func (cfg *NotifierConfig) RegisterFlags(f *flag.FlagSet) { | ||
f.BoolVar(&cfg.TLSEnabled, "ruler.tls-enabled", true, "Enable TLS for gRPC client connecting to alertmanager-client.") |
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.
Do we need to validate the TLS flag when tls-enabled
is enabled?
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.
It seems we didn't check it in other components. So I'll follow it.
tls_enabled
flag for alertmanager_client
configruler.tls-enabled
configuration for alertmanager client
c313d2e
to
6064583
Compare
Friendly ping @dimitarvdimitrov ~ |
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.
Thanks! I left a minor wording suggestion. The docs and the config descriptor will also need to be updated
…ana#3432) * Add `tls_enabled` flag for `alertmanager_client` config * Update CHANGELOG.md * Update CHANGELOG.md * Address comment
What this PR does
Add
tls_enabled
flag foralertmanager_client
config.Which issue(s) this PR fixes or relates to
close #3220
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]