Kamus controller always restarting

Describe the bug After update to Kamus version 0.6.6.0 (chart version 0.4.7) controller is terminating the process after watching for KamusSecret so pod is always restarting and at some moment probes fails so pod enters on CrashLoopBackOff state.

{
   "Timestamp":"2020-05-11T10:22:44.7789456+00:00",
   "Level":"Information",
   "MessageTemplate":"Starting watch for KamusSecret V1Alpha2 events",
   "Properties":{
      "SourceContext":"CustomResourceDescriptorController.HostedServices.V1Alpha2Controller"
   }
}
Hosting environment: Production
Content root path: /home/dotnet/app
Now listening on: https://0.0.0.0:8888
Now listening on: http://0.0.0.0:9999
Application started. Press Ctrl+C to shut down.
{
   "Timestamp":"2020-05-11T10:24:33.8513234+00:00",
   "Level":"Information",
   "MessageTemplate":"Watching KamusSecret events completed, terminating process",
   "Properties":{
      "SourceContext":"CustomResourceDescriptorController.HostedServices.V1Alpha2Controller"
   }
}
Application is shutting down...

Versions used Kamus (API images): 0.6.6.0 Kamus CLI: 0.3.0 Chart version: 0.4.7 KMS provider: AwsKms Kubernetes flavour and version: 1.14.9-aws.8

Expected behavior Kamus controller not restarting and be in a healthy state.

[shaikatz]

Hi, @MihaiAnei thanks for the info. There are 2 issues here as you pointed out.

The first one, that we log conflict each time we come up, it’s just a cosmetic issue and nothing that hurt functionality.

The second one is probably a regression introduced by the Kubernetes client we’ve updated, and it stopped honoring the long timeout we provide to the HttpClient we use. It shuts off the stream too fast, and then the observable receives a completed event as you pointed out, and terminate the container.

I’ll try to work on a solution for both issues soon.

[shaikatz]

Great, you can expect restart once an hour since this is the timeout we provide to the watcher.