text: Title: Failure in Conformance test - Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]
  Body: /kind bug
  
  Don't think this is related to, but not sure  https://github.com/kubernetes/kubernetes/issues/60745 .
  
  ```
  Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.7-gke.5", GitCommit:"9b635efce81582e1da13b35a7aa539c0ccb32987", GitTreeState:"clean", BuildDate:"2018-08-02T23:42:40Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
  ```
  I'm thinking the `Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]` should be moved out of conformance... but not quite sure yet. 
  
  ## 
  - Sonubuoy e2e results link:  https://scanner.heptio.com/519c1537b4a7fa4ad0855f621b2c678f/diagnostics/
  
  - Another nice thing to fix: 
  
  The fact that we upgrade from a serv-hostname to a redis image is kinda weird.  Why redis ?  From a security perspective, the smaller the dependent image the easier it is to confirm this test has a 'true positive' result set. 
  ```Aug 27 13:53:55.394: INFO: Wrong image for pod: daemon-set-26bm5. Expected: gcr.io/kubernetes-e2e-test-images/redis-amd64:1.0, got: gcr.io/kubernetes-e2e-test-images/serve-hostname-amd64:1.0.```
  
  cc @kubernetes/sig-testing 
  
  