-
Notifications
You must be signed in to change notification settings - Fork 117
Use the new initContainers field instead of the deprecated annotation #528
Use the new initContainers field instead of the deprecated annotation #528
Conversation
|
Any other interesting changes brought about by the fabric8 upgrade? |
|
@foxish will do some research on that. |
|
rerun integration tests please |
1 similar comment
|
rerun integration tests please |
felixcheung
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this change the required minimum version of k8s?
|
@felixcheung Yes, this change requires k8s 1.6 and up. |
|
Hmm.. as a side note, I couldn't find description on k8s version requirements, could we add to README.md? |
|
@felixcheung good point. I will add to https://github.com/apache-spark-on-k8s/userdocs/blob/master/src/jekyll/running-on-kubernetes.md once this PR is merged. |
|
rerun integration tests please |
|
Doc updates for minimum k8s version requirement in apache-spark-on-k8s/userdocs#18. |
|
LGTM! Will merge EOD if no further comments. |
…apache-spark-on-k8s#528) * Use the new initContainers field in Kubernetes 1.8 * Fixed the integration tests
What changes were proposed in this pull request?
Fixes #524. Changes to use the new
initContainersfield instead of the deprecated annotation, support of which is dropped as of Kubernetes 1.8. This requires updating the version of the fabric8 kubernetes-client.