Wayback Machine
68 captures
18 Aug 2020 - 16 Sep 2025
Oct NOV Dec
25
2022 2023 2024
success
fail
About this capture
COLLECTED BY
Organization: Archive Team
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: URLs
TIMESTAMPS
loading
The Wayback Machine - https://web.archive.org/web/20231125030232/https://kubernetes.io/docs/setup/best-practices/
  • Documentation
  • Kubernetes Blog
  • Training
  • Partners
  • Community
  • Case Studies
  • Versions
    Release Information v1.28 v1.27 v1.26 v1.25 v1.24
  • English
    中文 (Chinese) 한국어 (Korean) 日本語 (Japanese) Bahasa Indonesia हिन्दी (Hindi) Українська (Ukrainian)
  1. Kubernetes Documentation
  2. Getting started
  3. Best practices

Best practices


Considerations for large clusters

Running in multiple zones

Validate node setup

Enforcing Pod Security Standards

PKI certificates and requirements

Feedback

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub Repository if you want to report a problem or suggest an improvement.

Last modified June 12, 2019 at 5:27 PM PST: Restructure the left navigation pane of setup (#14826) (55ac801bc4)
Edit this page Create child page Create an issue Print entire section
Documentation Blog Training Partners Community Case Studies
© 2023 The Kubernetes Authors | Documentation Distributed under CC BY 4.0
Copyright © 2023 The Linux Foundation ®. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page
ICP license: 京ICP备17074266号-3