Hasan Turken
Hasan Turken
> For this specific use case, would it make sense to have your Helm chart create a type: NodePort service? Then your composition could create a load balancer as a...
I remember that we have discussed [similar](https://github.com/crossplane/crossplane/pull/2494#discussion_r733313923), [capabilities]((https://github.com/crossplane/crossplane/pull/2494#r696081422)) during the design and ended up choosing not to support publishing to multiple secrets/stores in favor of simplification especially considering this would...
@Shadowraze228 [publishConnectionDetailsWithStoreConfigRef](https://doc.crds.dev/github.com/crossplane/crossplane/apiextensions.crossplane.io/Composition/[email protected]#spec-publishConnectionDetailsWithStoreConfigRef) in the composition spec works similar to the deprecated [writeConnectionSecretsToNamespace](https://doc.crds.dev/github.com/crossplane/crossplane/apiextensions.crossplane.io/Composition/[email protected]#spec-writeConnectionSecretsToNamespace) field: > PublishConnectionDetailsWithStoreConfig specifies the secret store config with which the connection secrets of composite resource dynamically provisioned...
> @turkenh yep, it's my case I see, then I would say it is expected since one is the secret for the claim and the other is the secret for...
We are starting to work on this ticket, you can expect a design PR soon 🚀
Closing as a duplicate of https://github.com/crossplane/crossplane/issues/3393
Rather than extending the composition API further, I would also prefer to lean on the composition functions as a solution here especially given we already have a [workaround](https://github.com/crossplane/crossplane/issues/2772#issuecomment-1141492865) whenever that...
> In order to discuss further its API, perhaps it would make sense to open a new issue for it? I was more interested in how a possible API could...