Ability for ApiServerSource to extract information from remote clusters.

[nachocano]

Problem
In #3295 we asked for feedback regarding Core Sources. One ask was to allow ApiServerSource to specify a kubeconfig in order to be able to point to a different cluster. See #3295 (comment).

Persona:
Developer

Exit Criteria
ApiServerSource can connect to a different cluster.

Additional context (optional)
See #3295

[grantr]

Decided against adding this for v1beta1. @arzarif how important is this feature for you?

[arzarif]

Hi @grantr - apologies for the delayed response. I'd say it's an important feature, but not a pressing one currently (for me anyway). The specific use case I had in mind was pulling in events from across multiple clusters into an event bus that resides within a centralized operations cluster; my intention was to be able to kick off Tekton-based pipelines from this operations cluster using these events.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[lionelvillard]

/remove-lifecycle stale

[Shashankft9]

I was also evaluating the best way to deploy knative in such architecture where there are multiple user clusters, to make it central I would run serving in just one cluster and this is where it would make sense to have eventing deployed in the same cluster as well and then the source to connect with different clusters using kubeconfig.
+1 for this feature

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.