kubernetes-sigs/cluster-api-provider-aws

[e2e] Re-enable clusterctl upgrade spec tests

Open

#5,169 opened on Oct 21, 2024

View on GitHub
 (17 comments) (0 reactions) (1 assignee)Go (689 forks)auto 404
help wantedkind/featurelifecycle/rottenneeds-triagepriority/important-soon

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

Describe the solution you'd like

When we have a release with the new AMI changes it the re-enable the following tests:

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):

Contributor guide

Research direction
Identify the specific AMI references in the failing tests and update them to available AMIs. For the etcd version change, locate the expected version string and update it to 3.5.15-0. Ensure the tests can run with the new release.
Tech stack
gokubernetes
Domain
backendapiinfrastructure
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoKubernetese2e testingAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60