Cloud API Adaptor Troubleshooting
Generic troubleshooting steps after installation of Cloud API Adaptor
Cloud API Adaptor
Documentation for Cloud API Adaptor a.k.a Peer Pods
Categories:
Warning
TODO: This was copied with few adaptations from here: https://github.com/confidential-containers/cloud-api-adaptor/ This needs to be tested and verified if the instructions still work and needs a rework.Introduction
This repository contains the implementation of Kata remote hypervisor. Kata remote hypervisor enables creation of Kata VMs on any environment without requiring baremetal servers or nested virtualization support.
Goals
- Accept requests from Kata shim to create/delete Kata VM instances without requiring nested virtualization support.
- Manage VM instances in the cloud to run pods using cloud (virtualization) provider APIs
- Forward communication between kata shim on a worker node VM and kata agent on a pod VM
- Provide a mechanism to establish a network tunnel between a worker and pod VMs to Kubernetes pod network
Architecture
The background and description of the components involved in ‘peer pods’ can be found in the architecture documentation.
Components
- Cloud API adaptor (cmd/cloud-api-adaptor) -
cloud-api-adatorimplements the remote hypervisor support. - Agent protocol forwarder (cmd/agent-protocol-forwarder)
Installation
Please refer to the instructions mentioned in the following doc.
Supported Providers
- aws
- azure
- ibmcloud
- libvirt
- vsphere
Adding a new provider
Please refer to the instructions mentioned in the following doc.
Contribution
This project uses the Apache 2.0 license. Contribution to this project requires the DCO 1.1 process to be followed.
Collaborations
- Slack: Channel #confidential-containers-peerpod on CNCF slack.
- Weekly Community meeting at 14:00 - 15:00 UTC every Wednesday.