nats-io / nack

NATS Controllers for Kubernetes (NACK)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

gRPC debug Output

Zetanova opened this issue · comments

Using charts:
nack-0.19.0 0.8.0
nats-0.19.1 2.9.8

The controller is working without TLS, authentication and accounts,
but after enabling TLS, auth and using accounts,
the controller can start and connect to the nats cluster successfully over his defined creds of SYS account,
but to create a consumer CRD it simply fails with:
controller.go:416] failed to process consumer: failed to check if consumer exists: context deadline exceeded

I created the stream 'test' in account 'SANDBOX' over nats.exe from my dev machine.

What I tried so fair:

  • I tried to enable debug output of the controller with the -v=10 parameter, but it prints only requests/responses to the kube API
  • Remove the SYS creds of the controller helm and it starts with an auth error
  • Create an Account CRD 'SANDBOX' with and without the server-url, tls, creds options
  • Added the tester.creds of acccount 'SANDBOX' to the secret of the nack-helm
  • Added server-url, tls, creds-NAME to 'tester.creds' to the Consumer CRD

Nothing worked and the only error logged of the controller is:
controller.go:416] failed to process consumer: failed to check if consumer exists: context deadline exceeded

Can't find any example that uses simple creds files and don't know how and what the controller needs to use and connect to the proper nats account. The lack of debug output from the controller to the nats server does not help.

Need help