1# Linkerd Roadmap
2
3This document is intended to describe high-level plans for the Linkerd
4project and is neither comprehensive nor prescriptive. For a more granular
5view of planned work, please refer to the project's upcoming [milestones].
6
7## Separate helm chart for Linkerd CRDs
8
9Following best practices, Custom Resource Definitions are being migrated to
10their own helm chart
11
12## Client-side policy, v2
13
14As we identify new primitives/patterns for server-side configuration, we plan
15to replace the current `ServiceProfile` APIs with new client-side primitives
16that support the existing resources as well as:
17
18- Circuit-breakers
19- Non-cluster-local traffic targets
20- TLS requirements
21- Route-Specific Authorization
22- Outbound Route Configuration
23- Header-based Routing
24
25## Mesh expansion
26
27Linkerd's mTLS identity only works for resources managed by Kubernetes. We
28plan to extend Linkerd to support non-Kubernetes workloads.
29
30## OpenMetrics
31
32The OpenMetrics working group is developing a new standard for metric
33exposition. We plan to support this format and follow best practices
34identified by this project.
35
36## Linkerd Gateway
37
38The foundation for this feature exists in the multi-cluster gateway which
39provides connectivity between clusters using the multi-cluster extension. As the
40need for tighter ingress integration develops, the gateway functionality will
41develop into a multi-purpose entry point for traffic entering the cluster,
42reducing the dependency on features and development cycles for current ingress
43providers.
44
45<!-- references -->
46[milestones]: https://github.com/linkerd/linkerd2/milestones
View as plain text