-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Add doc on OpenStack provider #74
Add doc on OpenStack provider #74
Conversation
@zreigz, please, note that OpenStack CLI clients like I suppose, it will be useful to modify your existing documentation with these updates. |
3f4cf65
to
fb8c3c0
Compare
Thanks for comment. I've already added this information |
As we have discussed on Kubernetes/OpenStack-SIG Slack channel and bi-weekly meeting, the "default" OpenStack provider for I'd like to suggest to put this document to the "Custom solutions" section and name as "OpenStack with Heat" or something similar. |
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
44693ce
to
a4fe129
Compare
Yeah, once the kube-up provider gets merged, we should ping someone to merge this. Also, to bypass CLA-bot: I consent to have this commit merged in. |
342310a
to
3b35a7a
Compare
@elsonrodriguez @zreigz please, add to the prerequisites section information about the cluster minimal requirements to deploy the solution (cluster size requirements, necessary components to be enabled, i.e. Heat etc.) |
…irements Adding a list of OpenStack requirements for provider docs.
…irements Revised requirements for OpenStack kube-up provider.
@idvoretskyi PTAL |
@quinton-hoole PTAL, now that the kube-up provider is merged, we need an M for people to RTF out of. |
Once kube-up is finished, your cluster should be running: | ||
|
||
```console | ||
./cluster/kubectl.sh get cs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From kubectl.sh:
# echo "NOTE:"
# echo "kubectl.sh is deprecated and will be removed soon."
# echo "please replace all usage with calls to the kubectl"
# echo "binary and ensure that it is in your PATH."
# echo ""
# echo "Please see 'kubectl help config' for more details"
# echo "about configuring kubectl for your cluster."
# echo "-=-=-=-=-=-=-=-=-=-="
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, please use clusterstatuses, rather than cs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding the kubectl.sh, I've subscribed to this: kubernetes/kubernetes#8817
In terms of user experience, kubectl.sh provides the easiest way to start with k8s, especially from the get.k8s.io perspective (curl | bash
).
Once kubectl.sh has been converted to an installer for kubectl, I'll update the docs accordingly.
For a simple test, issue the following command: | ||
|
||
```sh | ||
./cluster/kubectl.sh run nginx --image=nginx --generator=run-pod/v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As above.
@elsonrodriguez Minor nits. Happy to address those in a separate PR. |
We can fix any problems in follow-ups. |
…gyGmbH/openstack-provider-doc Add doc on OpenStack provider
admin-tls-bootstrapping-pr-20170815
Signed-off-by: Anurag Paliwal <apaliwal@adobe.com>
This documentation is related to pull request: kubernetes/kubernetes#21737