Describe the problem/challenge you have
Currently, kapp-controller tests are run against static Kubernetes versions. There is no automated mechanism to continuously verify compatibility against the absolute latest Kubernetes releases (built daily) or ensure continued support for the oldest supported versions on a nightly schedule. This can lead to late discovery of breaking changes in new Kubernetes releases.
Describe the solution you'd like
I have implemented a new nightly automation pipeline that:
-
Builds Fresh Kind Images: Automatically builds a Kind node image from the latest commit of the upstream Kubernetes repository (e.g., release-1.35) and the minimum supported version (e.g., release-1.32) every night.
-
Pushes to Registry: Tags and pushes these custom images to the container registry (e.g., ghcr.io/carvel-dev/kindest-node).
-
Triggers E2E Tests: Automatically triggers the Nightly E2E Tests workflow to run the full kapp-controller test suite against these freshly built clusters.
Anything else you would like to add:
[Additional information that will assist in solving the issue.]
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Describe the problem/challenge you have
Currently, kapp-controller tests are run against static Kubernetes versions. There is no automated mechanism to continuously verify compatibility against the absolute latest Kubernetes releases (built daily) or ensure continued support for the oldest supported versions on a nightly schedule. This can lead to late discovery of breaking changes in new Kubernetes releases.
Describe the solution you'd like
I have implemented a new nightly automation pipeline that:
Builds Fresh Kind Images: Automatically builds a Kind node image from the latest commit of the upstream Kubernetes repository (e.g., release-1.35) and the minimum supported version (e.g., release-1.32) every night.
Pushes to Registry: Tags and pushes these custom images to the container registry (e.g., ghcr.io/carvel-dev/kindest-node).
Triggers E2E Tests: Automatically triggers the Nightly E2E Tests workflow to run the full kapp-controller test suite against these freshly built clusters.
Anything else you would like to add:
[Additional information that will assist in solving the issue.]
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.