-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
Story (Required)
As a developer trying to use Shipwright, I want Shipwright Builds to support the latest Kubernetes and Tekton releases.
<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>
Background (Required)
<Describes the context or background related to this story>
The Shipwright community updates its Kubernetes and Tekton dependencies with each upstream minor release. This action happens at most 4 weeks prior to the planned minor release date (see the community roadmap)
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
In the shipwright-io/build project, ensure the following is completed:
- Update k8s.io/* go dependencies in the build project to the current release.
- Update tektoncd/pipeline go dependencies the current LTS release
- Update the min and max supported Kubernetes and Tekton versions in the CI pipeline.
Note: the community has created a significant amount of automation for these tasks.
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met