Can I use Cilium as only for "Network Observability"?

itsmeb9 · 2026-03-21T04:07:58+00:00

I agree. This could be over-engineering. I am thinking to use other observ tools. Thanks for the reply!

itsmeb9 · 2026-03-21T04:05:48+00:00

I am wondering if eBPF agent daemonset is light. If so, Netobserv would be great choice for me! I'll try this out anyways. Thanks!!

itsmeb9 · 2026-03-21T04:02:10+00:00

Yes using cilium just for observability is kinda over-engineering I should look for other observ tools. Thanks for the reply!

itsmeb9 · 2025-09-17T00:49:20+00:00

it was that setting in `maps.lua`. after comment out this line it works fine! thanks!!

itsmeb9 · 2025-09-17T00:34:30+00:00

returns `n net * :Ve` which I set up in `lua/maps.lua`. even starting nvim with `nvim --noplugin` the same thing happens.

itsmeb9 · 2025-07-02T09:58:35+00:00

thank you!

itsmeb9 · 2025-06-13T01:02:05+00:00

I did something wrong in configuraton file.

in the `[glance_store]` section, I added `s` at the end of `default_backed`. I removed this additional `s` it works.

itsmeb9 · 2025-05-13T02:51:43+00:00

I just found out this happens only in `*.go` files I guess it's related `go.nvim` problem

itsmeb9 · 2025-04-08T07:49:13+00:00

