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

GCP Description field is blank #661

Closed
thockin opened this issue Mar 4, 2019 · 4 comments
Closed

GCP Description field is blank #661

thockin opened this issue Mar 4, 2019 · 4 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@thockin
Copy link
Member

thockin commented Mar 4, 2019

Service LBs populate the description field with helpful information. I see GCE ingress does not do that for things like forwarding rules. Would be helpful in UIs.
@rramkumar1 rramkumar1 added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 4, 2019
@rramkumar1 rramkumar1 added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Mar 27, 2019
@KatrinaHoffert
Copy link
Contributor

I assume this is referring to the descriptions on the load balancer forwarding rules like shown below?

Image of GCP console

This seems to only be visible in the advanced menu, when viewing the forwarding rule directly, or with the likes of gcloud compute forwarding-rules describe (noting this since it took me some testing to find what was likely referred here).

Anyway, looking into this one.

@KatrinaHoffert KatrinaHoffert mentioned this issue May 24, 2019
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 19, 2019
@thockin
Copy link
Member Author

thockin commented Aug 19, 2019

/lifecycle frozen
/remove-lifecycle stale
/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 19, 2019
@Aut0R3V
Copy link

Aut0R3V commented Jan 7, 2021

@thockin can we close this issue? I think that #757 solves the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@KatrinaHoffert @swetharepakula @thockin @k8s-ci-robot @rramkumar1 @fejta-bot @Aut0R3V