kubernetes: bouncer not found

[usma0118]

Scenario:
Scale up/down nginx hosted on kubernetes.

pod ip: 10.6.163.53

time="2024-09-05T16:05:16+02:00" level=error msg="while fetching bouncer info: ent: bouncer not found" ip=10.6.163.53 time="2024-09-05T16:05:16+02:00" level=info msg="10.6.163.53 - [Thu, 05 Sep 2024 16:05:16 CEST] \"GET /v1/decisions?ip=*.*.*.* HTTP/1.1 403 174.398µs \"crowdsec-openresty-bouncer/v1.0.2\" \""

lapi still shows this as
INGRESS 10.6.100.163 ✔️ 2024-09-01T20:58:28Z crowdsec-openresty-bouncer v1.0.2 api-key

Ingress logs:
[error] 188#188: *50208 [lua] crowdsec.lua:600: Allow(): [Crowdsec] bouncer error: Http error 403 while talking to LAPI (http://crowdsec-service.watchtower.svc.cluster.local:8080/v1/decisions?ip=10

[usma0118]

@LaurenceJJones any feedback?

[LaurenceJJones]

@LaurenceJJones any feedback?

Currently not, we are working on release of 1.6.3 once this is completed I will have sometime to test this.

However, a preface note is ent: bouncer not found is when the LAPI does not have the bouncer API key within the database, so I would check:

• Exec into the ingress pod and check the configuration file:
  • Has api key within the file
  • API key is pre populated by BOUNCER_KEY_<name> environment variables set on LAPI env

[usma0118]

@LaurenceJJones any feedback?

Currently not, we are working on release of 1.6.3 once this is completed I will have sometime to test this.

However, a preface note is ent: bouncer not found is when the LAPI does not have the bouncer API key within the database, so I would check:

• Exec into the ingress pod and check the configuration file:

  • Has api key within the file
  • API key is pre populated by BOUNCER_KEY_<name> environment variables set on LAPI env

Bouncer key is added via env variable. (two keys are added).
compain is only for one key.

Based on https://discourse.crowdsec.net/t/bouncer-not-found/1719 i have pruned key and restarted lapi pod and things have started working again.

Will keep an eye.