-
Notifications
You must be signed in to change notification settings - Fork 53
Upgrade the spark-on-k8s-operator module to spark-operator-chart-1.1.15 #minor #232
base: master
Are you sure you want to change the base?
Upgrade the spark-on-k8s-operator module to spark-operator-chart-1.1.15 #minor #232
Conversation
Thank you for opening this pull request! 🙌 These tips will help get your PR across the finish line:
|
12e6bfe
to
755efbf
Compare
Codecov Report
@@ Coverage Diff @@
## master #232 +/- ##
==========================================
+ Coverage 62.50% 63.95% +1.44%
==========================================
Files 142 142
Lines 8849 9365 +516
==========================================
+ Hits 5531 5989 +458
- Misses 2816 2852 +36
- Partials 502 524 +22
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
Cc @akhurana001
LGTM, @akumor weird that the coverage is broken |
go.mod
Outdated
k8s.io/api => k8s.io/api v0.20.2 | ||
k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.20.2 | ||
k8s.io/apimachinery => k8s.io/apimachinery v0.20.2 | ||
k8s.io/apiserver => k8s.io/apiserver v0.20.2 | ||
k8s.io/cli-runtime => k8s.io/cli-runtime v0.20.2 | ||
k8s.io/client-go => k8s.io/client-go v0.20.2 | ||
k8s.io/cloud-provider => k8s.io/cloud-provider v0.20.2 | ||
k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.20.2 | ||
k8s.io/code-generator => k8s.io/code-generator v0.20.2 | ||
k8s.io/component-base => k8s.io/component-base v0.20.2 | ||
k8s.io/cri-api => k8s.io/cri-api v0.20.2 | ||
k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.20.2 | ||
k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.20.2 | ||
k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.20.2 | ||
k8s.io/kube-proxy => k8s.io/kube-proxy v0.20.2 | ||
k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.20.2 | ||
k8s.io/kubectl => k8s.io/kubectl v0.20.2 | ||
k8s.io/kubelet => k8s.io/kubelet v0.20.2 | ||
k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.20.2 | ||
k8s.io/metrics => k8s.io/metrics v0.20.2 | ||
k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.20.2 |
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.
Per this report, we may have to bump the deps to v0.20.11 for all of these...
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.
Unable to display this organization
The organization does not exist, or you do not have permissions to access it.
I can't view that report, but upgrading to v0.20.11 doesn't sound like it will be a problem. I'll look into bumping that version
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.
@EngHabu I pushed a new commit that changed the deps to v0.20.11 but it looks like snyk is still failing
29ce44c
to
1a7784f
Compare
This upgrades the module to the spark-operator-chart-1.1.15 release. https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/commits/spark-operator-chart-1.1.15 Signed-off-by: akumor <[email protected]>
1a7784f
to
3688404
Compare
Signed-off-by: akumor <[email protected]>
3688404
to
3a7f924
Compare
This PR upgrades the spark-on-k8s-operator plugin with the goal of fixing support for defining the podSecurityContext for a SparkApplication created by executing a Spark task.
TL;DR
This upgrades the module to the spark-operator-chart-1.1.15 release.
Type
Are all requirements met?
Complete description
I fixed the bug by upgrading the version of the spark-on-k8s-operator to the most recently tagged release
spark-operator-chart-1.1.15
and updated the spark flyteplugin code to be compatible.Tracking Issue
flyteorg/flyte#2025
Follow-up issue
NA