adding peerpods as dependency #54
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add peerpods chart as a dependency when peerpods is enabled and include a basic Docker workflow. Comprehensive e2e coverage for major providers (Azure, libvirt, AWS, IBM Cloud, Docker) already exists at the CAA CI level. Fixes: confidential-containers#2 Signed-off-by: Beraldo Leal <[email protected]>
Member
Author
|
@fidencio... better late then never! Looking for early feedback on this one, for whenever you have some spare cycles. We're still waiting on IBM Cloud test stabilization and the final CAA release before publishing the latest helm chart to the OCI registry. Kudos to @stevenhorsman and @wainersm for all the work on the CI integration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add peerpods chart as a dependency when peerpods is enabled and include a basic Docker workflow. Comprehensive e2e coverage for major providers (Azure, libvirt, AWS, IBM Cloud, Docker) already exists at the CAA CI level.
Fixes: #2