READY ubuntu-1604-xenial-v20180522 ubuntu-os-cloud ubuntu-1604-lts READY ubuntu-1804-bionic-v20180522 ubuntu-os-cloud ubuntu-os-cloud ubuntu-1804-lts READY Select an image based on project and family rather than by name. This ensures any scripts or other automation always works with a non-deprecated 2. Create the image with nested virtualization support SOURCE_IMAGE_PROJECT=ubuntu-os-cloud SOURCE_IMAGE_FAMILY=ubuntu-1804-lts IMAGE_NAME=${SOURCE_IMAGE_FAMILY}-nested gcloud compute images create

running in the parent cgroup hierarchy by following the bpftool documentation [https://manpages.ubuntu.com/manpages/focal/man8/bpftool-cgroup.8.html]. For more information, see the Pull Request [https://github bundled along with the Linux distro. In this guide, we are using an Ubuntu container as the client, and so will update it with Ubuntu specific instructions. Other Linux distros will have different mechanisms details. For Ubuntu, we first copy the additional CA certificate to the client pod filesystem $ kubectl cp myCA.crt default/mediabot:/usr/local/share/ca- certificates/myCA.crt Then run the Ubuntu-specific

running in the parent cgroup hierarchy by following the bpftool documentation [https://manpages.ubuntu.com/manpages/focal/man8/bpftool-cgroup.8.html]. For more information, see the Pull Request [https://github bundled along with the Linux distro. In this guide, we are using an Ubuntu container as the client, and so will update it with Ubuntu specific instructions. Other Linux distros will have different mechanisms details. For Ubuntu, we first copy the additional CA certificate to the client pod filesystem $ kubectl cp myCA.crt default/mediabot:/usr/local/share/ca- certificates/myCA.crt Then run the Ubuntu-specific

running in the parent cgroup hierarchy by following the bpftool documentation [https://manpages.ubuntu.com/manpages/focal/man8/bpftool-cgroup.8.html]. For more information, see the Pull Request [https://github bundled along with the Linux distro. In this guide, we are using an Ubuntu container as the client, and so will update it with Ubuntu specific instructions. Other Linux distros will have different mechanisms details. For Ubuntu, we first copy the additional CA certificate to the client pod filesystem $ kubectl cp myCA.crt default/mediabot:/usr/local/share/ca- certificates/myCA.crt Then run the Ubuntu-specific

bundled along with the Linux distro. In this guide, we are using an Ubuntu container as the client, and so will update it with Ubuntu specific instructions. Other Linux distros will have different mechanisms details. For Ubuntu, we first copy the additional CA certificate to the client pod filesystem $ kubectl cp myCA.crt default/mediabot:/usr/local/share/ca- certificates/myCA.crt Then run the Ubuntu-specific TLS inspection. To keep things simple, in this example we will simply copy this list out of the Ubuntu filesystem of the mediabot pod, though it is important to understand that this list of trusted CAs

Install Vagrant You need to run at least Vagrant version 1.8.3 or you will run into issues boo�ng the Ubuntu 17.04 base image. You can verify by running vagrant --version . If you don’t already have Vagrant kernels that are newer than 4.8, but even recent versions of general purpose opera�ng systems such as Ubuntu 16.10 ship fairly recent kernels. Some Linux distribu�ons s�ll ship older kernels but many of them eek_2/] >= 25 LinuxKit [h�ps://github.com/linuxkit/linuxkit/tree/master/kernel] all Ubuntu [h�ps://wiki.ubuntu.com/YakketyYak/ReleaseNotes#Linux_kernel_4.8] >= 16. >= 16. Opensuse [h�ps://www.opensuse

bundled along with the Linux distro. In this guide, we are using an Ubuntu container as the client, and so will update it with Ubuntu specific instructions. Other Linux distros will have different mechanisms details. For Ubuntu, we first copy the additional CA certificate to the client pod filesystem $ kubectl cp myCA.crt default/mediabot:/usr/local/share/ca- certificates/myCA.crt Then run the Ubuntu-specific TLS inspection. To keep things simple, in this example we will simply copy this list out of the Ubuntu filesystem of the mediabot pod, though it is important to understand that this list of trusted CAs