Reflection is to slow. Pod goes into ImagePullBackOff

[redx177]

I am using Gitops and on pull requests of my app I create a new environment to test the PR. I will create a namespace and the required pods. But until the kubernetes-reflector replicated the imagepullsecret, the pods already went into ImagePullBackOff state.

kubernetes-reflector logs show:

2022-05-04 12:38:13.495 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:35:19.1644564. Faulted: False.
2022-05-04 12:38:13.504 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-04 12:38:13.768 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 0 - Updated 0 - Deleted 0 - Validated 9.
2022-05-04 13:12:02.234 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:57:19.8038623. Faulted: False.
2022-05-04 13:12:02.235 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-04 13:15:50.371 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:38:42.5296269. Faulted: False.
2022-05-04 13:15:50.372 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-04 13:37:29.214 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:59:15.7097240. Faulted: False.
2022-05-04 13:37:29.214 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-04 13:37:29.554 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 0 - Updated 0 - Deleted 0 - Validated 9.
2022-05-04 13:44:03.810 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:32:01.5747240. Faulted: False.
2022-05-04 13:44:03.810 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-04 14:03:22.530 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:47:31.9659988. Faulted: False.
2022-05-04 14:03:22.530 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-04 14:14:12.683 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:30:08.6807986. Faulted: False.
2022-05-04 14:14:12.683 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-04 14:30:02.454 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:52:33.0470167. Faulted: False.
2022-05-04 14:30:02.454 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-04 14:30:02.562 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 9.
2022-05-04 14:30:02.600 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created my-new-ns/my-secret as a reflection of my-ns/my-secret
2022-05-04 14:39:40.142 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:36:17.6118289. Faulted: False.
2022-05-04 14:39:40.142 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources 

As I see it, the reflector tried to reflect secrets at 12:38, 13:37 and 14:30. So in the worst case, I'd have to wait for almost an hour until the secret get reflected.

Is this how the reflector works, or have I done something wrong? Can the reflector maybe get notified when a new namespace has been created and then "instantly" reflect secrets? Or alternatively can it check for new namespaces every 30 seconds or so?

[winromulus]

Hi @redx177

Reflector does not poll but listens to events from k8s to instantly process reflections. The session in the logs show when a subscription has started and when it closes (k8s closes event subscriptions periodically). From the logs you have posted, the event about the new namespace came in at 14:30:02.562 and was created at 14:30:02.600 I'm not sure what happened to the scheduling, but I assure you that reflector immediately reacts to notifications about secret changes or namespace changes. There have been issues with k8s in the past where it did not report events immediately OR at all, so it would be very useful to let me know which version of k8s you have.

What you can do in the meantime is to open a terminal and stream the logs of reflector and open a second terminal and manually create a namespace and see the live reflection (the logs should immediately show a new reflection being created). If there is a delay of more than 2 seconds, we can dig more.

[redx177]

Thank you for the quick reply and sorry for my lack of knowledge. It seems to work nicely. I've tailed the pod logs with kubectl logs --tail=100 -f reflector-pod-name -n my-namespace and created a new namespace. It the secret got reflected instantly.

So I guess it must be a problem with my gitops tooling (ArgoCD). I will investigate further. Sorry for the hassle.

Btw. This tool is awesome. Thank you so much for sharing it <3

[redx177]

hm... it seems to not work all the time for me.

Test 1. It first worked instantly when I've tested it before and have written the previous comment. Test 2. Then I've tested it again and it was slow. See explanation and the log below in this comment. Test 3. And after that I've tested it again and it worked flawlessly again. See log below in this comment Test 4. It is back to slow. Explanation below.

We are working with Rancher.

• Rancher 2.6.0
• K8s 1.21.4

=== Test 2 === This one was working slow.

I've created 3 namespaces:

• pr-test1: Created at 09:37:57 UTC manually via kubectl create namespace pr-test1
• pr-test2: Created at 09:38:59 UTC manually via Rancher GUI. This will set the Rancher project the namespace belongs to.
• pr-my-feature: Created at 09:36:48 UTC automatically via ArgoCD.

I start them with the prefix "pr-" because the secret I would like to reflect has a rule that it only reflects to namespaces which start with "pr-"

Log showed:

2022-05-05 09:27:42.107 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:30:45.8178055. Faulted: False.
2022-05-05 09:27:42.107 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-05 09:27:42.246 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 0 - Updated 0 - Deleted 0 - Validated 12.
2022-05-05 09:31:56.964 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:39:24.5916685. Faulted: False.
2022-05-05 09:31:56.964 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-05 09:37:15.249 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:44:13.7247084. Faulted: False.
2022-05-05 09:37:15.249 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-05 10:10:36.915 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:33:21.6660470. Faulted: False.
2022-05-05 10:10:36.915 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-05 10:15:12.746 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:47:30.6388918. Faulted: False.
2022-05-05 10:15:12.746 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-05 10:15:12.887 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 3 - Updated 0 - Deleted 0 - Validated 10.
2022-05-05 10:15:12.939 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-my-feature/my-secret as a reflection of my-ns/my-secret
2022-05-05 10:15:13.004 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test1/my-secret as a reflection of my-ns/my-secret
2022-05-05 10:15:13.156 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test2/my-secret as a reflection of my-ns/my-secret
2022-05-05 10:24:37.487 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:52:40.5227356. Faulted: False.
2022-05-05 10:24:37.487 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-05 10:51:01.679 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:40:24.7640228. Faulted: False.
2022-05-05 10:51:01.679 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources

=== Test 3 === I've created multiple namespaces. pr-test1, pr-test3 and pr-test4 I've created manually with kubectl. pr-my-feature was created with ArgoCD (it existed before already and I've deleted it. Don't know if that changes anything)

Below is the direct continuation of the log from above. The secrets got reflected instantly.

2022-05-05 10:59:56.402 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:44:43.6556575. Faulted: False.
2022-05-05 10:59:56.402 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-05 10:59:56.529 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected my-ns/my-secret where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 13.
2022-05-05 10:59:56.557 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test3/my-secret as a reflection of my-ns/my-secret
2022-05-05 11:08:07.538 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-my-feature/my-secret as a reflection of my-ns/my-secret
2022-05-05 11:09:33.644 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test1/my-secret as a reflection of my-ns/my-secret
2022-05-05 11:09:52.795 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test3/my-secret as a reflection of my-ns/my-secret
2022-05-05 11:09:57.020 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created pr-test4/my-secret as a reflection of my-ns/my-secret

=== Test 4 === Namespace pr-my-feature2 was created with ArgoCD at 11:31:31 UTC. See command line output from 11:31:48 UTC:

> kubectl describe namespace pr-my-feature2
Name:         pr-my-feature2
Labels:       app=my-app
              argocd.argoproj.io/instance=my-feature2
              field.cattle.io/projectId=p-th5gj
              kubernetes.io/metadata.name=pr-my-feature2
Annotations:  cattle.io/status:
                {"Conditions":[{"Type":"ResourceQuotaInit","Status":"True","Message":"","LastUpdateTime":"2022-05-05T11:31:31Z"},{"Type":"InitialRolesPopu...
              field.cattle.io/projectId: c-gfdcx:p-th5gj
              lifecycle.cattle.io/create.namespace-auth: true
Status:       Active

No resource quota.

No LimitRange resource.

> kubectl get secrets -n pr-my-feature2
NAME                  TYPE                                  DATA   AGE
default-token-mtg5h   kubernetes.io/service-account-token   3      113s

I expect to have the secret my-secret after the kubectl get secrets command at the end. The log from the kubernetes-reflector shows nothing.

[ManuelMueller1st]

I can observe the same behavior in an AWS EKS cluster with k8s 1.21 and Argo CD. But I have no idea how to debug it.

[dkarlovi]

Similar behaviour on AKS, k8s 1.23.5.

1. I have a secret with a wildcard namespace setup and auto-reflection
2. I create a new namespace, the secret should end up in there
3. Check the namespace, secret is not there
4. Delete the reflector pod
5. Check the namespace, the secret is now there (was created as expected on startup, meaning the entire setup is correct)
6. Create another test namespace, the secret is there immediately, works as expected
7. ?
8. Now it doesn't work again with exactly the same namespace names, until I again delete the pod

[dkarlovi]

Sorry for spamming, but I have some logs now.

The namespace was created by Helm at 8:58 UTC:

apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2022-05-30T08:58:01Z"
  labels:
    kubernetes.io/metadata.name: store-demo-review-infra-secrets
    name: store-demo-review-infra-secrets
  name: store-demo-review-infra-secrets
  resourceVersion: "2922145"
  uid: a1d88c0a-8bfb-4c2e-9860-ee1442531847
spec:
  finalizers:
  - kubernetes
status:
  phase: Active

The last few logs from the reflector, you can see that it didn't notice the namespace being created, it just sits there (no logs after 8:51, but checked after the namespace was created)

2022-05-30 08:46:27.714 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:38:27.3678417. Faulted: False.
2022-05-30 08:46:27.714 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-30 08:51:32.022 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:57:18.4978533. Faulted: False.
2022-05-30 08:51:32.022 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources

Now delete the pod, it immediately creates the secrets on startup:

$ kubectl -n emberstack-reflector delete pod reflector-5fc85c9964-mxgwd
$ kubectl -n emberstack-reflector logs reflector-5fc85c9964-gmjkt 
2022-05-30 09:01:00.148 +00:00 [INF] () Starting host
2022-05-30 09:01:00.610 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-30 09:01:00.645 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-30 09:01:00.659 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-30 09:01:01.028 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/app-secrets where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 1.
2022-05-30 09:01:01.136 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-infra-secrets/app-secrets as a reflection of store-demo-templates/app-secrets
2022-05-30 09:01:01.184 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/registry-pull-secret where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 1.
2022-05-30 09:01:01.192 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-infra-secrets/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret

meaning the secrets are correctly configured for auto-reflection into this namespace.

Judging from the way you describe the tool architecture, this means the namespace creation event is not correctly received after a while. Could it be that, after the session is first closed by Kubernetes, the tool doesn't correctly switch monitoring to the new subscription? That would explain why it works at first, but stops "after a while". :thinking:

I've created a namespace before the session reset to test the theory, the secrets got auto-reflected. I'll create another one after I see the session got reset in the reflector logs, if it doesn't work then, I think we have a culprit. Will update here in an hour or so.

Update

OK, it seems we're on to something, but it's not as clear cut as I imagined, here's the logs

2022-05-30 09:26:03.388 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test-before-session-reset/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret
2022-05-30 09:26:03.398 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test-before-session-reset/app-secrets as a reflection of store-demo-templates/app-secrets
2022-05-30 09:43:32.639 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:42:32.0333010. Faulted: False.
2022-05-30 09:43:32.641 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources
2022-05-30 09:44:25.294 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:43:24.6352104. Faulted: False.
2022-05-30 09:44:25.295 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources

# here created store-demo-review-test-after-session-reset @09:45, reflection delayed for 2mins, until the restart (?)

2022-05-30 09:47:13.586 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:46:12.9410373. Faulted: False.
2022-05-30 09:47:13.587 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-30 09:47:13.619 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/app-secrets where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 2.
2022-05-30 09:47:13.633 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test-after-session-reset/app-secrets as a reflection of store-demo-templates/app-secrets
2022-05-30 09:47:13.673 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/registry-pull-secret where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 2.
2022-05-30 09:47:13.681 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test-after-session-reset/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret

# here created store-demo-review-test2-after-session-reset @09:52, reflection immediate

2022-05-30 09:52:15.502 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test2-after-session-reset/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret
2022-05-30 09:52:15.512 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test2-after-session-reset/app-secrets as a reflection of store-demo-templates/app-secrets

# here created store-demo-review-test3-after-session-reset @10:08, reflection immediate

2022-05-30 10:08:21.141 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test3-after-session-reset/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret
2022-05-30 10:08:21.149 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test3-after-session-reset/app-secrets as a reflection of store-demo-templates/app-secrets
2022-05-30 10:14:49.370 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Session closed. Duration: 00:30:24.0749936. Faulted: False.
2022-05-30 10:14:49.370 +00:00 [INF] (ES.Kubernetes.Reflector.Core.ConfigMapWatcher) Requesting V1ConfigMap resources
2022-05-30 10:27:20.794 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:40:07.2076328. Faulted: False.
2022-05-30 10:27:20.794 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-30 10:27:20.838 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/registry-pull-secret where permitted. Created 0 - Updated 0 - Deleted 0 - Validated 5.
2022-05-30 10:27:20.878 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/app-secrets where permitted. Created 0 - Updated 0 - Deleted 0 - Validated 5.
2022-05-30 10:41:35.917 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Session closed. Duration: 00:58:03.2754536. Faulted: False.
2022-05-30 10:41:35.917 +00:00 [INF] (ES.Kubernetes.Reflector.Core.NamespaceWatcher) Requesting V1Namespace resources

# here created store-demo-review-test3-after-session-reset @11:05, reflection delayed 6 mins

2022-05-30 11:14:22.213 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Session closed. Duration: 00:47:01.4186849. Faulted: False.
2022-05-30 11:14:22.213 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretWatcher) Requesting V1Secret resources
2022-05-30 11:14:22.245 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/registry-pull-secret where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 5.
2022-05-30 11:14:22.254 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test4-after-session-reset/registry-pull-secret as a reflection of store-demo-templates/registry-pull-secret
2022-05-30 11:14:22.281 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Auto-reflected store-demo-templates/app-secrets where permitted. Created 1 - Updated 0 - Deleted 0 - Validated 5.
2022-05-30 11:14:22.287 +00:00 [INF] (ES.Kubernetes.Reflector.Core.SecretMirror) Created store-demo-review-test4-after-session-reset/app-secrets as a reflection of store-demo-templates/app-secrets

I guess all secrets are reflected during the session restart, but something prevents the real-time aspect from working.

[stale[bot]]

Automatically marked as stale due to no recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[redx177]

Am I allowed to push-up this issue?

[stale[bot]]

Removed stale label.

[stale[bot]]

Automatically marked as stale due to no recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[redx177]

push

[stale[bot]]

Removed stale label.

[winromulus]

The new version (work in progress) should fix this issue.

[nerem]

We also ran into this issue. Any update, when we can expect the fix? Thank you very much in advance!

[mhienle]

Same issue here, we would highly appreciate a fix being released. Thanks for the great work!

[jmc000]

Ran into the same issue here, looking forward to the release. Thanks!

[Compy]

Any ETA on a release? I really don't want to have to pull the revamp branch and create a custom image. Excited to get this going!

[ManuelMueller1st]

The new version (work in progress) should fix this issue.

How can we support you on this?

[jalibu]

We have the same issue and would love to get a fixed version soon :-)

[winromulus]

Please try the new version. This issue should be fixed. Please reopen if this is still a problem (some scenarios are extremely hard to reproduce and help is required to validate the fix).

[redx177]

Thank you so much <3 Just saw this now and will let you know how it goes.

[redx177]

Till now it works great <3