Document how certs are handled in Big Bang

BB-850

As a BB package engineer, I need to understand how BB package dependencies are handled so that I can make sure to implement so that BB will properly enforce the dependency.

There are two types of dependencies: dedicated and shared. With dedicated dependencies, I believe we already decided that the package will own deploying and configuring the dependency. An example would be a database specifically for the package. For shared dependencies, we have not decided. The user can probably assume items like istio and cert-manager are available. But what about something like minio?

added to epic &24 (closed)

changed the description

added BB Documentation Standards label

added 1 deleted label

added teamcore/security label

added priority8 label

added stale label

changed epic to &190 (closed)

removed stale label

added stale label

@killian.byrne this issue has been inactive for 60 days and is being labelled as marked-for-auto-close. If this issue is still required please take action by removing the stale and marked-for-auto-close labels and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken it will be auto closed in 30 days.

added marked-for-auto-close label

removed stale label

@killian.byrne this issue has been inactive for 30 days and is being labelled as stale. If this issue is still required please take action by removing the stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 60 days.

added stale label

added delete-me label

@killian.byrne this issue has been closed due to the label delete-me.

closed

mentioned in commit d98af2b4

mentioned in commit b240f0f1

mentioned in commit 83ce32d9

mentioned in commit a90f5811

mentioned in commit 2ec2552e

mentioned in commit a1004a1b

mentioned in commit f0edb1c3

mentioned in commit f3bf748f

mentioned in commit c204cf8d

mentioned in commit 0a2a2488

mentioned in commit 5a5528b3