Skip to content

adding peerpods as dependency#54

Draft
beraldoleal wants to merge 1 commit intoconfidential-containers:mainfrom
beraldoleal:chart-peerpods-as-coco-dep
Draft

adding peerpods as dependency#54
beraldoleal wants to merge 1 commit intoconfidential-containers:mainfrom
beraldoleal:chart-peerpods-as-coco-dep

Conversation

@beraldoleal
Copy link
Member

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

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>
@beraldoleal
Copy link
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.

@fidencio
Copy link
Member

@beraldoleal ...

Run echo "📦 Updating Helm chart dependencies..."
📦 Updating Helm chart dependencies...
🔧 CI test detected - using dev chart version from main (0.0.0-dev)...
✅ Updated Chart.yaml to use dev version 0.0.0-dev
Error: directory ../cloud-api-adaptor/src/cloud-api-adaptor/install/charts/peerpods not found
Error: Process completed with exit code 1.

@beraldoleal
Copy link
Member Author

@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.

@fidencio
Copy link
Member

I guess the main question that I have here is whether we want to have this deployed alongside other kata deployments.
What's your plan when it comes to that? Is it all or nothing? Docs should reflect that.

@beraldoleal
Copy link
Member Author

I guess the main question that I have here is whether we want to have this deployed alongside other kata deployments. What's your plan when it comes to that? Is it all or nothing? Docs should reflect that.

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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for deploying the peer pods

2 participants