Repository navigation
docs: add External Secrets Operator v0.14.4 installation guide - #852
Merged
Merged
Conversation
This branch was successfully deployed
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
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.
Adds an installation guide for External Secrets Operator v0.14.4, the version now available in the Alauda Cloud marketplace for ACP 4.1, 4.2, 4.3 and 4.4.
Contents
OperatorConfig.kubernetesprovider).Validation: every command and YAML block was run unchanged on an ACP 4.3.2 cluster. Only the Vault and API-server addresses were filled in. Each claim was paired with a negative check. For example:
SecretSyncedErrorwhile the Secret keeps its last value;kubectl get operatorconfigresolves to the Ceph CSI kind on ACP, so the guide always uses the full resource name.The upgrade path is described from release testing on ACP 4.1, 4.2, 4.3.2 and 4.4.
The
id:field is omitted on purpose so CI assigns the KB id on merge; zh is generated by the translation job.🤖 Generated with Claude Code