Nic Cope

@stevendborrelli I don't think we can move all the `spec.composition*` fields to the Composition. There's a chicken and egg issue - those field specify what Composition and ref to use....

I _suspect_ this would fit well in https://github.com/crossplaneio/crossplane-cli, which powers the `kubectl crossplane` functionality, but I'm going to leave the issue here for now.

I'm increasingly thinking it might be more useful to build a tool that can create a Crossplane CR given a running external resource. This would help folks migrate from Terraform,...

Relates to https://github.com/crossplane/docs/issues/287.

> think we have this topic for future improvements for runtime-config To be explicit, we have no intention to support for alternative package deployment in core at this time. As...

> We would like to have Crossplane use functions that are managed or deployed by it. @MisterMX I just noticed - should this say "_aren't_ managed or deployed"?

Perhaps a bit meta, but I could imagine using a middleware function for this. i.e. You could deploy a function that proxied requests to some other function (or function-like service)...

@MisterMX Thanks for the context. I feel okay adding an `--insecure` flag to disable TLS. Per https://github.com/crossplane/crossplane/pull/5454#discussion_r1513329402 though, I don't think it should apply only to functions.

> When running Calico on an EKS cluster, the kubernetes control plane will still run on the AWS CNI (the control plane is completely managed by AWS and cannot be...

Adding a flag to providers (and core) to make the webhook port configurable sounds reasonable to me.