-
Notifications
You must be signed in to change notification settings - Fork 77
feat: grafloki start/stop #2696
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
Conversation
...d_framework/highlevel/engine_consuming_kurtosis_command/engine_consuming_kurtosis_command.go
Outdated
Show resolved
Hide resolved
container-engine-lib/lib/backend_impls/docker/docker_manager/types/container.go
Show resolved
Hide resolved
Hey everyone, tried building from source on latest It built successfully using the top level build script and the CLI output that it's using the correct tag (dirty) of the kutosis engine. Also a note, since grafana is usually also used with prometheus (e.g ethpandas/optimism) to gather metrics from various services, it would be nice to be able to configure the grafloki grafana to connect to any running prometheus service as part of an enclave (or perhaps move prometheus outside of the enclave all-together and basically observability is handled by kurtosis) such that we don't have 2 grafana instances running: one to gather metrics and one with An additional idea and simple idea would be that while fluentd is the default drive, you could also enable the user to set custom driver -- at least for docker, such that one can use
|
## Description A user reported the grafana container not having access to the bindmounted datasource yaml within the container. This was due to varying permissions from the original tmp file created by the CLI and inherited by the bindmounted file. To get around this, this change gives the grafana container root user which fixed their issue. ## Is this change user facing? YES ### References #2696 (comment)
🤖 I have created a release *beep* *boop* --- ## [1.7.0](1.6.0...1.7.0) (2025-04-17) ### Features * add grafloki to kurtosis config ([#2707](#2707)) ([b6794e1](b6794e1)) * export service logs (Kubenertes) ([#2693](#2693)) ([c00f357](c00f357)) * grafloki start/stop ([#2696](#2696)) ([53d823a](53d823a)) * service update ([#2689](#2689)) ([4cda391](4cda391)) ### Bug Fixes * **backend/kubernetes:** use default KUBECONFIG resolution ([#2672](#2672)) ([379e49b](379e49b)) * docker auth wasn't being used by engine and API ([#2699](#2699)) ([4eea787](4eea787)) * give grafana root access ([#2706](#2706)) ([b8e2fab](b8e2fab)) * remove k8s ingress on stop user services ([#2715](#2715)) ([e31c0d4](e31c0d4)) * return empty deployment if not found ([#2716](#2716)) ([451c70e](451c70e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Description
Implements
kurtosis grafloki start
andkurtosis grafloki stop
. These start and stop grafana and loki instances over Docker and K&s depending on the cluster type. The engine will then be restarted and configured to send enclave logs to the instances.Is this change user facing?
YES
References
#2276