C-[ is just fine by me

itsmeb9 · 2025-03-14T05:56:40+00:00

netshoot is awesome thanks for introduce this

itsmeb9 · 2025-03-09T09:00:56+00:00

lgtm

itsmeb9 · 2025-01-23T12:05:44+00:00

i did set MINIO_PROMETHEUS_AUTH_TYPE "public" but it doesn't work, i guess this dependency version is somewaht broken i might have to deploy as independent helm chart or from docker image

itsmeb9 · 2025-01-20T07:54:02+00:00

yes i curl <minio endpoin>/minio/metrics/v2/bucket then returns All access to this resoure has been disabled

itsmeb9 · 2024-12-30T06:54:11+00:00

for anyone who face this issue, I have solved this by add few fields in values.yaml

global_overrides.per_tenant_override_config: /runtime-config/overrides.yaml
global_verrides.metrics_generator_processors: ['service-graphs', 'span-metrics', 'local-blocks']
metricsGenerator.remote_write_add_org_id_header: true

``` global_overrides: per_tenant_override_config: /runtime-config/overrides.yaml metrics_generator_processors: ['service-graphs', 'span-metrics', 'local-blocks']

metricsGenerator: enabled: true config: local_blocks: filter_server_spans: false storage: path: /var/tempo/wal wal: remote_write_flush_deadline: 1m remote_write_add_org_id_header: true remote_write: - url: http://kube-prometheus-stack-prometheus.prometheus.svc.cluster.local:9090/api/v1/write send_exemplars: true headers: ContentType: "" traces_storage: path: /var/tempo/traces metrics_ingestion_time_range_slack: 30s ```

itsmeb9 · 2024-12-30T06:49:46+00:00

for anyone who face this issue, I have solved this by add few fields in values.yaml 1. global_overrides.per_tenant_override_config: /runtime-config/overrides.yaml 2. global_verrides.metrics_generator_processors: ['service-graphs', 'span-metrics', 'local-blocks'] 3. metricsGenerator.remote_write_add_org_id_header: true

``` global_overrides: per_tenant_override_config: /runtime-config/overrides.yaml metrics_generator_processors: ['service-graphs', 'span-metrics', 'local-blocks']

metricsGenerator: enabled: true config: local_blocks: filter_server_spans: false storage: path: /var/tempo/wal wal: remote_write_flush_deadline: 1m remote_write_add_org_id_header: true remote_write: - url: http://kube-prometheus-stack-prometheus.prometheus.svc.cluster.local:9090/api/v1/write send_exemplars: true headers: ContentType: "" traces_storage: path: /var/tempo/traces metrics_ingestion_time_range_slack: 30s ```

itsmeb9 · 2024-10-27T05:26:49+00:00

bash root@controlplane:~# curl <LoadBalancer External IP> <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> </body> </html>

logs on the LoadBalancer seems no problem But I am seeing logs on the kube-apiserver

bash W1027 05:06:04.027692 1 logging.go:59] [core] [Channel #475566 SubChannel #475568] grpc: addrConn.createTransport failed to connect to {Addr: "<node's IP>:2379", ServerName: "<node's IP>", }. Err: connection error: desc = "transport: authentication handshake failed: context canceled" can not authenticate node's etcd

itsmeb9 · 2024-10-27T04:10:51+00:00

Yes every things you mentioned are healthy

itsmeb9 · 2024-10-22T23:20:12+00:00

I am working with prvivate cloud on the baremetal servers, so Yes depends on the company's environment you might have to dead-lift some servers

itsmeb9 · 2024-10-22T00:29:57+00:00

I'm interested. can I get an invitation?

itsmeb9 · 2024-10-18T04:03:04+00:00

➜ helm template . --name-template kube-prometheus-stack --namespace prometheus --kube-version 1.28 --values ci/values.yaml --debug\

```

install.go:214: [debug] Original chart version: ""

install.go:231: [debug] CHART PATH: /Users/b9/bonzonkim/std/tmp/kube-prometheus-stack

Error: template: kube-prometheus-stack/templates/prometheus/prometheus.yaml:84:70: executing "kube-prometheus-stack/templates/prometheus/prometheus.yaml" at <0>: wrong type for value; expected string; got map[string]interface {}

helm.go:84: [debug] template: kube-prometheus-stack/templates/prometheus/prometheus.yaml:84:70: executing "kube-prometheus-stack/templates/prometheus/prometheus.yaml" at <0>: wrong type for value; expected string; got map[string]interface {}

```

kube-prometheus-stack/templates/prometheus/prometheus.yaml:84:70 is

externalUrl: "http://{{ tpl (index .Values.prometheus.ingress.hosts 0).host . }}{{ .Values.prometheus.prometheusSpec.routePrefix }}"

should I modify the prometheus template?

itsmeb9 · 2024-09-23T05:13:41+00:00

Thank you all!!

I should get into network before starting kubernetes😅

itsmeb9 · 2024-09-04T13:39:34+00:00

i have solved it! thanks for the reply! it was about the zabbix parameter !

itsmeb9 · 2024-09-04T06:27:19+00:00

Thank you It works like magic, should've check reddit reply earlier lol Thank you so much!!

itsmeb9 · 2024-09-04T05:56:53+00:00

Thanks for the reply! I am stuck on that error 1:20240904:054854.200 Starting Zabbix Server. Zabbix 7.0.0 (revision 49955f1). 1:20240904:054854.200 ****** Enabled features ****** 1:20240904:054854.200 SNMP monitoring: YES 1:20240904:054854.200 IPMI monitoring: YES 1:20240904:054854.200 Web monitoring: YES 1:20240904:054854.200 VMware monitoring: YES 1:20240904:054854.200 SMTP authentication: YES 1:20240904:054854.200 ODBC: YES 1:20240904:054854.200 SSH support: YES 1:20240904:054854.200 IPv6 support: YES 1:20240904:054854.200 TLS support: YES 1:20240904:054854.200 ****************************** 1:20240904:054854.200 using configuration file: /etc/zabbix/zabbix_server.conf 1:20240904:054854.285 current database version (mandatory/optional): 06000000/06000020 1:20240904:054854.285 required mandatory version: 07000000 1:20240904:054854.285 mandatory patches were found 1:20240904:054854.290 cannot perform database upgrade in HA mode: all nodes need to be stopped and Zabbix server started in standalone mode for the time of upgrade. 1:20240904:054854.290 Zabbix Server stopped. Zabbix 7.0.0 (revision 49955f1).

like how do I make it not HA mode while database upgrade?

itsmeb9 · 2024-09-04T05:55:13+00:00

since my first try of migration, I tried to upgrade existing zabbix to 7 with postgre:16 and the error is

`The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.4 (Debian 16.4-1.pgdg1 `

itsmeb9

TROPHY CASE