githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam Next steps Now /var/snap/microk8s/current/args/cni-network/cni.conf curl https://raw.githubusercontent.com/cilium/cilium/v1.5/plugins/cilium-c systemctl restart snap.microk8s.daemon-containerd.service systemctl restart snap.microk8s

From Managed Kubernetes to App Platform: 1.5 Years of Cilium Usage at DigitalOcean Timo Reimann, DigitalOcean October 28, 2020 digitalocean.com History / Context ● DigitalOcean Kubernetes Service

0 1 1.1 1.2 1.3 1.4 1.5 1.6 2 2.1 2.2 2.3 2.4 2.5 3 3.1 3.2 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 5 5.1 5.2 6 6.1 6.2 6.3 6.4 目錄 介紹 第1章 Linux安全渗透简介 1.1 什么是安全渗透 1.2 安全渗透所需的工具 1.3 Kali Linux简介 Linux简介 1.4 安装Kali Linux 1.5 Kali更新与升级 1.6 基本设置 第2章 配置Kali Linux 2.1 准备内核头文件 2.2 安装并配置NVIDIA显卡驱动 2.3 应用更新和配置额外安全工具 2.4 设置ProxyChains 2.5 目录加密 第3章 高级测试实验室 3.1 使用VMware Workstation 3.2 攻击WordPress和其他应用程序 Continue按钮，将显示如图1.4所示的界面。 图1.4 选择您的区域 （4）在该界面选择区域为“中国”，然后单击“继续”按钮，将显示如图1.5所示的界 面。 大学霸 Kali Linux 安全渗透教程 12 1.4 安装Kali Linux 图1.5 配置键盘 （5）在该界面选择键盘模式为“汉语”，然后单击“继续”按钮，将显示如图1.6所示的 界面。 图1.6 配置网络 （6）该界

............................................................................................ 20 1.5 系统初始化进程 .......................................................................................... yum 和 dnf 两个命 令，大家在实际操作中随意选择就好。甚至这两个命令的提示信息都基本一样，感知不到什 么区别。 动手部署一台 Linux 操作系统 60 1.5 系统初始化进程 Linux 系统的开机过程是这样的，即先从 BIOS 开始，然后进入 Boot Loader，再加载系 统内核，然后内核进行初始化，最后启动初始化进程。初始化进程作为 Linux 交换分区的创建过程与前文讲到的挂载并使用存储设备的过程非常相似。在对/dev/sdb 存储设备进行分区操作前，有必要先说一下交换分区的划分建议：在生产环境中，交换分区 的大小一般为真实物理内存的 1.5～2 倍。为了让大家更明显地感受交换分区空间的变化，这 里取出一个大小为 5GB 的主分区作为交换分区资源： [root@linuxprobe~]# fdisk /dev/sdb Welcome

让我们假设上游源码包为 debhello-1.5.tar.gz。 此类型的源码旨在作为非系统文件安装，例如： $ tar -xzmf debhello-1.5.tar.gz $ cd debhello-1.5 $ ./configure --with-math $ make $ make install 让我们取得源码并制作 Debian 软件包。 下载 debhello-1.5.tar.gz $ wget wget http://www.example.org/download/debhello-1.5.tar.gz ... $ tar -xzmf debhello-1.5.tar.gz $ tree . +-- debhello-1.5 | +-- LICENSE | +-- Makefile.in | +-- configure | +-- data | | +-- hello.desktop +-- hello.c +-- debhello-1.5.tar.gz 4 directories, 8 files 102 CHAPTER 8. 更多示例 8.8. MAKEFILE.IN + CONFIGURE（单个二进制 … 此处的源码如下所示。 src/hello.c（v=1.5）： $ cat debhello-1.5/src/hello.c #include "config

512 megabytes 1.5 gigabyte 2.5 gigabytes Server (Standard) live server 1 gigahertz (amd64 only) 1 gigabyte 1.5 gigabyte n/a Server (Minimal) debian-installer 300 megahertz 384 megabytes 1.5 gigabytes 2 bridge, controls which interfaces are part of the bridge, etc. See man brctl for more information. 1.5. Resources • The Ubuntu Wiki Network page1 has links to articles covering more advanced network configuration DM-Multipath. The kpartx is provided in its own package, but the multipath-tools package depends on it. 1.5. DM-Multipath Setup Overview DM-Multipath includes compiled-in default settings that are suitable

x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients must reconnect[1] 1.5.x 1.6.y Required Minimal to None Clients must reconnect[1] Annotations: the DaemonSet. Adding the options to the ConfigMap will not impact the ability to rollback. Cilium 1.5.y and earlier are compatible with the options although their values will be ignored as both options described in Upgrading Minor Versions. Users running older versions should first upgrade to the latest v1.5.x point release to minimize disruption of service connections during upgrade. Changes that may require

x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients must reconnect[1] 1.5.x 1.6.y Required Minimal to None Clients must reconnect[1] 1.6.x 1 the DaemonSet. Adding the options to the ConfigMap will not impact the ability to rollback. Cilium 1.5.y and earlier are compatible with the options although their values will be ignored as both options as described in Upgrading Cilium. Users running older versions should first upgrade to the latest v1.5.x point release to minimize disruption of service connections during upgrade. Changes that may require

. . 10 1.4 Project Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.5 Project History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.5.1 Project target Debugging debuggable via make debug target Continue reading for more features and usage. 1.5 Project History 1.5.1 Project Origins About 10 years ago (2010), a tinylinux proposal: Work on Tiny issues, here is the recommended configuration: Hardware Requirement Description Processor X86_64, > 1.5GHz Must choose 64bit X86 while using virtual machine Disk >= 50G System (25G), Docker Images(~5G)

. . 10 1.4 Project Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.5 Project History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.5.1 Project target Debugging debuggable via make debug target Continue reading for more features and usage. 1.5 Project History 1.5.1 Project Origins About 10 years ago (2010), a tinylinux proposal: Work on Tiny issues, here is the recommended configuration: Hardware Requirement Description Processor X86_64, > 1.5GHz Must choose 64bit X86 while using virtual machine Disk >= 50G System (25G), Docker Images(~5G)