Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

Build pod-checkpointer images for multiple architectures #424

Closed
aaronlevy opened this issue Apr 11, 2017 · 6 comments
Closed

Build pod-checkpointer images for multiple architectures #424

aaronlevy opened this issue Apr 11, 2017 · 6 comments
Labels
area/checkpointer area/distribution lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1

Comments

@aaronlevy
Copy link
Contributor

For kubeadm to make use of the pod-checkpointer, we need to start building container images for upstream supported architectures.

Need a list of the architectures that are required - but opening this issue to track.

/cc @luxas

@luxas
Copy link

luxas commented Apr 16, 2017

amd64, arm, arm64, ppc64le and s390x are the architectures that are needed

Should be as easy as setting GOARCH really. Please prioritize this as using the checkpointer is a necessary requirement for reliable selfhosting in v1.7 👍

@aaronlevy aaronlevy modified the milestone: Next-Release Apr 18, 2017
@luxas
Copy link

luxas commented May 30, 2017

friendly ping @aaronlevy

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 22, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/checkpointer area/distribution lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1
Projects
None yet
Development

No branches or pull requests

5 participants