-
Notifications
You must be signed in to change notification settings - Fork 523
chore: Hyperv and upstream Containerd package support #3688
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3688 +/- ##
========================================
Coverage 73.14% 73.15%
========================================
Files 147 147
Lines 25165 25301 +136
========================================
+ Hits 18408 18508 +100
- Misses 5623 5655 +32
- Partials 1134 1138 +4
Continue to review full report at Codecov.
|
@@ -31,41 +31,20 @@ cp bin/ctr.exe /output | |||
#cp bin/containerd.exe /output # missing CRI plugin, so build from containerd/cri | |||
cd \$GOPATH | |||
cd src/github.com/containerd | |||
git clone https://github.com/containerd/cri.git | |||
git clone https://github.com/jterry75/cri.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we using someone's fork of ContainerD?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This the fork the Container Platform team maintains for making the updates required for hyperv. They are in active conversation with the Containerd team to integrate these changes into the upstream. This was the same process they had for the initial Containerd Support that is now in the 1.4 release.
Update docs/topics/features.md Co-authored-by: Matt Boersma <Matt.Boersma@microsoft.com>
I think we probably want to add a new property in the api model that sets if the default runtime class in the containerd config uses hyper-v isolation or not. |
Agreed I created issue #3687 with a possible idea. As of right now this will allow running both based on the configuration file that is present in the hyperv package. This is not ideal but wanted to get thoughts on #3687 and get something to unlock the failing tests before modifying the api model to far. Thinking on it a bit more the model change might be something like:
This would allow user to specify:
These fields would only be valid if using containerd. |
I think we need to have at least have a switch for the default runtime handler / isolation type for this to get checked in to master. We can use #3687 to figure out how to handle more customizing the non-default runtime classes defined in the containerd config. |
} | ||
"networkPlugin": "azure", | ||
"containerRuntime": "containerd", | ||
"windowsContainerdURL": "https://k8swin.blob.core.windows.net/k8s-windows/containerd/containerplat-aks-test-0.0.8.zip" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May I regard this package url as the _official url_for 20H1 so far?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes this is the latest package
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are the official bits but we will probably need to host them along with our other artifacts for production use.
k8swin.blob.core.windows.net is just hosted in a single zone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am going to set up a different url for prod use. Will follow back once I have it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
That should not block this PR IMO
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsturtevant, marosset The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* chore: Hyperv and upstream Containerd package support (#3688) * fix: fix issue where installing a different version of containerd vs what was pre-installed on VHD failed silently (#3743) * feat: collect hyperv logs * fix: do not log secret in provisioning script Co-authored-by: Mark Rossetti <marosset@microsoft.com>
* hyperv and upstream support * update docs and scripts for hyperv Co-authored-by: Matt Boersma <Matt.Boersma@microsoft.com>
Reason for Change:
Containerd 1.4rc1 is now available. Hyperv support has progressed but is still in experimental support.
This pr enables:
RuntimeClass
Better support for configuring Containerd will be done in a separate PR after a discussion in issue #3687
Issue Fixed:
Fixes #2827
Requirements:
Notes: