Geoffrey
My feedback
155 results found
-
7 votesGeoffrey supported this idea ·
-
4 votesGeoffrey supported this idea ·
-
7 votesGeoffrey supported this idea ·
-
5 votesGeoffrey supported this idea ·
-
6 votesGeoffrey supported this idea ·
-
7 votesGeoffrey supported this idea ·
-
8 votes
An error occurred while saving the comment -
3 votesGeoffrey shared this idea ·
-
11 votesGeoffrey supported this idea ·
-
17 votesGeoffrey supported this idea ·
-
18 votesGeoffrey supported this idea ·
-
63 votesGeoffrey supported this idea ·
-
67 votesGeoffrey supported this idea ·
-
4 votesGeoffrey shared this idea ·
-
4 votesGeoffrey supported this idea ·
-
16 votes
An error occurred while saving the comment Geoffrey commentedHave possibility the manage this limite by ourself.
Also as long as talked about safety. Target clusters for users can be identified. However, this cannot be done for "custom roles". This feature is important because currently, security by "custom role" is deployed on all clusters of a project. This forces us to create one project per cluster to be able to manage database access security.
Geoffrey supported this idea · -
5 votesGeoffrey supported this idea ·
-
23 votesGeoffrey supported this idea ·
-
3 votesGeoffrey supported this idea ·
-
6 votesGeoffrey supported this idea ·
I dont think is a good idea. We use this fonctionnality to protect the data and to be sure that a encrypted cluster can not be restore and anothers projects/environment (ex: cannot restore production data to dev).
I you need that. Restore on the same project to a new cluster. Disable encryption take a snapshot and restore to anoter project.