cloud-provider icon indicating copy to clipboard operation
cloud-provider copied to clipboard

Improving OpenStack Integration Docs

Open andrewsykim opened this issue 6 years ago • 13 comments

OpenStack integration docs should be updated as per https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20180731-cloud-provider-docs.md

andrewsykim avatar Feb 12 '19 20:02 andrewsykim

/help

andrewsykim avatar Feb 12 '19 20:02 andrewsykim

@andrewsykim: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

/help

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.

k8s-ci-robot avatar Feb 12 '19 20:02 k8s-ci-robot

/assign @hogepodge @dims

andrewsykim avatar Feb 19 '19 20:02 andrewsykim

/milestone v1.15 /priority critical-urgent

andrewsykim avatar Mar 20 '19 20:03 andrewsykim

/assign @hogepodge /unassign @dims

dims avatar Apr 16 '19 11:04 dims

@hogepodge should this still be p0 for v1.16?

andrewsykim avatar Jul 10 '19 21:07 andrewsykim

Yes.

hogepodge avatar Jul 16 '19 22:07 hogepodge

/assign @adisky

andrewsykim avatar Oct 02 '19 20:10 andrewsykim

cc @kendallnelson

andrewsykim avatar Oct 02 '19 21:10 andrewsykim

@andrewsykim it is returning 404 https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0019-cloud-provider-documentation.md could you help me where to update the docs?? we maintain docs here https://github.com/kubernetes/cloud-provider-openstack/tree/master/docs, is it needs to be updated in k/website?

adisky avatar Oct 09 '19 05:10 adisky

got it https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20180731-cloud-provider-docs.md

adisky avatar Oct 09 '19 05:10 adisky

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

fejta-bot avatar Jan 07 '20 17:01 fejta-bot

/remove-lifecycle stale /lifecycle frozen

andrewsykim avatar Jan 22 '20 21:01 andrewsykim