Hasan Turken
Hasan Turken
ComposeResources behaviour is inconsistent when the spec of Composed Resource is not fully specified
Just hit this issue while trying to give a [deterministic name](https://github.com/crossplane/crossplane/issues/3120) to my composed resource. Thanks @ytsarev for the dummy value workaround.
@codes4coffee ACK regarding adding/improving docs. Do you mean writing secrets into the same Kubernetes cluster similar to the existing `writeConnectionSecretToRef` API? If yes, you don't have to do anything for...
@uluzox responded [here](https://github.com/crossplane-contrib/provider-kubernetes/issues/35#issuecomment-1104020537). But the short answer is XRs are not namespace hence `metadata.namespace` is not set.
@dee0sap thanks for the issue! Actually, we don't have a direct dependency to Vault itself, we depend on the following packages from `Vault` repository: ``` github.com/hashicorp/vault/api v1.3.1 // indirect github.com/hashicorp/vault/sdk...
Just opened [this](https://github.com/crossplane/crossplane-runtime/pull/327) if it helps.
@dee0sap that would be great, thanks! Just built/pushed `turkenh/crossplane:vault-update` from #3035.
@bobh66 yes, you can either define a new service account with enough permissions and pass it to the provider using controller config or you can grab existing SA for an...
I was about to create a new issue titled "Deploy time parameters for configuration packages" with the same arguments and found this issue. @marcinc explained the reasoning pretty well and...
From Turkey, on a Mac with `kubectl` `v1.23.3`: ```bash $ kubectl version Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:25:17Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.9-eks-a64ea69", GitCommit:"540410f9a2e24b7a2a870ebfacb3212744b5f878", GitTreeState:"clean",...
@enrichman this is expected to happen when the secret has an owner other than the MR itself which is the `DynamoDBTable` here. Did you check who owns that secret, i.e....