In this Document Encrypting Secret data at REST, the example to verify
decrypt secret is bit confusing, on running
$ kubectl describe secret secret1 -n default
"should match mykey: mydata" never match because data is enoded,
This commit redirects it to decoding the secret
The current YAML doesn't work since hugepages requires you to include memory and/or CPU limits as well, or you get the error: "HugePages require cpu or memory".
* add examples using "rollout"
since "rolling-update" is deprecated, add example using "rollout"
* better deprecation reference
Referenced version where `rolling-update` was deprecated
Separated `rollout` example into it's own block
* update ol ul li bullet to disc
- update ol ul li bullet to disc
- move note out of list so that list numbers are correct
- fix typo
* futher clean-up
* rewrite of ingress
- reset and rewritten to provide more clarity and directness on what
ingress is and does.
* cleanup from review
- also normalized Ingress -> ingress through-out
* update documentation on CoreDNS
* Update dns-custom-nameservers.md
Fixed nit noted in comments and cleaned up a few more things while I was in there. This whole topic needs a complete redo, but this PR is an iterative improvment. Thanks!
* Added documentation about stringData
I've added some documentation about the stringData field, including a simple example showing how it can be used.
* fixup! Added documentation about stringData
* fixup! Added documentation about stringData
- Added a missing full stop.
- Separated the details on the --type flag under the respective section.
- Linked to the page on setting up Minikube locally.
- Introduced the VM abbreviation when used for the first time on the page.
In AWS cloud platform, omitting the name while initializing etcd cluster
causes "Couldn't find local name "$HOSTNAME in the initial cluster configuration"
It seems that the etcd tries to find short hostname, not the FQDN hostname.
To avoid this, passing the name explicitly to etcd configuration solved the problem.
[related issue1](https://github.com/coreos/bugs/issues/2054)
[related issue2](https://github.com/kubernetes/kubeadm/issues/653)
- The intro section had repeated text on visiting the community page. Refactored this content.
- Minor changes to content.
- Added links to Slack and the SIG docs mailing list.
* Copy-edit based on the style guide
Made the following changes:
- Used present tense.
- Removed latin phrases
- {{< tab name=“Content File #1” include=“example1” />}} was not shown as code. Updated it.
- Copy-edited the description for include under Tabs.
* Updated the text based on the comments
When starting minikube with
`--extra-config=apiserver.Authorization.Mode=RBAC`, the apiserver
container exits with the following error:
```
error: unknown flag: --Authorization.Mode
```
Starting it with `--extra-config=apiserver.authorization-mode=RBAC`
instead fixes the issue.
The first step of [1], kubeadm is necessary to be upgraded because we
need to run kubeadm upgrade plan. Then, the line shows `upgrade kubeadm:`.
However, the commandline contains kubelet also. That seens copy&paste
mistake and unnecessary. This removes it.
In addition, the format of another tab is broken. This fixes it also by
naming another tab.
[1]: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-12/#upgrade-the-control-plane
Liuduii
Sunghoon Kang
Kayce Basques
gparvind
Daniel Bastos
Karen Bradshaw
Qiming
Joseph Heck
yongsong you
yanghaichao12
adisky
Cliff Burdick
Anastas Dancha
Benedikt Franke
Stig Otnes Kolstad
Sandeep Rajan
Adam Connelly
Bernat Moix
CaoShuFeng
Jordan Liggitt
Will Beason
Quy Le Ngoc
shavidissa
hongkunyoo
Aivars Sterns
Rohit Agarwal
Chao Wang
hintss
nepomucen
Jay
Mumshad Mannambeth
Stéphane Este-Gracias
Indradhanush Gupta
Pierre-Yves Aillet
Nikhita Raghunath
erganzi
Pingan
Kenichi Omichi
William Zhang