Author | Xu Di, Chen Jun, Ao Xiaojian, Song Jinchao
Industry news
As the largest version upgrade of the Flink community so far, Flink 1.10 accommodates the development and implementation of more than 1,200 issues by more than 200 contributors, including significant optimization of the overall performance and stability of Flink jobs, and initial integration of native Kubernetes. (beta version) and major optimizations for Python support (PyFlink).
This release is security-focused, and major update highlights include adding support for integrating Linkerd's cross-TLS foundation with external certificate issuers (e.g. Vault, cert-manager), improving GitOps workflows, and making it easy to automatically rotate TLS credentials ; also improved dashboard performance and improved the usability of Helm charts.
Important upstream progress
Kubernets
-
The 1.18 branch was officially created on Tuesday, code freeze on March 5th;
feature gate PodTopologySpread upgraded to beta version.
A new token issuer has been introduced, and those that conform to the OIDC (OpenID Connect) standard can be used as token issuers.
Mainly to solve the crash that occurs during the kubelet certificate rotate process.
You can view the work queue metrics in the controller manager.
An event is reported when the kubelet cannot mount the filesystem.
Allows the GC to clean up ControllerRevisions, avoiding entering a loop that cannot be removed.
Use docker buildx for cross build .
Same
In a multi-cluster, some services are local to the cluster in nature and should not be accessed from other clusters, so operators who support Mesh need to selectively decide whether to merge a single service into a multi-cluster Mesh.
Kubernetes launched the alpha version of Service Topology in version 1.17 . Based on the previous Service, it extended support for zone and region labels, and allowed arbitrary topology. This feature requires EndpointSlice to be enabled. There needs to be plans to support it in Istio, enabling richer regional routing and load balancing capabilities.
- Istio Roadmap 2020 in planning :
- Installation: The control plane is merged into istiod, supports multiple control planes in a single mesh (for control plane upgrades), supports storage of istio configuration data outside of Kubernetes, supports non-stop migration of existing applications on K8s and virtual machines to istio;
- Multi-cluster: support single network/multiple networks, support single control plane/multiple control planes;
- Virtual machine support: refactor service entry to workload entry;
- Service discovery: support consul/Lambda/Azure functions/Zookeeper;
- Scalability: deprecate Mixer v1, support WASM to extend Envoy, and implement Policy and Tlemetry in Mixer;
- Operation and maintenance: new traffic management API; support K8s Ingress v2, support using WASM to extend Istio;
- Security: Added Istio Agent; support to use SDS to extend Mesh running on virtual machines; Mesh federation using SPIFFE trust bundle.
- The Istio 2020 Release plan , which is also planned, will be released every three months in principle:
- Istio 1.5: Expected on February 18th, but it has been delayed, changed to March 5th
- Istio 1.6: Expected May 19
- Istio 1.7: Expected August 18
- Istio 1.8: Expected November 15th
- Istio prepares to deprecate Mixer
Mixer will be marked as deprecated in Istio 1.5; scheduled for removal in Istio 1.7 (expected to be released in August 2020), Mixer's code will be moved to Istio-ecosystem. The new Mixer V2 solution is under development, and the original functions of Mixer will be moved to Envoy and extended in the form of WASM.
Open source project recommendation
It is convenient for spring cloud to connect with spring boot applications running in Kubernetes.
Recommended reading this week
Listed 13 disadvantages of running Kubernetes in bare metal.
An overall interpretation of the current overview of the Service Mesh ecosystem.
" Alibaba Cloud Native focuses on micro-services, serverless, containers, Service Mesh and other technical fields, focuses on popular cloud-native technology trends, and implements large-scale implementation of cloud-native, and is the technology circle that understands cloud-native developers best."