-
Notifications
You must be signed in to change notification settings - Fork 242
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
Remove upx from the kubeone-e2e image #1443
Conversation
Signed-off-by: Marko Mudrinić <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: 76092c4752132b9fb99bbb1aa074236b3ad9b201
|
/retest |
/test pull-kubeone-e2e-aws-upgrade-1.20-1.21 |
* upstream/master: Increase the minimum Kubernetes version to v1.19 (kubermatic#1466) Automatically deploy CSI plugin and driver for supported providers, and add support for OpenStack Cinder CSI (kubermatic#1465) Add support for versioned images (kubermatic#1463) Add changelog for v1.3.0-alpha.1 release (kubermatic#1460) Use kubeadm/v1beta3 API for Kubernetes 1.22+ clusters (kubermatic#1457) Enable PodSecurity admission controller for 1.22 clusters (kubermatic#1456) Add Kubernetes 1.22 tests and remove 1.18 tests (kubermatic#1447) Extend restart API server script to handle failing crictl logs (kubermatic#1448) Remove upx from the kubeone-e2e image (kubermatic#1443) terraform/vsphere: Inherit firmware settings from the template VM (kubermatic#1445) Update machine-controller to v1.35.1 (kubermatic#1440) Redirect push-e2e-image job failures to the appropriate channel (kubermatic#1442) Update images (kubermatic#1441) Azure CCM (kubermatic#1438) Upgrade machine-controller to v1.35.0 (kubermatic#1437) Check if unzip is present on the current system. (kubermatic#1435)
What this PR does / why we need it:
The Kubernetes 1.22 binaries are not compatible with
upx
, so we decided to stop using it.Does this PR introduce a user-facing change?:
/assign @kron4eg