Resources deleted in cluster are not removed from Clouddriver's cache

[mattgogerly]

Issue Summary:

If a resource (e.g. ReplicaSet) is deleted in a cluster but not by Spinnaker, the record in the DB is not purged. As a result the resource continues to display in Deck, even though clicking on it returns a 404.

Cloud Provider(s):

Kubernetes

Environment

Spinnaker running on Kubernetes deploying to Kubernetes, backed by MySQL.

Steps to Reproduce:

Deploy a ReplicaSet. Delete it from the cluster manually. Observe the ReplicaSet persists in Deck.

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale