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
[blog] Adding introduction blog on KubeEdge - 2019-03-12-kubeedge-k8s-based-edge-intro.md #13158
Conversation
Initial created.
Adding KubeEdge High Level Arch img for the blog
Adding KubeEdge Logo img for blog
Updated all the sections for KubeEdge, a k8s based edge computing platform. (2019-03-12-kubeedge-k8s-based-edge-intro)
Minor format updates
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
cc @stewart-yu |
Deploy preview for kubernetes-io-master-staging ready! Built with commit 36e1d8a https://deploy-preview-13158--kubernetes-io-master-staging.netlify.com |
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.
Thanks for your PR @skdwriting 👍
And need CLA
/assign @kbarnard10 for review either
content/en/blog/_posts/2019-03-12-kubeedge-k8s-based-edge-intro.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2019-03-12-kubeedge-k8s-based-edge-intro.md
Outdated
Show resolved
Hide resolved
2. Clone and Build KubeEdge Cloud and Edge | ||
3. Run Cloud | ||
4. Run Edge | ||
|
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.
have format error, may be need blank line
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.
Sorry , could not make out the issue.
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.
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.
see the preview, please
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.
content/en/blog/_posts/2019-03-12-kubeedge-k8s-based-edge-intro.md
Outdated
Show resolved
Hide resolved
@skdwriting Please sign CLA. |
Signed the CLA. Thanks. |
cc @CindyXing for IOT/Edge wg opinion. |
Review of @stewart-yu fixed for KubeEdge/kubeedge link
ping me back after all tech review done |
Linefeed update.
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.
Currently there are a few kubernetes based solutions for edge workload including KubeEdge, Rancher K3s and Virtual Kubelet. There are can more. Different from K3s and virtual kubelet, KubeEdge has its control plane at cloud; and each edge node runs as a worker node in the cluster. Here edge is considered as an extension of cloud. The whole thing is a K8s cluster.
The benefits of KubeEdge are to save resource overhead if run cluster at each edge location; and save OPs cost.
We should call these out and clarify the position KubeEdge project holds.
KubeEdge control plane in cloud and extension part made it mode clear.
@CindyXing, thanks for the comments. It helps. Note: somehow, did not see the reply option to your comment, hence added as a new comment |
Done technical review. LGTM. Thanks. |
Per @CindyXing, we have done the technical review. Please give a final approval. Thanks! |
@m1093782566 Great - thanks! Will get this published first thing tomorrow. |
Cool! Thanks! |
/approve |
@stewart-yu @kbarnard10 @zacharysarah @CindyXing , Thanks a lot. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kbarnard10, stewart-yu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…-based-edge-intro.md (#13158) * Create 2019-03-12-kubeedge-k8s-based-edge-intro.md Initial created. * Create kubeedge-highlevel-arch.png * Adding KubeEdge High Level Arch img Adding KubeEdge High Level Arch img for the blog * Adding KubeEdge Logo img Adding KubeEdge Logo img for blog * Updated KubeEdge intro blog Updated all the sections for KubeEdge, a k8s based edge computing platform. (2019-03-12-kubeedge-k8s-based-edge-intro) * Update 2019-03-12-kubeedge-k8s-based-edge-intro.md Minor format updates * Update 2019-03-12-kubeedge-k8s-based-edge-intro.md * [ReviewFix] 2019-03-12-kubeedge-k8s-based-edge-intro.md Review of @stewart-yu fixed for KubeEdge/kubeedge link * [ReviewFix] Format 2019-03-12-kubeedge-k8s-based-edge-intro.md Linefeed update. * Update 2019-03-12-kubeedge-k8s-based-edge-intro.md * Update 2019-03-12-kubeedge-k8s-based-edge-intro.md * [ReviewFix] 2019-03-12-kubeedge-k8s-based-edge-intro.md KubeEdge control plane in cloud and extension part made it mode clear. * Update 2019-03-12-kubeedge-k8s-based-edge-intro.md * Rename 2019-03-12-kubeedge-k8s-based-edge-intro.md to 2019-03-19-kubeedge-k8s-based-edge-intro.md * Update 2019-03-19-kubeedge-k8s-based-edge-intro.md
Adding a blog post on Introduction to KubeEdge, a Kubernetes based Edge computing platform.
2019-03-12-kubeedge-k8s-based-edge-intro.md and related images.
Please note that KubeEdge team is also collaborating with Kubernetes IOT/EDGE WORKING GROUP. Also KubeEdge is one of the reference architecture discussed in the workgroup.