Add root ca cert for telemetry configuration #1363
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1363
Loading…
Reference in a new issue
No description provided.
Delete branch "AlekseySVTN/frostfs-node:add-root-ca-cert-for-telemetry-configuration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Aleksey Savaitan a.savaitan@yadro.com
@ -17,0 +14,4 @@
conf, err := tracingconfig.ToTracingConfig(c.appCfg)
if err != nil {
c.log.Error(logs.FrostFSNodeFailedInitTracing, zap.Error(err))
return
Need to think about "return" here.
WIP #1361 Add root ca cert for telemetry configurationto WIP: Add root ca cert for telemetry configuration@ -256,2 +256,3 @@
"endpoint": "localhost:9090",
"exporter": "otlp_grpc"
"exporter": "otlp_grpc",
"caCert": ""
trusted_ca
ortrusted_ca_list
(as we already have in other places, though, I am not sure we want an array here)We have decided to use trusted_ca for first steps.
b16d4b10c6
to4036461500
@ -23,0 +26,4 @@
if caCert := config.StringSafe(c.Sub(subsection), "caCert"); caCert != "" {
certPool := x509.NewCertPool()
ok := certPool.AppendCertsFromPEM([]byte(caCert))
Ehm, do you expect the whole certificate to be inlined in the configuration?
It is much better to accept path, as we already do.
Fixed, we have decided to use path on FS.
4036461500
to81350b33d5
81350b33d5
toab2746c2e8
ab2746c2e8
toec6ff3c9d5
ec6ff3c9d5
todf007b9671
df007b9671
toa8a979917b
WIP: Add root ca cert for telemetry configurationto Add root ca cert for telemetry configuration@ -17,2 +14,4 @@
conf, err := tracingconfig.ToTracingConfig(c.appCfg)
if err != nil {
c.log.Error(logs.FrostFSNodeFailedInitTracing, zap.Error(err))
} else {
Please, check it. It seems to be more good to paste return after c.log on 16 and on 20 line.
@dstepanov-yadro @fyrchik
agree
Fixed.
a8a979917b
to9013b6a737
@ -256,2 +256,3 @@
"endpoint": "localhost:9090",
"exporter": "otlp_grpc"
"exporter": "otlp_grpc",
"trusted_ca": ""
These values are used in tests, it would be nice to use some non-empty value here, e.g.
/etc/ssl/tracing.pem
Fixed.
Can we avoid updating gRPC? It introduced
deprecated
warnings9013b6a737
tod04b95ee23
New commits pushed, approval review dismissed automatically according to repository settings
Do you mean "paste nolint staticcheck"? Or something else (turn of ci/cd lintier for pr/ etc..)? Or may be put grpc.NewClient as linter says?
d04b95ee23
toa883ac4a4c
@ -1278,7 +1278,6 @@ func (c *cfg) reloadConfig(ctx context.Context) {
// all the components are expected to support
// Logger's dynamic reconfiguration approach
var components []dCmp
Refactoring reason: linter - funlen 82>80.
It is better to put the refactoring in a separate commit.
Fixed
a883ac4a4c
to368a8f6fc4
gopls
check can't be disabled: https://github.com/golang/go/issues/50764 with source code annotation368a8f6fc4
toc46c605341
c46c605341
to87620d71f6
Agree, I did't find solution to skip gopls suggestions.
So, should I remove "WithBlock" and replace DialContext to NewClient by gopls suggestions? Or any other ideas exits?
Will fix here #1374
you can rebase
87620d71f6
to7bbe90803c
Thanks, done.