osbase/logtree.LeveledLogger -> go/logging.Leveled
This factors out the common leveled logger interface out of the logtree.
We want to use the same interface outside of logtree/supervisor usage
within the resolver code, which will be exposed to clients.
Change-Id: I299e76d91e8cefddf8f36f1e58432418c4694df2
Reviewed-on: https://review.monogon.dev/c/monogon/+/3411
Reviewed-by: Tim Windelschmidt <tim@monogon.tech>
Tested-by: Jenkins CI
diff --git a/metropolis/node/kubernetes/clusternet/clusternet.go b/metropolis/node/kubernetes/clusternet/clusternet.go
index 28e268d..30c15a1 100644
--- a/metropolis/node/kubernetes/clusternet/clusternet.go
+++ b/metropolis/node/kubernetes/clusternet/clusternet.go
@@ -41,9 +41,9 @@
"k8s.io/client-go/kubernetes"
"k8s.io/client-go/tools/cache"
+ "source.monogon.dev/go/logging"
oclusternet "source.monogon.dev/metropolis/node/core/clusternet"
"source.monogon.dev/osbase/event"
- "source.monogon.dev/osbase/logtree"
"source.monogon.dev/osbase/supervisor"
)
@@ -52,7 +52,7 @@
Kubernetes kubernetes.Interface
Prefixes event.Value[*oclusternet.Prefixes]
- logger logtree.LeveledLogger
+ logger logging.Leveled
}
// ensureNode is called any time the node that this Service is running on gets