External secrets #323
Merged
External secrets #323
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added pages to index.md and mkdocs.yml - Updated for plain language and active voice @IanKWatts - In visual studio code the system is letting me know that Fenced code blocks should have language specified and provides this link: https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md040.md I am unsure how this affects the code blocks.
|
|
||
| ESO's main purpose to keep your Kubernetes Secrets in sync with external APIs. It uses custom resources `ExternalSecret` and `SecretStore` to provide a user-friendly abstraction for the external API that stores and manages the lifecycle of the secrets for you. | ||
|
|
||
| You install ESO in each cluster. It's **self-serve**, so you can: |
There was a problem hiding this comment.
do you mean "we installed ESO in each cluster, so you can self-serve"?
| A STRA for Vault has been completed by the Platform Services team. | ||
|
|
||
| ## Alternatives | ||
| If you would prefer to use a different secrets management system, you may use the External Secrets Operator to link your OpenShift namespace to an external service, such as AWS Secrets Manager or Azure Key Vault. See the [External Secrets Operator documentation](external-secrets.md) for more information. |
There was a problem hiding this comment.
maybe also mention that Openshift secure is now encrypted, so it's okay to use Openshift secret objects
|
|
||
| We recommend running the Azure CLI in a Docker or Podman container. Installing the CLI directly on your machine requires many dependencies, which might conflict with other tools or take up unnecessary space if you only need it for this task. | ||
|
|
||
| Make sure you have a running Docker ir Podman environment before starting. |
There was a problem hiding this comment.
Suggested change
| Make sure you have a running Docker ir Podman environment before starting. | |
| Make sure you have a running Docker or Podman environment before starting. |
Pilargit12
approved these changes
May 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add documentation for the External Secrets Operator to the 'Secrets management' section.