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

As a Knative administrator, I want to list autoscaling configs which apply to overall Knative platform. #15

Closed
zhanggbj opened this issue Nov 5, 2020 · 5 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@zhanggbj
Copy link

zhanggbj commented Nov 5, 2020

Move from knative/client-contrib#44

Please refer to #14 for all the configs need to list

@zhanggbj zhanggbj changed the title [kn-admin]As a Knative administrator, I want to list autoscaling configs which apply to overall Knative platform. As a Knative administrator, I want to list autoscaling configs which apply to overall Knative platform. Nov 5, 2020
@zhanggbj
Copy link
Author

zhanggbj commented Nov 5, 2020

/assign @chaozbj
per offline discussion, Chao would like to take care of it.

@knative-prow-robot
Copy link

@zhanggbj: GitHub didn't allow me to assign the following users: chaozbj.

Note that only knative-sandbox members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @chaozbj
per offline discussion, Chao would like to take care of it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@chaozbj
Copy link
Contributor

chaozbj commented Nov 6, 2020

/assign

navidshaikh added a commit to navidshaikh/kn-plugin-admin that referenced this issue Dec 16, 2020
replace toc members in OWNERS file with their alias technical-oversight-committee
@github-actions
Copy link

github-actions bot commented Feb 5, 2021

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2021
@zhanggbj
Copy link
Author

PR merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants