by Sylvain Desbureaux and Krzysztof Opasiak
plans for Honolu were set here: Honolulu intents
Official Helm 3 support
Helm3 (up to 3.3) is officially supported while helm2 is not.
We support helm3 "out of the box" without need of a specific chart datastore.
Official repository for helm charts
Not done on Honolulu
Some advancement has been made and hope for something during Honolulu Maintenance Release
More robust container image retrieval (done)
All containers from ONAP installation is coming from one of these 4 repositories:
- ONAP repository
- Docker Hub
- Google K8S repository
- Elastic repository
some templates have been made in order to easily overwrite each of these and put credentials if needed.
It should simplifiate a lot air-gap installations
New Mariadb version (done)
Instead of using old version of mariadb from an unsupported (and dead) image, we have move to bitnami with latest version available there (10.5.8)
upgrade to newer versions should be a lot simpler
there's a prometheus support also if you want to scrape data from database instances
More components in shared Mariadb
Work has not advanced as thought here. Work is continuing on Istanbul release
Internalize AAI and Robot (done)
AAI and robot are no more subcharts.
It should simplify generic work (version bumping, common templating changes, ...)
AAI chart cleanup
As did with SO, we'll clean a little bit AAI in order to make it helm3 compatible without need of postgresql store on helm3.
remove of unused r/f/tproxies from AAF: done
Certificates automatic generation: done
More automatic certificate retrieval
during Honolulu release :
- A1 Policy management
- AAI (except babel, schema service and graphadmin)
- CDS
- MSB
- Holmes
- VNFSDK
- DMaaP Message Router
- Music
have moved to automated certificate retrieval
Finalize dual stack support
ONAP works on dual stack (IPv4/IPv6) enabled Kubernetes.