Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sources.* resources v1beta1 meta umbrella task #3529

Closed
4 tasks done
lionelvillard opened this issue Jul 7, 2020 · 7 comments
Closed
4 tasks done

sources.* resources v1beta1 meta umbrella task #3529

lionelvillard opened this issue Jul 7, 2020 · 7 comments

Comments

@lionelvillard
Copy link
Member

lionelvillard commented Jul 7, 2020

Here the list of sources to move to v1beta1, with additional features based on feedback, and tentative assignment:

@capri-xiyue
Copy link
Contributor

capri-xiyue commented Jul 16, 2020

I'm willing to work on ApiServerSource. @nachocano @lionelvillard Can you help add my name for the apiserversource? I don't have the permission to modify that part.

@nachocano
Copy link
Contributor

I'm willing to work on ApiServerSource. @nachocano @lionelvillard Can you help add my name for the apiserversource. I don't have the permission to do that part.

Awesome, done! Thanks Xiyue!

@capri-xiyue
Copy link
Contributor

capri-xiyue commented Jul 16, 2020

@lionelvillard @n3wscott @nachocano
Just wanna clarify some questions for ApiServerSource.

  1. Have the opensource community decided that v1beta1 ApiServerSource is gonna support filtering on a resource's name? Or the additional feature requests needed for v1beta1 ApiServerSource is still under discussion?
  2. For the filtering on a resource's name, does it mean that we will have ApiServerSource Spec similar to this:
apiVersion: sources.knative.dev/v1alpha1
kind: ApiServerSource
metadata:
  name: testnamespace
  namespace: default
spec:
  serviceAccountName: events-sa
  mode: Resource
  resources:
    - apiVersion: v1
      kind: Namespace
      name: filternamespace

And it supports send events for add, update, delete of v1 namespace with name filternamespace

  1. The addition feature request is for v1beta1, right? Is it ok that I move ApiServerSource to v1beta1 first and then work on the additional feature request?

  2. Besides the possible API change needed for additional feature request like filtering on a resource's name, do we need to do any other API change for v1beta1 ApiServerSource?

@lionelvillard
Copy link
Member Author

My take on this:

  1. I think we should go for it
  2. I would consider supporting field selector which support name selector.
  3. yes
  4. maybe an optional way to connect to another cluster.

@capri-xiyue
Copy link
Contributor

@lionelvillard Thanks for the clarification!

@nachocano
Copy link
Contributor

Assigning it to Lionel as he is working on the last piece missing, the PingSource updates.
/assign @lionelvillard

@lionelvillard
Copy link
Member Author

PingSource is now done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants