Andrey Klimentyev

The current approach is extremely simple and efficient since it creates a global API Watch, and cross-references pullSecretReferences with the secrets directly in the memory of the `image-availability-exporter`.

What's in the logs?

How would you define a "new image"? Using Docker Registry API semantics.

@yuripastushenko Are you using the latest `v0.1.13` image? This has been fixed for a long time.

>the next major version, this will raise an error This thing here prompted me to write an issue. Thanks for a quick response!

>Is this another field on the pod spec that would be checked against? Resolve StorageClass's [`provisioner`](https://github.com/kubernetes/api/blob/master/storage/v1/types.go#L40-L41) field and >I'm assuming this would be a config field for the descheduler that...

@armsnyder I've been using your changes to great effect! Thanks! Unfortunately, the PR does not work on the latest master. Tests fail as well. Can you rebase, please?

@nabokihms Can you take a look?

Hi. That won't work, unfortunately. The code itself does not support snapshotting yet. I'll see what can be done on the Go side (this week), and get back to you.

Will be explored in https://github.com/deckhouse/deckhouse/issues/2477