Skip to content

Latest commit

 

History

History
275 lines (192 loc) · 20.6 KB

CHANGELOG.md

File metadata and controls

275 lines (192 loc) · 20.6 KB
Raw

CHANGELOG

v0.5.0

What's New

Manage EdgeX Foundry system in OpenYurt in a cloud-native, non-intrusive way

  • yurt-edgex-manager

    Yurt-edgex-manager enable OpenYurt to be able to manage the EdgeX lifecycle. Each EdgeX CR (Custom Resource) stands for an EdgeX instance. Users can deploy/update/delete EdgeX in OpenYurt cluster by operate the EdgeX CR directly. (yurt-edgex-manager, @yixingjia, @lwmqwer)

  • yurt-device-controller

    Yurt-device-controller aims to provider device management functionalities to OpenYurt cluster by integrating with edge computing/IOT platforms, like EdgeX in a cloud native way. It will automatically synchronize the device status to device CR (custom resource) in the cloud and any update to the device will pass through to the edge side seamlessly. More information can be found at: (yurt-device-controller, @charleszheng44, @qclc, @Peeknut, @rambohe-ch, @yixingjia)

Yurt-tunnel support more flexible settings for forwarding requests from cloud to edge

  • Support forward https request from cloud to edge for components(like prometheus) on the cloud nodes can access the https service(like node-exporter) on the edge node. Please refer to the details: (#442, @rambohe-ch, @Fei-Guo, @DrmagicE, @SataQiu)

  • support forward cloud requests to edge node's localhost endpoint for components(like prometheus) on cloud nodes collect edge components(like yurthub) metrics(http://127.0.0.1:10267). Please refer to the details: (#443, @rambohe-ch, @Fei-Guo)

Other Notable Changes

Bug Fixes

  • fix incomplete data copy of resource filter (#452, @SataQiu)
  • remove excess chan that will block the program (#446, @zc2638)
  • use buffered channel for signal notifications (#471, @SataQiu)
  • add create to yurt-tunnel-server ClusterRole (#500, adamzhoul)

v0.4.1

What's New

Join or Reset node in one step

In order to enable users to use OpenYurt clusters quickly and reduce the cost of users learning OpenYurt, yurtctl has provided the subcommands convert and revert, to implement the conversion between OpenYurt cluster and Kubernetes cluster. However, It still has some shortcomings:

  • No support for new nodes to join the cluster directly;
  • Users are required to pre-built a kubernetes cluster, and then do conversion, which has a relatively high learning cost for beginners.

So, we need to add subcommands init, join, reset for yurtctl. and join and reset subcommands can be used in v0.4.1, and init subcommand will comes in next version. Please refer to the proposal doc and usage doc for details. (#387, #402, @zyjhtangtang)

Support Pods use InClusterConfig access kube-apiserver through yurthub

Many users in OpenYurt community have requested that support InClusterConfig for pods to access kube-apiserver through yurthub on edge nodes. so pods on cloud can move to edge cluster smoothly. so we add the following features.

  • yurthub supports https serve.
  • env KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT should be the address that yurthub listening, like 169.254.2.1:10261

Please refer to the issue #372 for details. (#386, #394, @luckymrwang, @rambohe-ch)

Support filter cloud response data on edge side

In the cloud-edge scenario, In response to requests from edge components (such as kube-proxy) or user pods to the cloud, it is hoped that some customized processing can be performed on the data returned by the cloud, we consider providing a generic data filtering framework in the yurthub component, which can customize the data returned from the cloud without being aware of the edge components and user pods, so as to meet business needs simply and conveniently. And provides two specific filtering handlers.

  1. support endpointslice filter for keeping service traffic in-bound of nodePool
  2. support master service mutation for pod use InClusterConfig access kube-apiserver

Please refer to the Proposal doc for details. (#388, #394, @rambohe-ch, @Fei-Guo)

Other Notable Changes

  • Yurtctl modify kube-controllersetting to close the nodelifecycle-controller (#399, @Peeknut)
  • Proposal: EdgeX integration with OpenYurt (#357, @yixingjia, @lwmqwer)
  • Proposal: add ingress feature support to nodepool (#373, @zzguang, @wenjun93)
  • Proposal: OpenYurt Convertor Operator for converting K8S to OpenYurt (#389, @gnunu)
  • add traffic(from cloud to edge) collector metrics for yurthub (#398, @rambohe-ch)
  • Add sync.Pool to cache *bufio.Reader in tunnel server (#381, @DrmagicE)
  • improve tunnel availability (#375, @aholic)
  • yurtctl adds parameter enable app manager to control automatic deployment of yurtappmanager. (#352, @yanhui)

Bug Fixes

  • fix tunnel-agent/tunnel-server crashes when the local certificate can not be loaded correctly (#378, @SataQiu)
  • fix the error when cert-mgr-mode set to kubelet (#359, @qclc)
  • fix the same prefix key lock error (#396, @rambohe-ch)

v0.4.0

What's New

Node Resource Manager Released

Node resource manager is released in this version, which provides local node resources management of OpenYurt cluster in a unified manner. It currently supports LVM, QuotaPath and Pmem, and create or update the compute, storage resources based on local devices. It works as daemonset spread on each edge node, and manages local resources with a predefined spec stored in configmap. Please refer to the usage doc for details. (#1, @mowangdk, @wenjun93)

Add Cloud Native IOT Device Management API definition

Inspiring by the Unix philosophy, "Do one thing and do it well", we believe that Kubernetes should focus on managing computing resources while edge devices management can be done by adopting existing edge computing platforms. Therefore, we define several generic custom resource definitions(CRD) that act as the mediator between OpenYurt and the edge platform. Any existing edge platforms can be integrated into the OpenYurt by implementing custom controllers for these CRDs. In addition, these CRDs allow users to manage edge devices in a declarative way, which provides users with a Kubernetes-native experience.(#233, #236, @Fei-Guo, @yixingjia, @charleszheng44)

Kubernetes V1.18 is supported

OpenYurt officially supports version v1.18 of Kubernetes. Now, OpenYurt users are able to convert v1.18 Kubernetes cluster to OpenYurt cluster or deploy components of OpenYurt on v1.18 Kubernetes cluster manually. the main work for supporting v1.18 Kubernetes as following:

  1. refactor serializer of cache manager to adapt ClientNegotiator in k8s.io/apimachinery v0.18
  2. add context parameter in api for calling client-go v0.18

and based on Kubernetes compatibility, v1.16 Kubernetes is still supported. (#288, @rambohe-ch)

UnitedDeployment support patch for pool

UnitedDeployment controller provides a new way to manage pods in multi-pool by using multiple workloads. Each workload managed by UnitedDeployment is called a pool and user can only configure the workload replicas in the pool. Based on the patch feature, besides the workload replicas configuration, user can easily configure other fields(like images and resoures) of workloads in the pool.(#242, #12, @kadisi)

Support caching CRD resources by yurthub

Because resources in the resourceToKindMap can be cached by yurt-hub component, when network between cloud and edge disconnected, if any pod(eg: calico) on the edge node that used some resources(like crd) not in the above map want to run continuously, that is to say, the pod can not restarted successfully because resources(like crd) are not cached by yurt-hub. This PR can solve this limitation. Now yurt-hub is able to cache all kubernetes resources, including crd resource that defined by user.(#162, #231, #225, #265, @qclc, @rambohe-ch)

Prometheus and Yurt-Tunnel-Server cross-node deployment is supported via DNS

In the edge computing scenario, the IP addresses of the edge nodes are likely to be the same. So we can not rely on the node IP to forward the request but should use the node hostname(unique in one cluster). This PR provides the ability for the yurt-tunnel-server to handle requests in the form of scheme://[hostname]:[port]/[req_path].(#270, #284, @SataQiu, @rambohe-ch)

Support kind cluster and node level conversion by yurtctl

OpenYurt supports the conversion between the OpenYurt cluster and the Kubernetes cluster created by minikube, kubeadm, and ack. Now OpenYurt supports the conversion between kind cluster and OpenYurt cluster. (#230, #206, #220, #234, @Peeknut)

Other Notable Changes

Bug Fixes

  • fix list runtimeclass and csidriver from cache error when cloud-edge network disconnected (#258, @rambohe-ch)
  • fix the error of cluster status duration statistics (#295, @zyjhtangtang)
  • fix bug when ServeHTTP panic (#198, @aholic)
  • solve ips repeated question from addr.go (#209, @luhaopei)
  • fix t.Fatalf from a non-test goroutine (#269, @contrun)
  • Uniform label for installation of yurt-tunnel-agent openyurt.io/is-edge-worker=true (#275, @yanhui)
  • fix the bug that dns controller updates dns records incorrectly (#283, @SataQiu)
  • It solves the problem that the cloud node configuration taint (#299, @yanhui)
  • Fixed incorrect representation in code comments. (#296, @felix0080)
  • fix systemctl restart in manually-setup tutorial (#205, @DrmagicE)

v0.3.0

Project

  • Add new component Yurt App Manager that runs on cloud nodes
  • Add new provider=kubeadm for yurtctl
  • Add hubself certificate mode for yurthub
  • Support log flush for yurt-tunnel
  • New tutorials for Yurt App Manager

yurt-app-manager

  • Implement NodePool CRD that provides a convenient management experience for a pool of nodes within the same region or site
  • Implement UnitedDeployment CRD by defining a new edge application management methodology of using per node pool workload
  • Add tutorials to use Yurt App Manager

yurthub

  • Add hubself certificate mode for generating and rotating certificate that used to connect with kube-apiserver as default mode
  • Add timeout mechanism for proxying watch request
  • Optimize the response when cache data is not found

yurt-tunnel

  • Add integration test
  • Support log flush request from kube-apiserver
  • Optimize tunnel interceptor for separating context dailer and proxy request
  • Optimize the usage of sharedIndexInformer

yurtctl

  • Add new provider=kubeadm that kubernetes cluster installed by kubeadm can be converted to openyurt cluster
  • Adapt new certificate mode of yurthub when convert edge node
  • Fix image pull policy from Always to IfNotPresent for all components deployment setting

v0.2.0

Project

  • Support Kubernetes 1.16 dependency for all components
  • Support multi-arch binaries and images (arm/arm64/amd64)
  • Add e2e test framework and tests for node autonomy
  • New tutorials (e2e test and yurt-tunnel)

yurt-tunnel

Features

  • Implement yurt-tunnel-server and yurt-tunnel-agent based on Kubernetes apiserver network proxy framework
  • Implement cert-manager to manage yurt-tunnel certificates
  • Add timeout mechanism for yurt-tunnel

yurtctl

Features

  • Add global lock to prevent multiple yurtctl invocations concurrently
  • Add timeout for acquiring global lock
  • Allow user to set the label prefix used to identify edge nodes
  • Deploy yurt-tunnel using convert option

Bugs

  • Remove kubelet config bootstrap args during manual setup

v0.1.0-beta.1

yurt-controller-manager

Features

  • Avoid evicting Pods from nodes that have been marked as autonomy nodes

yurthub

Features

  • Use Kubelet certificate to communicate with APIServer
  • Implement a http proxy for all Kubelet to APIServer requests
  • Cache the responses of Kubelet to APIServer requests in local storage
  • Monitor network connectivity and switch to offline mode if health check fails
  • In offline mode, response Kubelet to APIServer requests based on the cached states
  • Resync and clean up the states once node is online again
  • Support to proxy for other node daemons

yurtctl

Features

  • Support install/uninstall all OpenYurt components in a native Kubernetes cluster
  • Pre-installation validation check