James Strachan

@arschles if you want to play, there's an implementation of `helm upgrade` that works as you describe in this PR: https://github.com/helm/helm/pull/323

@technosophos assuming we went down the road of detecting annotations at installation time, do you think we should use `helm install` command line arguments to enable/disable secret generation? I'd personally...

I've closed the previous PR and raised a new leaner meaner rebased & cherry picked PR: https://github.com/helm/helm/pull/326

@nicolaferraro its shipped in openshift 3.6.0 now so I guess its getting there; its gonna be marked beta for kubernetes 1.8 though am sure there'll be YAML changes ;) https://github.com/kubernetes-incubator/service-catalog...

I'm not yet sure of the difference between the new runtime stuff and non-runtime. e.g. if a `DeploymentConfig` needs a `RoleBinding` to run, then I'd assume that should be part...

yeah - we used to instantiate templates in the mvn plugin; guess its not been used yet in 3.x. Or folks can apply them via `kubernetesApply()` in a pipeline or...

@kameshsampath I saw this come up on IRC recently and never had chance to dive into the use case. So the `fabric8:resource` goal builds resources, at build time, to run...

so try use `mvn fabric8:import` and it should do the trick. We may need to tweak the generated BuildConfig a little to properly use the new `jenkinsPipelineStrategy` if it detects...

FWIW gofabric8 installs things as kubernetes templates. We could have a plugin configuration to force the openshift.yml to be converted to an OpenShift template. I guess it depends if openshift...

FWIW we've added some to this additional repository: ```bash kubeval --additional-schema-locations https://jenkins-x.github.io/jenkins-x-schemas ```