The Cloud Native Computing Basis (CNCF) is internet hosting KubeCon + Cloud Native Con this week in Salt Lake Metropolis, UT, and through the occasion, it introduced the commencement of two of its tasks: cert-manager and Dapr.
Cert-manager is an open supply certificates administration platform that helps builders automate issuance and renewal of Transport Layer Safety (TLS) and Mutual Transport Layer Safety (mTLS) certificates.
It was created in 2017 at Jetstack (now owned by Venafi, a CyberArk firm), accepted into the CNCF Sandbox in November 2020, and moved to the CNCF Incubators in 2022. On the time of its commencement, cert-manager had over 450 contributors, 200 releases, and 500 million downloads per thirty days.
“By making it simpler for builders to acquire, handle, and automate safety certificates, cert-manager helps guarantee functions stay safe all through their lifecycles, making the ecosystem safer as an entire,” stated Chris Aniszczyk, CTO of the CNCF. “We’re thrilled to see the challenge attain this milestone and look ahead to it persevering with to enhance the cloud native safety area.”
The opposite graduated challenge, Dapr (Distributed Utility Runtime), is a runtime for constructing distributed functions. It was created by Microsoft in 2019, and accepted into the CNCF Incubator in November 2021. As we speak, it has over 3,700 contributors and has over 70 million downloads.
“In as we speak’s aggressive surroundings it’s extra vital than ever for organizations to have the ability to ship dependable and scalable functions shortly,” stated Aniszczyk. “Dapr gives a complete answer for growing edge and cloud native functions, saving builders useful time and releasing them to concentrate on innovating.”
Each tasks combine with many different CNCF tasks, equivalent to Envoy, Istio, Kubernetes, OpenTelemetry, Prometheus, and SPIFFE.
Jaeger v2 launched
Moreover, the distributed tracing platform Jaeger — one of many first tasks to ever graduate from the CNCF — has reached a serious milestone with the discharge of v2.
This launch marks an vital architectural change in that the platform is now based mostly on the OpenTelemetry Collector. In accordance with the CNCF, this architectural change made sense as a result of there was already some overlap and each Jaeger and OpenTelemetry Collector typically utilized one another’s code.
“Collector helps receivers for legacy Jaeger codecs carried out by importing Jaeger packages. And Jaeger reuses Collector’s receivers and knowledge mannequin converters. Due to this synergy, it’s been our objective for some time to carry the 2 tasks nearer,” the Jaeger maintainers wrote in a weblog put up.
Some key options and advantages led to in Jaeger v2 embrace:
- Native assist for the OpenTelemetry Protocol (OTLP) knowledge format
- Batch knowledge processing
- Implementation of the identical configuration and deployment mannequin because the OpenTelemetry Collector
- All core options of the OpenTelemetry Collector, like auth, cert reloading, inside monitoring, and z-pages
- Entry to OpenTelemetry Collector extensions
- The flexibility to carry out tail-based sampling
