* Add files via upload
Custom Resource Definition, that replaces Third Party Resources.
* Update customresourcedefinition.yaml
Minor formating error
* Update customresourcedefinition.yaml
missing id key
* Update customresourcedefinition.yaml
deleted aka key
* Update customresourcedefinition.yaml
Made a minor edit to "name" and "id" and added "aka" section, but should require a "related" section. The related section may have the Custom Resource term, but there is currently no glossary term for Custom Resource.
* Replace old zkOk.sh livenessProbe by zookeeper-ready
Fixes one part of the issue #7287
* Update probe script content with the zookeeper-ready
Fixes the part with shows/explains the probe script at issue #7287
* Fix the path to delete liveness probe
Issue #7287
* Replace zkOk.sh readinessProbe by zookeeper-ready
Fixes "Testing for Readiness" section in issue #7287
* Add instructions to remove docker images; fixes#6874
On cleanup of Minikube, adds instructions to optionally remove Docker images created in tutorial setup
* update wording of instructions to include flag
Updates the wording to explicitly match the shell command and flags used.
If we are getting releases from the stable channel, I think the plan output would say stable instead of experimental. At least, that is what I see in this video, around 40:15 mins in: https://www.youtube.com/watch?v=x9doB5eJWgQ&feature=youtu.be
* Update on install-kubectl.md
Added more info on the reason people may get "the connection to the server was refused error". It will help newbies understand the kubectl is a client that connects to a cluster. Hence, a Kubernetes cluster such as a minikube tool will be needed to verify that kubectl is functioning correctly.
* updating wording to remove redundancy
* Updates to Component Overview
* Changed VMs to machines -- it can be both VM or physical machine.
* Separated Addons from Master section, since it depends on an addon if it's components are executed on Master or Node.
* Fix ID of Kubelet glossary
* Removed fluentd and supervisord
These are not necessary to mention here in the overview.
* fluentd is one of Cluster-level Logging solutions briefly described in Addons Section
* supervisord is not required to be run on the Node
* Requested change - remove Addons manager reference
* After review updates
* Updated the Addons page reference