summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorLingxian Kong <anlin.kong@gmail.com>2019-08-28 22:11:27 +1200
committerLingxian Kong <anlin.kong@gmail.com>2019-09-02 10:06:49 +1200
commita1aa15282ea91eafb4afe476336949aec965add2 (patch)
tree492ad375e0b4980c22c286b121ccb3496d10514b /releasenotes
parente739ef6e935ccae0b8b68e0828449897275e5cc0 (diff)
downloadtrove-a1aa15282ea91eafb4afe476336949aec965add2.tar.gz
Support management security group
Allow the cloud admin to control the security groups on the management port of Trove instance, a new config option `management_security_groups` is introduced for that purpose. Change-Id: I4b22b87d37792be700d4ec7f78a7ea479ddb5814 Story: 2006466 Task: 36395
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/train-02-management-security-group.yaml11
1 files changed, 11 insertions, 0 deletions
diff --git a/releasenotes/notes/train-02-management-security-group.yaml b/releasenotes/notes/train-02-management-security-group.yaml
new file mode 100644
index 00000000..a1613688
--- /dev/null
+++ b/releasenotes/notes/train-02-management-security-group.yaml
@@ -0,0 +1,11 @@
+---
+features:
+ - The cloud admin is able to apply a security group to management port(with
+ purpose of communicating with control plane and other management tasks) of
+ the Trove instance, by setting the ``management_security_groups`` config
+ option. The cloud admin is responsible for managing the security group
+ rules. The security group and its rules need to be created before deploying
+ Trove.
+upgrade:
+ - The management security group won't affect the Trove instances created
+ before upgrade. \ No newline at end of file