Skip to content

Commit df2b266

Browse files
authored
Update policies.md
Added policy to use a custom key to encrypt etcd
1 parent 81e7d53 commit df2b266

File tree

1 file changed

+10
-0
lines changed
  • app-dev/devops-and-containers/oke/oke-policies

1 file changed

+10
-0
lines changed

app-dev/devops-and-containers/oke/oke-policies/policies.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,16 @@ UNCLEAR: Maybe this policy is necessary for every IPv6 cluster
2828
Allow any-user to use ipv6s in compartment <compartment-ocid-of-network-resources> where all { request.principal.id = '<cluster-ocid>' }
2929
```
3030

31+
32+
### ENCRYPT ETCD WITH A KEY
33+
34+
To encrypt etcd secrets at rest using a custom key, this needs to be specified at cluster creation and the following policy must be in place:
35+
36+
[https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengencryptingdata.htm#console](https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengencryptingdata.htm#console)
37+
38+
```
39+
Allow any-user to use keys in compartment <compartment-name> where ALL {request.principal.type = 'cluster', target.key.id = '<key-ocid>'}
40+
```
3141

3242

3343
### ENCRYPT BOOT VOLUME WITH KEY

0 commit comments

Comments
 (0)