Use Kubernetes 1.11 CRD status sub-resource

[stefanprodan]

• drop compatibility with Kubernetes 1.10
• add status and additional printer columns to Canary CRD
• use CRD UpdateStatus for Canary status updates
• skip readiness checks if the canary analysis is not running
• rename status state to phase (Initialized, Progressing, Succeeded, Failed)
• add canary weight to status

Canary status:

kubectl describe canary

Status:
  Canary Weight:         15
  Failed Checks:         5
  Last Applied Spec:     eyJjb250YWluZXJz.....
  Last Transition Time:  2019-01-16T13:47:16Z
  Phase:                 Progressing

Additional printer columns:

kubectl get canaries --all-namespaces

NAMESPACE   NAME      STATUS        WEIGHT   LASTTRANSITIONTIME
test        podinfo   Progressing   15       2019-01-16T14:05:07Z
prod        frontend  Succeeded     0        2019-01-15T16:15:07Z
prod        backend   Failed        0        2019-01-14T17:05:07Z

Fix #11

[codecov-io]

Codecov Report

Merging #29 into master will decrease coverage by 0.53%.
The diff coverage is 57.37%.

@@            Coverage Diff            @@
##           master     #29      +/-   ##
=========================================
- Coverage   49.64%   49.1%   -0.54%     
=========================================
  Files           8       8              
  Lines         987    1010      +23     
=========================================
+ Hits          490     496       +6     
- Misses        416     431      +15     
- Partials       81      83       +2

Impacted Files	Coverage Δ
pkg/controller/router.go	86.15% <100%> (+0.07%)	⬆️
pkg/controller/recorder.go	81.63% <100%> (ø)	⬆️
pkg/controller/scheduler.go	22.22% <15.78%> (-0.82%)	⬇️
pkg/controller/controller.go	6.91% <66.66%> (ø)	⬆️
pkg/controller/deployer.go	57.73% <70%> (-1.47%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1b84cd...1d31b5e. Read the comment docs.