List view
- Due by June 3, 2024•9/9 issues closed
- Due by April 15, 2024•16/16 issues closed
- Due by April 1, 2024•6/6 issues closed
Imports and exports reference Service catalog entries which are managed centrally/set in system namespace.
No due dateEnable automation for secure access of cloud services from within a ClusterLink enabled system. This may include simplified configuration for cloud service export/import, access hardening (e.g., VPE and identity based access credentials) and ensuring end to end TLS with cloud service works
No due dateEnable ClusterLink to import/export services in non-k8s environments, such as Linux/SLURM
No due dateClusterLink operational within a single namespace without cluster wide privileges (e.g., CRDs installed at cluster level, watch all namespaces, etc.)
No due dateSupport for SPIFFE/SPIRE generated certificates in gateways. Support certificate validation and rotation (e.g., reload). Gateway changes should be minimized and it should remain SPIFFE/SPIRE independent
Due by April 28, 2024Allow specification of service, workload and peer attributes in objects, their exchange and use in policy decisions. Currently we use a single predefined label for workload identification
No due dateInitially support single tenant (fabric) in CM, later consider if can extended for soft multi-tenancy (i.e., same org, different fabrics - not a hostile environment). Consider possible simplification of cross cluster operations (e.g. peer and service catalog, automating export/import relations, etc.) Assume a management agent in each spoke cluster and a central management application in hub cluster (also k8s CRD based).
No due datePer connection as well as system metrics exposed via standard interfaces. The milestone could be extended to support additional observability aspects (e.g., OpenTelemetry in control plane, logging, ...)
No due dateChange all demos and documentation to refer to CRD based management
Due by April 1, 2024•6/6 issues closedSimplified installation using a k8s operator. ClusterLink CLI modified to support operator needs and simplify user interactions (eg. create ingress points)
Due by March 31, 2024•4/4 issues closed- No due date•2/2 issues closed
- No due date
All ClusterLink runtime configuration can be done via CRDs and kubectl. Support for Spec/Status on peers, export, import and policies. Some objects live in dedicated cl-system namespace, some in developer namespaces.
Due by March 31, 2024•9/9 issues closed- No due date•6/6 issues closed
ClusterLink code base, samples and documentation ready for consumption, hosted on our own domain.
Due by March 31, 2024•19/19 issues closedAll features and demos working with new control and data planes
Due by November 5, 2023•7/7 issues closed