Skip to content

Releases: Wind-River/cloud-platform-deployment-manager

v2.0.8-4 release

06 Jan 13:57
Compare
Choose a tag to compare
Upversion v2.0.8-4

Signed-off-by: Hugo Brito <hugo.brito@windriver.com>

Release v2.0.10

16 Dec 01:51
1ffff21
Compare
Choose a tag to compare
Remove resource request in manifest (#152) (#155)

The current helm chart requests cpu and memeory resource for
kube-rbac-proxy, which is not supposed to.

This commit removes the resource request in the helm chart. This
commit also removes the workaround to force generate helm chart.
This commit will not generate new DM image.

Test passed:
Deploy an AIOSX system with the new helm chart.

Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>

Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>

Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>

Release v2.0.9-1

05 Jan 14:48
f4e0903
Compare
Choose a tag to compare
Upversion to 2.0.9-1 (#134)

Fix addresses creation for any interface class(#116)

This commit upversions to 2.0.9-1 to cherry-pick the
fix in PR #116

Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>

Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>

2.0.9 release

15 Jun 15:37
c48215e
Compare
Choose a tag to compare
Upversion to 2.0.9 (#110)

Signed-off-by: Enzo Candotti <enzo.candotti@windriver.com>

Co-authored-by: Enzo Candotti <enzo.candotti@windriver.com>

Upversion to 2.0.8

23 Nov 22:01
8b9801c
Compare
Choose a tag to compare
Add master NoSchedule toleration (#84)

StarlingX 6.0 will add master NoSchedule taints to controller nodes.

Add a taint toleration to the deployment manager pods and increase the chart version.

Signed-off-by: dsulliva <david.sullivan@windriver.com>

2.0.7 release

20 May 22:14
Compare
Choose a tag to compare
Upversion to 2.0.7

Signed-off-by: Don Penney <don.penney@windriver.com>

v2.0.6

24 Jun 21:29
b5ad801
Compare
Choose a tag to compare

2.0.6 release

First stable release

07 Nov 18:41
Compare
Choose a tag to compare

This is the first stable release of the DM. Development will continue on the master branch with bug fixes cherry-picked back to stable/v1.0.0 if deemed critical enough.