-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.5] Bug 1848785: Fetch latest upstream patches #30
[release-4.5] Bug 1848785: Fetch latest upstream patches #30
Commits on Jun 19, 2020
-
Configuration menu - View commit details
-
Copy full SHA for e822c4c - Browse repository at this point
Copy the full SHA e822c4cView commit details -
prow.sh: use 1.3.0 hostpath driver for testing
The final 1.3.0 release of the hostpath driver really uses the 1.3.0 driver image in its deployment, in contrast to the previous -rc candidates which still used 1.2.0.
Configuration menu - View commit details
-
Copy full SHA for e6c1dce - Browse repository at this point
Copy the full SHA e6c1dceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 310bc7c - Browse repository at this point
Copy the full SHA 310bc7cView commit details -
build for multiple platforms only in CI, add s390x
Developers should not be forced to build for all platforms by default. We also don't want to copy-and-paste the go invocation for each new platform. To address both, the target platform(s) are now configurable via BUILD_PLATFORMS and additional platforms are only enabled in the Prow CI. For now this serves as a test that the source actually compiles for multiple platforms. Building images for different target platforms is a different problem.
Configuration menu - View commit details
-
Copy full SHA for 2959d37 - Browse repository at this point
Copy the full SHA 2959d37View commit details -
Configuration menu - View commit details
-
Copy full SHA for 848599c - Browse repository at this point
Copy the full SHA 848599cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b3176d - Browse repository at this point
Copy the full SHA 4b3176dView commit details -
Update snapshotter to version 2.0.1
Signed-off-by: Grant Griffiths <grant@portworx.com>
Configuration menu - View commit details
-
Copy full SHA for deea989 - Browse repository at this point
Copy the full SHA deea989View commit details -
Configuration menu - View commit details
-
Copy full SHA for a9b0c06 - Browse repository at this point
Copy the full SHA a9b0c06View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9d1c777 - Browse repository at this point
Copy the full SHA 9d1c777View commit details -
Add .prow.sh to enable prow jobs
Change-Id: I1142fc76b939c03ba05070179b5ab9574c096571
Configuration menu - View commit details
-
Copy full SHA for 61140cb - Browse repository at this point
Copy the full SHA 61140cbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4f97fc8 - Browse repository at this point
Copy the full SHA 4f97fc8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 89a7eeb - Browse repository at this point
Copy the full SHA 89a7eebView commit details -
Change-Id: I369683a10673e9da15998ddd9056890db6154b69
Configuration menu - View commit details
-
Copy full SHA for 8d2f882 - Browse repository at this point
Copy the full SHA 8d2f882View commit details -
Configuration menu - View commit details
-
Copy full SHA for c8f1238 - Browse repository at this point
Copy the full SHA c8f1238View commit details -
Support local snapshot RBAC for pull jobs
Signed-off-by: Grant Griffiths <grant@portworx.com>
Configuration menu - View commit details
-
Copy full SHA for 3a09d7d - Browse repository at this point
Copy the full SHA 3a09d7dView commit details -
Configuration menu - View commit details
-
Copy full SHA for cba5fbb - Browse repository at this point
Copy the full SHA cba5fbbView commit details -
cloud build: initial set of shared files
The approach taken here extends the existing support for cross-compiling binaries on the build host and specifying the Go compiler: Go is installed if needed (as in Prow testing), binaries are build on the host, then one image is created for each platform, and finally those are combined into a single multi-architecture image.
Configuration menu - View commit details
-
Copy full SHA for 5b0bab0 - Browse repository at this point
Copy the full SHA 5b0bab0View commit details -
build.make: fix push-multiarch ambiguity
"make push-multiarch" matched both push-multiarch and push-%. This seems to be none-deterministic and in at least one repo (external-provisioner), make picked the wildcard rule which then failed because there is no "multiarch" command. This ambiguity gets resolved by instantiating the wildcard rules only for existing commands. The advantage also is that "make push-no-such-command" will fail with an obvious "No rule to make target 'push-no-such-command'" instead of attempting to build the command.
Configuration menu - View commit details
-
Copy full SHA for def9d81 - Browse repository at this point
Copy the full SHA def9d81View commit details -
build.make: properly declare push-multiarch
It's not a real file and thus should better be marked as phony.
Configuration menu - View commit details
-
Copy full SHA for 67b4ef4 - Browse repository at this point
Copy the full SHA 67b4ef4View commit details -
build.make: optional inclusion of Windows in multiarch images
Most repos inherit the default BUILD_PLATFORMS, which includes Windows, but don't have the necessary Dockerfile.Windows yet. To simplify the rollout of multiarch image builds, Windows binary building continues to be tested (i.e. BUILD_PLATFORMS remains unchanged), but push-multiarch skips Windows if the Dockerfile.Windows is missing.
Configuration menu - View commit details
-
Copy full SHA for 1a8f5d4 - Browse repository at this point
Copy the full SHA 1a8f5d4View commit details -
cloud build: initialize support for running commands in Dockerfile
If the Dockerfile needs to run some command, that step fails unless QEMU is set up properly first: failed to solve: rpc error: code = Unknown desc = failed to load LLB: runtime execution on platform linux/ppc64le not supported
Configuration menu - View commit details
-
Copy full SHA for 23fe0ff - Browse repository at this point
Copy the full SHA 23fe0ffView commit details -
cloud build: k8s-staging-sig-storage
As discussed in kubernetes/k8s.io#943, we want to consolidate under k8s-staging-sig-storage.
Configuration menu - View commit details
-
Copy full SHA for a2d3909 - Browse repository at this point
Copy the full SHA a2d3909View commit details -
Configuration menu - View commit details
-
Copy full SHA for 93ef622 - Browse repository at this point
Copy the full SHA 93ef622View commit details -
Allow to set custom permissions for the mounted folder
For RWX volume, kubelet does not perform recursive ownership/permission change. The heuristics that kubelet uses is being modified via - kubernetes/enhancements#1682 Having said that, for RWX volumes which are made available via NFS protocol, using fsGroup is not recommended because if there are 2 pods that are trying to use same volume but with different fsGroup then one pod may lock out the other pod. To avoid this, we must be able to set the folder permissions to 777. This commit adds a cli option --mount-permissions, that allows to define custom permissions. If the value is not specified, then default permissions will be kept. Cherry-picked from: kubernetes-csi#36
Configuration menu - View commit details
-
Copy full SHA for b345251 - Browse repository at this point
Copy the full SHA b345251View commit details