This commit elaborates on how to deploy nfs-client as well as modify and
doing changes to the files before said deployment, updating the
README.md to make deployment easier.
(cherry picked from commit e2bee920ee)
RBCA is no longer alpha and thus `v1` is only needed.
Service account has been added to deployment.yaml in order to get the
example to work correctly.
(cherry picked from commit 95186ce5dc)
- Reorganized to use Makefile for building
- Added arm container for use in ARM based kubernetes clusters
Signed-off-by: Niklas Wik <niklas.wik@iki.fi>
(cherry picked from commit 166056da73)
- Importing API types from k8s.io/api
- Update client-go and apimachinery version
- Remove lib/helper and use the kubernetes one temporary
(cherry picked from commit 53163dd4b2)
Adds example configuration files for clusters that have RBAC enabled
(1.6) or OpenShift users.
This is mostly a cut and paste job from the EFS example.
(cherry picked from commit a82645d4ec)
It used to be necessary to override from where the E2E suite came on a
case-by-case basis (initially, testing was using a more recent suite
against an older Kubernetes). This should never become necessary again
and the lack of a specific entry for 1.18 already had the unintended
effect that Kubernetes 1.18 was tested with the suite from master, so
overall it is better to always use the E2E suite which matches
Kubernetes.
Kubernetes 1.19.0 uses Go 1.15, but refers to it as 1.15.0. This broke
both the check whether we need to install 1.15 (because "go version"
reports 1.15, which didn't match 1.15.0) and then downloading the
release archive (because the URL also only uses 1.15).
Go 1.15 was released and is the major version that Kubernetes 1.19.0
is going to use. There are probably bugs in the older 1.13.3 that were
fixed, so we should update.
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
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.
"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.
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.
Philippe Gagnon
Matthew Wong
Peter Grant
Charlie Drage
Ian Chakeres
Lawrence Dudley
Niklas Wik
Steve Leon
Clayton O'Neill
Jackie Li
Michelle Au
Kubernetes Prow Robot
Patrick Ohly
Ashish Ranjan
namrata-ibm
Animesh Kumar
Yibo Cai