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.

Sign up for GitHub

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

Jump to bottom

HTTPProxy: Update printer columns #1567

Closed
1 of 3 tasks
stevesloka opened this issue Sep 24, 2019 · 3 comments
Closed
1 of 3 tasks

HTTPProxy: Update printer columns #1567

stevesloka opened this issue Sep 24, 2019 · 3 comments
Labels
area/httpproxy Issues or PRs related to the HTTPProxy API. area/status Issues or PRs related to exposing status for APIs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@stevesloka
Copy link
Member

stevesloka commented Sep 24, 2019 •
edited by davecheney
Loading

Describe the solution you'd like
Need to fix up the printer columns used to show HTTPProxy CRDs when using kubectl.

Currently breaking issues:

  • Fix "first route" column

New Features:

  • Show root vs child Proxy
  • Separate HTTP vs TCP Proxy implementations
@stevesloka stevesloka added this to the 1.0.0-rc.1 milestone Sep 24, 2019
@davecheney davecheney modified the milestones: 1.0.0-rc.1, 1.0.0-rc.2 Sep 29, 2019
@davecheney davecheney added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Oct 11, 2019
@davecheney davecheney mentioned this issue Oct 17, 2019
Closed
@youngnick
Copy link
Member

All of these features are not deliverable without adding extra information into the status: area.

For 1.0.0-rc.2, I'll remove the 'first route' column, since it does nothing on HTTPProxy anyway, then this will go back on the backlog, blocked behind figuring out what to do about status.

youngnick pushed a commit to youngnick/contour that referenced this issue Oct 25, 2019
Remove 'first route' print column from HTTPProxy CRD
7d742a9 
Updates projectcontour#1567.

Signed-off-by: Nick Young <[email protected]>
@youngnick youngnick mentioned this issue Oct 25, 2019
Merged
youngnick pushed a commit that referenced this issue Oct 25, 2019
@youngnick
Remove 'first route' print column from HTTPProxy CRD
0bc1f2f 
Updates #1567.

Signed-off-by: Nick Young <[email protected]>
@davecheney davecheney modified the milestones: 1.0.0-rc.2, Backlog Oct 25, 2019
@davecheney davecheney removed help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. httpproxy/v1alpha1 labels Oct 25, 2019
@jpeach jpeach added the area/httpproxy Issues or PRs related to the HTTPProxy API. label Nov 12, 2019
@youngnick youngnick added the area/status Issues or PRs related to exposing status for APIs. label Dec 9, 2019
@skriss skriss removed this from the Backlog milestone Jul 25, 2022
@github-actions GitHub Actions
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@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 Jul 21, 2024
@github-actions GitHub Actions
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/httpproxy Issues or PRs related to the HTTPProxy API. area/status Issues or PRs related to exposing status for APIs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@davecheney @jpeach @stevesloka @skriss @youngnick