Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to use kata-containers main branch #1754

Merged
merged 11 commits into from
May 17, 2024

Conversation

stevenhorsman
Copy link
Member

No description provided.

@stevenhorsman stevenhorsman added the test_e2e_libvirt Run Libvirt e2e tests label Mar 20, 2024
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 4 times, most recently from 32f8e17 to 169400f Compare March 20, 2024 16:08
@stevenhorsman stevenhorsman removed the test_e2e_libvirt Run Libvirt e2e tests label Mar 20, 2024
@beraldoleal
Copy link
Member

beraldoleal commented Mar 22, 2024

Hi @stevenhorsman here is the commit that we need to fix the fieldMask error:

beraldoleal@f8ccccb

Build is passing locally here when including this commit. Feel free to incorporate it in your PR.

@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 4 times, most recently from f6191f5 to ea9c24b Compare March 25, 2024 11:10
@stevenhorsman stevenhorsman added the test_e2e_libvirt Run Libvirt e2e tests label Mar 25, 2024
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 4 times, most recently from bcf9d39 to fad3fb7 Compare March 27, 2024 13:05
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 4 times, most recently from d8a5a05 to c7b8c6c Compare April 10, 2024 15:07
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 7 times, most recently from 4dd86b7 to c7c48d6 Compare April 18, 2024 12:47
@stevenhorsman
Copy link
Member Author

If anyone is interested. I've created some instructions for how to test this PR out in #1596 (comment)

There are still some things to resolve though, so it's not fully ready yet:

  • Resolve the double CAA ds issue
  • Improve the caching on kata-containers to allow us to pick pinned releases
  • Use caches for the guest components to speed up the podvm build
  • Work out how to resolve the containerd & nydus caching limitation in our CI/for development

@@ -536,6 +536,30 @@ func (p *CloudAPIAdaptor) Deploy(ctx context.Context, cfg *envconf.Config, props
return err
}

// TODO can we do this better with go code?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. I just found this example https://github.com/kubernetes/client-go/blob/master/examples/create-update-delete-deployment/main.go#L111 of using client-go to update a deployment.

@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 2 times, most recently from f19b998 to 3ac419d Compare May 14, 2024 14:31
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 3 times, most recently from 05d1072 to 4b51ae4 Compare May 15, 2024 08:08
@stevenhorsman stevenhorsman linked an issue May 15, 2024 that may be closed by this pull request
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 2 times, most recently from b532596 to 18d15d3 Compare May 15, 2024 10:53
- Remove old PullImage and image service code
as image protos not supported on kata main
- Also remove the criClient code. We used to use the this
to get the image based on digest, but don't have
that code now that we've moved to the snapshotter approach, so remove
the unused references
- As we don't need the cri runtime endpoint in the code now,
we can also remove the related kustomizes that set it

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
- Update the agentServer to match the kata-runtime changes in protobuf
versions in kata-containers/kata-containers#8061
- Primarily swapping `types.Empty` for `emptypb.Empty`

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
- Re generate the podvminfo proto implementation with the new protobuff
- The re-gened podvm info is in a package __, so we need to alias the package
to podvm in our code

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
@stevenhorsman stevenhorsman force-pushed the kata-runtime-bump branch 2 times, most recently from c8816d8 to d9f219d Compare May 15, 2024 16:52
Remove specific nydus test now it is needed for all
image pulls

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
- Update IsPulledWithNydusSnapshotter to no longer check for the
old direct pull image messages as that isn't used anymore

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
- Bump kata-containers to use the 3.5.0 release of the agent
to match the runtime version we are using

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
The kata-agent build (specifically libseccomp) requires the version of yq that
kata-containers uses. So run the kata install_yq.sh before we build it

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
Bump kata-runtime go module to use the 3.5.0
as the latest released runtime that has remote hypervisor and
guest image pull support

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
- Perform go mod tidy after bumping kata runtime

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
We don't think with the latest nydus-snapshotter changes, so that cri-runtime annotation
is needed, so try drop the comments completely

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
In order to switch to `main` kata-containers payload we need to
switch to use the latest operator. There isn't a released version of it yet that supports
the peer pods and nydus-snapshotter changes required,
so switch to the latest branch for now

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
Copy link
Member

@liudalibj liudalibj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stevenhorsman I tested this PR in my x86/s390x cluster, they worked as expected, thanks!
Here the images I built out:

quay.io/liudalibj/podvm-generic-ubuntu-s390x:bcc4c405f4aa5ac4526f508a4bdb3e8a86f4d6500d4eb56337944b1be83423a1
quay.io/liudalibj/podvm-generic-ubuntu-amd64:bcc4c405f4aa5ac4526f508a4bdb3e8a86f4d6500d4eb56337944b1be83423a1
quay.io/liudalibj/podvm-binaries-ubuntu-s390x:bcc4c405f4aa5ac4526f508a4bdb3e8a86f4d6500d4eb56337944b1be83423a1
quay.io/liudalibj/podvm-binaries-ubuntu-amd64:bcc4c405f4aa5ac4526f508a4bdb3e8a86f4d6500d4eb56337944b1be83423a1
quay.io/liudalibj/podvm-builder-ubuntu:bcc4c405f4aa5ac4526f508a4bdb3e8a86f4d6500d4eb56337944b1be83423a1
quay.io/liudalibj/cloud-api-adaptor:dev-6c395be8927835b6e5e0a59dfab891abedb4893b

Copy link
Member

@wainersm wainersm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HI @stevenhorsman ! Re-reviewed, my eyes I couldn't spot any error. Great work, thanks once again!

@wainersm wainersm merged commit a5e37f4 into confidential-containers:main May 17, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test_e2e_libvirt Run Libvirt e2e tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Attempt to update kata-runtime to point to the main version
6 participants