[e2e] clusterctl upgrade testing for EKS

randomvariable commented 3 years ago

/kind feature

Describe the solution you'd like Enable e2e clusterctl upgrade testing for v1alpha4 --> v1beta1 upgrades.

This is not currently possible because the spec requires the locally compiled e2e image to be prestaged on the node, see https://github.com/kubernetes-sigs/cluster-api/pull/5395 for details.

EKS Bootstrap Config doesn't currently allow the user to set commands that should be executed before kubelet starts that will allow the prestaging ( #2771 )

/priority important-soon /area testing

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

Cluster-api-provider-aws version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

randomvariable commented 3 years ago

/milestone v1.0.x

randomvariable commented 3 years ago

/triage accepted

richardcase commented 2 years ago

Moving as the bootstrap command feature isn't quite ready:

/milestone v1.2.0

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

sedefsavas commented 2 years ago

/remove-lifecycle stale

richardcase commented 2 years ago

/lifecycle frozen

richardcase commented 2 years ago

/remove-lifecycle frozen

richardcase commented 2 years ago

/milestone clear

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

richardcase commented 1 year ago

/remove-lifecycle rotten /priority critical-urgent

richardcase commented 1 year ago

/milestone v2.1.0

k8s-triage-robot commented 1 year ago

This issue is labeled with priority/critical-urgent but has not been updated in over 30 days, and should be re-triaged. Critical-urgent issues must be actively worked on as someone's top priority right now.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Deprioritize it with /priority {important-soon, important-longterm, backlog}
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

richardcase commented 1 year ago

/triage accepted

richardcase commented 1 year ago

/assign

richardcase commented 1 year ago

/unassign /milestone v2.x

k8s-triage-robot commented 1 year ago

This issue is labeled with priority/critical-urgent but has not been updated in over 30 days, and should be re-triaged. Critical-urgent issues must be actively worked on as someone's top priority right now.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Deprioritize it with /priority {important-soon, important-longterm, backlog}
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

dlipovetsky commented 1 year ago

/help /triage accepted

k8s-ci-robot commented 1 year ago

@dlipovetsky: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2828): >/help >/triage accepted Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 1 year ago

This issue is labeled with priority/critical-urgent but has not been updated in over 30 days, and should be re-triaged. Critical-urgent issues must be actively worked on as someone's top priority right now.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Deprioritize it with /priority {important-soon, important-longterm, backlog}
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

richardcase commented 1 year ago

/triage accepted

k8s-triage-robot commented 1 year ago

This issue is labeled with priority/critical-urgent but has not been updated in over 30 days, and should be re-triaged. Critical-urgent issues must be actively worked on as someone's top priority right now.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Deprioritize it with /priority {important-soon, important-longterm, backlog}
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

kubernetes-sigs / cluster-api-provider-aws

[e2e] clusterctl upgrade testing for EKS #2828

Guidelines