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

Ingress-GCE docs overhaul #557

Closed
rramkumar1 opened this issue Nov 26, 2018 · 6 comments
Closed

Ingress-GCE docs overhaul #557

rramkumar1 opened this issue Nov 26, 2018 · 6 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@rramkumar1
Copy link
Contributor

Using this issue to track the work being done to revamp the documentation in this repository.

/assign

@rramkumar1
Copy link
Contributor Author

/kind documentation

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Nov 26, 2018
@rramkumar1 rramkumar1 changed the title Ingress-GCE docs makeover Ingress-GCE docs overhaul Nov 26, 2018
@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 Feb 24, 2019
@rramkumar1 rramkumar1 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 12, 2019
@zvictor
Copy link

zvictor commented May 23, 2019

I am confused by the way it has been done.
Why deleting all the old docs before having new ones? What is the point of keeping users in the limbo with no place to check?

@rramkumar1
Copy link
Contributor Author

rramkumar1 commented Jun 4, 2019

@zvictor I'm not sure why you think we deleted old docs before having new ones. Only material that was severely outdated was outright deleted.

Everything else has either been updated already or left in place until there is a suitable replacement.

@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 Sep 2, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 2, 2019
@rramkumar1 rramkumar1 removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

No branches or pull requests

4 participants