Update Vault Cluster Install Documentation
What does this MR do?
Our documentation on using GitLab CI/CD to install Vault in a managed cluster does not make it clear how to expose Vault outside of the cluster. While this may not be a desirable production configuration, it does seem like a common approach for a first-time proof of concept. For example; a user on Gitlab.com deploying vault to a managed cluster, but running CI jobs on our SaaS shared runners (i.e. off cluster).
For new vault users, leveraging the UI may also be beneficial in understanding the state and structure of the secrets within vault.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team