Modify apparmor.md and delete .profile to enable the site to
build with Hugo 0.57.2. Could not cherry pick PR 16531 because
the Korean translation was added in 1.14.
Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>
Existing details related to services are ambiguous as it does not give an idea when to use an environment variable for service discovery. Also, it does not talk about the DNS method of service discovery which is highly recommended. so corrected document to provide these missing details.
per the godocs:
// RootCAs defines the set of root certificate authorities
// that clients use when verifying server certificates.
// If RootCAs is nil, TLS uses the host's root CA set.
* E2E testing blog post
* E2E testing blog post: add information about optional command line flags
* Update and rename 2019-03-30-e2e-testing-for-everyone.md to 2019-03-22-e2e-testing-for-everyone.md
Adds a link to a new nodejs client library. New library builds on top of the godaddy lib, providing useful kubectl-like abstractions like `get` and `updateOrCreate`, and adds API-mapping and version-handling so the client code does not need to worry about compatibility across cluster versions.
The tutorial has somebody expose this service externally, so they should be getting NodePort or LoadBalancer not ClusterIP. I followed this tutorial and that's what I got (as expected)
* 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
* Create Kubernetes-setup-using-Ansible-and-Vagrant.md
This blog describes the steps for to setting up a multi node Kubernetes cluster using Ansible and Vagrant.
* Apply suggestions from code review
Co-Authored-By: ljnaresh <naresh_lj@infosys.com>
* Markdown changes for syntax highting and reviews.
* Vagrant image & join command logic changes
* Update Kubernetes-setup-using-Ansible-and-Vagrant.md
* Adding author name and organization
* Markdown correction for colon
* Update Kubernetes-setup-using-Ansible-and-Vagrant.md
At its current form minikube fails to start with following error:
unknown flag: --AllowedUnsafeSysctls
Renaming it to allowed-unsafe-sysctls works as expected.
aimeeu