adding peerpods as dependency#54
adding peerpods as dependency#54beraldoleal wants to merge 1 commit intoconfidential-containers:mainfrom
Conversation
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 <bleal@redhat.com>
|
@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. |
|
@beraldoleal ... |
|
@fidencio ... This is expected...as we wait for the peerpods chart to be released... vide the TODO comment on the chart.yaml file.... If you can take a look ignoring this for now... would be nice. |
|
I guess the main question that I have here is whether we want to have this deployed alongside other kata deployments. |
That is a good question, and tbh, I can’t think of any reason why it shouldn’t coexist with the others. I can adapt without problems.... I would just like to know the opinion of the PeerPods community here... I might be missing something. @stevenhorsman , @wainersm , @mkulke . |
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