added powershell equivalent for eval $(minikube docker-env), and added some text to help a beginner understand in more concrete terms the difference between the local docker registry, and the one in minikube (might only be an issue for newbs, but I am a newb :) and limited to powershell :().
* improved and updated rollout history information
* minor change, manifest.yaml > manifest
* tweaks to the change-cause section
* annotation command typo
* redundancy fix
* removing the --record flag as it may be misleading
* resolve some semantics around ABAC and RBAC
some minor tweaks for readability.
* Update abac.md
* Update abac.md
* Update abac.md
* Update abac.md
* Update abac.md
We have a redirect, so these links aren't broken, but we shouldn't
rely on the redirect - that ends up with long chains of complicated
redirects and makes validating the markdown harder.
* Capitalized "Pod" in multiple locations
This style guide states to always capitalize Pod, but in the next section it was written in lowercase in a couple places. I've capitalized them.
* Capitalized two additional instances of "Pod" as recommended by @neolit123
[Jaguar](https://gitlab.com/sdnlab/jaguar) is an open source solution for Kubernetes's network based on OpenDaylight.
Jaguar provides overlay network using vxlan and Jaguar CNIPlugin provides one IP address per pod.
StatefulSet deletion does not have any guarantees of orderly termination of pods as is suggested by the documentation. Prior to 1.11 kubectl did scale down StatefulSets before deleting them, but this went away after the removal of reapers. Ref discussion in #68627.
This change updates the documentation to reflect this.
Wording is confusing to beginners - in the sentence before, it is just being explained that containers in the same pod are indeed run on the same physical host. Hopefully this clarifies that.
Cancel the invalid hyperlink
Cancel the invalid hyperlink
Cancel the invalid hyperlink
Cancel the invalid hyperlink
Cancel the invalid hyperlink
Cancel the invalid hyperlink
The CentsOS/RHEL/... section mentiones that SELinux must be put in permissive
mode, but the supplied command does the job only for the current boot. Once
the system is restarted SELinux can again enter enforcing mode thus breaking
a Kubernetes cluster.
Fix this by adding a sed command that permanently changes the SELinux mode to
permissive.
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
GKE On-Prem | Google Cloud
https://cloud.google.com/gke-on-prem/
Containerize on-premises applications and be cloud-ready. With GKE On-Prem, you get the Google Kubernetes Engine (GKE) experience directly in your data center. ... GKE On-Prem also registers your cluster with Google Cloud Console in order to have a single-pane-of-glass view for managing all your clusters.
* Add new Sass generation system
* Remove resources folder
* Add develop Sass command and sourcemaps
* Add Hugo version shortcode for use in docs
* Add OWNERS file to ./sass folder
bobs-bits
Miguel Angel Medina Mondragon
Tim Allclair (St. Clair)
LiuDui
tanshanshan
jay vyas
Justin Santa Barbara
alex-libre
DennyZhang - DevOps & Cloud Native
JJ Asghar
Preston Holmes
PONOUBA
Shen Yuanyu
Denis Salamanca
Thomas Strömberg
Florian Breisch
CaoShuFeng
SataQiu
Justin Clift
Morten Torkildsen
Karen Bradshaw
Robert Edström
caberdoz
Misty Linville
Luc Perkins
Rostislav M. Georgiev
Zach Corleissen
makocchi
Dennis Czombera
Kevin Kelani
Eyal Levin
stephan lindauer
Chao Wang
Pieter Vogelaar
PatMaz
Stanislas
Chazzledazzle1
Rui Cao
shutefan
Lubomir I. Ivanov
Jim Angel
Nilekh Chaudhari