Greg
05/21/2025, 2:24 PMca-certificates.crt file, and then mount that into the fluent bit container at /etc/ssl/certs/ca-certificates.crt which I understand to be the correct location.
However, unless I set tls.ca_file: "/etc/ssl/certs/ca-certificates.crt" for the prometheus output, I get SSL errors.Greg
05/21/2025, 2:24 PMGreg
05/21/2025, 2:26 PM-debug build of fluent-bit, I can open a shell and use curl to check if the CA is set up correctly.Greg
05/21/2025, 2:27 PM/etc/ssl/certs/ca-certificates.crt then curl works as expectedGreg
05/21/2025, 2:28 PM/etc/ssl/certs/ca-certificates.crt should work.Greg
05/21/2025, 2:28 PMGreg
05/21/2025, 2:29 PMGreg
05/21/2025, 2:29 PMtls.ca_file on the prom output, then it worksPat
05/21/2025, 2:30 PMPat
05/21/2025, 2:30 PMPat
05/21/2025, 2:31 PMGreg
05/21/2025, 2:32 PMGreg
05/21/2025, 2:32 PMtls.ca_file: "/etc/ssl/certs/ca-certificates.crt" to the prom outputGreg
05/21/2025, 2:33 PM- name: prometheus_remote_write
match: metrics.*
host: ${PROMETHEUS_HOST}
uri: /api/prom/push
port: 443
tls: on
tls.verify: on
tls.ca_file: "/etc/ssl/certs/ca-certificates.crt"
http_user: ${PROMETHEUS_USER_ID}
http_passwd: ${GRAFANA_TOKEN}Pat
05/21/2025, 2:33 PMGreg
05/21/2025, 2:34 PMPat
05/21/2025, 2:34 PMGreg
05/21/2025, 2:35 PMI think the docs say you do need to define it - otherwise it defaults to the empty stringBut this works for regular HTTPS endpoints, which are not self signed
Pat
05/21/2025, 2:35 PMGreg
05/21/2025, 2:36 PMPat
05/21/2025, 2:36 PMGreg
05/21/2025, 2:37 PMPat
05/21/2025, 2:38 PMGreg
05/21/2025, 2:40 PMAnurag Gupta
05/21/2025, 2:45 PMtls.crt_fileAnurag Gupta
05/21/2025, 2:45 PMGreg
05/21/2025, 2:50 PMGreg
05/21/2025, 2:51 PMGreg
05/21/2025, 2:51 PMGreg
05/22/2025, 10:45 AM/etc/ssl/certs/ files from where I updated the CA, then it works okayPat
05/22/2025, 11:20 AMPat
05/22/2025, 11:20 AMGreg
05/22/2025, 11:26 AM728616e5.0, which is a certificate fileGreg
05/22/2025, 11:28 AM/etc/ssl/certs has a bunch of file, mostly sym links to /usr/share/ca-certificates etc.Pat
05/22/2025, 11:28 AMGreg
05/22/2025, 11:31 AMupdate-ca-certificates it takes your CA and adds it to /etc/ssl/certs/ca-certificates.crt .
ca-certificates.crt should then have everything needed, and indeed to can pass this to the output with tls.ca_file: "/etc/ssl/certs/ca-certificates.crt" and it will work.Greg
05/22/2025, 11:31 AMGreg
05/22/2025, 11:32 AMPat
05/22/2025, 11:32 AMGreg
05/22/2025, 11:33 AM/etc/ssl/certs/ dir, including all sym link targetsPat
05/22/2025, 11:33 AMPat
05/22/2025, 11:33 AMGreg
05/22/2025, 11:34 AMIs that file part of the image then?Yes, I believe the image (including the non-debug distroless image), has a "complete" (?) debian based ssl file system layout
Greg
05/22/2025, 11:35 AMssl needs to be well configured, but how this is done is apparently different between distrosPat
05/22/2025, 11:37 AMGreg
05/22/2025, 11:38 AMPat
05/22/2025, 11:39 AMGreg
05/22/2025, 11:39 AMPat
05/22/2025, 11:41 AMGreg
05/22/2025, 11:46 AMtls.ca_file defaulted to /etc/ssl/certs/ca-certificates.crt , and was documented as such, it would give a hint as to how to override this (mounting over that file), and such a simple, single mount would then work for my use case.Greg
05/22/2025, 11:49 AMPat
05/22/2025, 12:28 PMGreg
05/22/2025, 12:29 PM