feat(vault-config): crossplane v2 namespaced XRD#69
Merged
patrick-hermann-sva merged 1 commit intomainfrom Apr 14, 2026
Merged
Conversation
Rework the vault-config configuration to match the v2 namespaced pattern established in vault-auth, and bump to xplane-vault-config 0.4.0 on the KCL module side. - XRD: apiextensions.crossplane.io/v2, scope: Namespaced, drop claimNames (v2 XRs are namespaced directly). Composite kind renamed from XVaultConfig to VaultConfig to match the existing example files and the sibling vault-auth style. - XRD: add providerConfigName + namespace spec fields; drop the connectionSecret block (not wired into the KCL module). - Composition: target new VaultConfig kind, use KCLInput (not the deprecated KCLRun), bump source to xplane-vault-config:0.4.0, and add the auto-ready step that vault-auth uses. - Examples: drop connectionSecret / writeConnectionSecretToRef (no longer in the schema), align ESO chart version to 0.11.3, refresh claim.yaml with providerConfigName + realistic k8sAuths. - functions.yaml: bump function-kcl to v0.12.1 (verified on k3s in the earlier vault-auth migration) and add function-auto-ready. Verified with `crossplane render examples/claim.yaml apis/composition.yaml examples/functions.yaml` — every composed Release/Object now lands in the XR's metadata.namespace with providerConfigRef.name honoring spec.providerConfigName. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
Rework the
vault-configbootstrap configuration to match the v2 namespaced pattern established invault-auth, and consumexplane-vault-config:0.4.0.apiextensions.crossplane.io/v2,scope: Namespaced, dropsclaimNames. Composite kind renamed fromXVaultConfigtoVaultConfigto match the existing example files and the sibling vault-auth style.providerConfigName+namespacefields; drop theconnectionSecretblock (not wired into the KCL module).VaultConfigkind, useKCLInput(not deprecatedKCLRun), bump source toxplane-vault-config:0.4.0, add thefunction-auto-readystep.connectionSecret/writeConnectionSecretToRef, align ESO chart to0.11.3, refreshclaim.yamlwithproviderConfigName+ realistick8sAuths.function-kcltov0.12.1and addfunction-auto-ready:v0.4.0.Test plan
crossplane render examples/claim.yaml apis/composition.yaml examples/functions.yaml— every composedRelease/Objectlands in the XR'smetadata.namespaceandproviderConfigRef.namehonorsspec.providerConfigNamefunction-kcl:v0.12.1examples/claim.yamlas a namespacedVaultConfigand confirmSynced=True, Ready=TrueGenerated with Claude Code