* 593 Add password requirments
* re-organize page to use tabs, remove redundant material
* eng: Bootstrap password has no validation/length requirements, subsequent admin passwords must be 12 chars or longer
* update quickstart guides with link to password requirments
* link to content in setting up bootstrap password
* Apply suggestions from code review
Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com>
* suggestions from code review
* update password requirements
* helm cli
* fix link
* another link
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
* sync 2.8
* syncing 2.7
* adding in helm-cli sync for 2.7 & 2.8
---------
Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com>
Co-authored-by: Billy Tat <btat@suse.com>
* Update aws-marketplace.md
Edit link to new listing. Remove link to outdated doc.
Remove outdated youtube video.
New video is forthcoming under separate PR.
* Update docs/getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md
Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
* Update docs/getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md
Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
* versioning
---------
Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
Co-authored-by: martyav <marty.avedon@suse.com>
* vagrant quickstart retitled for consistency
* rm number from title
* 2. rm number from title
* 3. rm number from title (Istio related, as were 2 prev)
* 4. rm number from title (Istio related)
* 5. rm number from title (Istio related)
* 6. rm number from title (Istio related)
* making backup 'examples' title more specific
* rewrite + making monitoring 'examples' title more specific
* suggestions from Btat
correcting capitalization for github, combining two lines into one
* versioning previous commit
* applying sunil's suggestions
rm'ing numbers from titles of pages missed in 2.0-2.4
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
---------
Co-authored-by: Billy Tat <btat@suse.com>
Originally added due to some unexpected versioning behavior that's no longer reproducible
Apply suggestions from code review
Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
* canonicized helm-cli quickstart
* canonicized hetzner quickstart
* canonicized outscale quickstart
these pages are very strange
they have no sidebar but are still accessible if you search for them via algolia
* fixing link in last commit
* canonicized vagrant quick start
* canonicized work-load-w-ingress quick start
* canonicized nodeports quick start
A new to k3s user might get "surprised" by error messages from kubectl
or k3s like:
WARN[0000] Unable to read /etc/rancher/k3s/k3s.yaml, please start server with --write-kubeconfig-mode to modify kube config permissions
error: error loading config file "/etc/rancher/k3s/k3s.yaml": open /etc/rancher/k3s/k3s.yaml: permission denied
It can happen when there is a k3s installed on the same machine and
`/etc/rancher/k3s/k3s.yaml` present.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
Instead of sending user to find the real number k3s tag format,
just give recent version of k3s which is needed by latest
rancher.
It would be great to update this value automatically, but I have
no good idea how to do this at the moment.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
Move the clause about INSTALL_K3S_VERSION before get.k3s.io
cluster installation command example to emphasize its requirement
to get the correct version of k3s on which the rancher should will
be installed, because it can be an annoying mistake that user might
start from setup from scratch.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
