-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
This is a rough plan what we intend to do for the next larger releases.
Current state as of writing this: 0.2.5. is out https://github.com/eclipse/kuksa.val/releases/tag/0.2.5
What: Trying to integrate the various KUKSA components (better) with databroker and future-proofing API
Why: Integrating some things we learned from the past years and take VSS developments into account. Enabling more of the existing KUKSA.val infrastructure to work with databroker
When: Q4/2022-Q1/2023
Content:
- Introduction of new kuksa.val.v1 GRPC API in databroker based on the learnings from kuksa.val databroker and server
- this will be provided alongside existing APIs during 0.3 release cycle
- the API design is meant to be extendable for further VSS extensions/overlays me wight want to support in the future
- Introduction of updated Python client library
- Added support for the new GRPC API (up until 0.2.5 only VISS supported)
- Porting of existing feeders and other components to the new API/new Python lib
- as a result much more components will work with databroker as well as server
What: Security and authorisation in databroker
Why: Almost all deployments will have security goals, and currently databroker supports none. The main goals security here are: Confidentiality: Having an encrypted connection as interaction with databroker might be over any kind of network in the car. Also as not every kuksa.val client will be allowed to perform all operations in all parts of the data model, authorisation is needed.
When: Q4/2022-Q1/2023
Content:
- Enabling TLS in databroker
- Supporting JWT tokens for authorisation based on an extended version of https://github.com/eclipse/kuksa.val/blob/master/doc/KUKSA.val_server/jwt.md
- will be extended to reflect differing access to "target" vs "current" values
- more fine-grained control over the right to change metadata/extending the tree