Vault egress NP update, new VPCCidr value added

Vault doesn't need to talk to the kube-api directly, but does need egress access to AWS API for things like KMS, S3, etc.

Adding new section to KMS doc recommending VPC Endpoints be configured for things like KMS & S3 to be able to further lock down Vault egress and traffic doesn't leave the AWS network.

Relates https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/944

added statusreview vault labels

added 1 commit

• eca6e65c - Vault egress update, new VPCCidr value

Compare with previous version

requested review from @gabe, @toladipupo, and @kavitha

approved this merge request

added 1 commit

• 955a9475 - Fleshing out comments for networkPolicies values

Compare with previous version

Do we want to name this variable to vpcCidr -- seems more consistent unless there are places where we start off vars in all caps?

approved this merge request

added 1 commit

• 8454ed1b - VPCCidr value to lowercase to match camel-case

Compare with previous version

resolved all threads

added 1 commit

• 69417776 - case change

Compare with previous version

approved this merge request

mentioned in commit 56373eb0

merged

mentioned in commit 84f0038e