Project 'platform-one/big-bang/apps/sandbox/vault' was moved to 'big-bang/product/packages/vault'. Please update any links and bookmarks that may still have the old path.
more restrictive network policies
All threads resolved!
All threads resolved!
Edited by Ryan Garcia
Merge request reports
Activity
assigned to @michaelmartin
added vault label
added 3 commits
-
635f4d7b...458cbfc5 - 2 commits from branch
main - e4b70e3a - Merge remote-tracking branch 'origin/main' into
-
635f4d7b...458cbfc5 - 2 commits from branch
requested review from @ryan.j.garcia
requested review from @gabe
requested review from @toladipupo
requested review from @kavitha
Resolved by Michael Martin@gabe pointed out and helped with understanding the default blocking of the 169.254.169.254 address. the vault-vault-0 (server) pod needs access, so I the egress-metadata.yaml now allows the vault server access.
Tested the rules on an ec2 instance to make sure the server started up and was able to auto unseal on restart. verified access to 169.254.169.254 was blocked by default on the other/vault-vault-agent-injector pod.
- Last reply by Michael Martin
added statusreview label
mentioned in commit 2050080b
mentioned in commit f8b82cd5
Please register or sign in to reply