Remove the "Prior v1.0.0" docs

- Based on discussion with the K3s team we decided to remove these completely This is because everything prior to v1.0.0 is not GA and not officially supported. It's strongly recommended to use the v1.0.0 or newer version of K3s.
2026-09-25 12:38:05 +00:00 · 2019-11-14 15:58:12 -07:00
parent 1015f129e2
commit a27c913ce6
4 changed files with 1 additions and 66 deletions
@@ -162,7 +162,3 @@ k3s agents can be configured with options `--node-label` and `--node-taint` whic
     --node-taint key1=value1:NoExecute
 ```

-Metrics Server
--------------
-
->**Note:** v1.0.0 and newer includes the metrics-server by default. For older versions of k3s, please visit [Configuration Info Prior to v1.0.0]({{< baseurl >}}/k3s/latest/en/configuration/older-configuration/).
@@ -1,21 +0,0 @@
---
-title: "Configuration Info Prior to v1.0.0"
-weight: 10
---
-
->**Note:** Running k3s v1.0.0 or newer is recommended.
-
-This page outlines any configuration info that is relevant to versions older than v1.0.0 but was removed or no longer needed in v1.0.0 and newer.
-
-Metrics Server	
--------------
-
->**Note:** k3s v1.0.0 includes the metrics-server by default.
-
-To add functionality for commands such as `k3s kubectl top nodes` metrics-server must be installed, 
-to install see the instructions located at https://github.com/kubernetes-incubator/metrics-server/.	
-
-**NOTE** : By default the image used in `metrics-server-deployment.yaml` is valid only for **amd64** devices,	
-this should be edited as appropriate for your architecture. As of this writing metrics-server provides	
-the following images relevant to k3s: `amd64:v0.3.3`, `arm64:v0.3.2`, and `arm:v0.3.2`. Further information	
-on the images provided through gcr.io can be found at https://console.cloud.google.com/gcr/images/google-containers/GLOBAL.
@@ -3,7 +3,7 @@ title: "High Availability (HA) Install"
 weight: 30
 ---

->**Note:** Official support for High-Availability (HA) was introduced in our v1.0.0 release. HA may work on older releases but has limited support. Older versions of k3s bring up server nodes slightly differently. Reference [this]({{< baseurl >}}/k3s/latest/en/installation/older-installations/) page for more information.
+>**Note:** Official support for High-Availability (HA) was introduced in our v1.0.0 release.

 >k3s servers do not utilize a quorum for leader election and so only a 2-node cluster is needed for HA at a minimum. You could optionally add one or more server nodes for additional redundancy.

@@ -1,40 +0,0 @@
---
-title: "Installations Prior to v1.0.0"
-weight: 50
---
-
-Running k3s v1.0.0 or newer is recommended as it has official support for PostgreSQL, MySQL, and etcd. v0.10.0 introduced support for PostgreSQL 10.7 and 11.5 only. Older versions did not have any official support for any external databases. 
-
-In v1.0.0 the method for adding server nodes is easier. If you are running a version of k3s older than v1.0.0, use these instructions for adding additional servers. Otherwise, the process is unchanged for joining workers.
-
-First, create your initial server, for example:
-
-```
-curl -fL https://get.k3s.io | sh -s - server --storage-endpoint='value_here' --cluster-secret='mysecret' --bootstrap-save
-```
-
-Then, add additional servers:
-
-```
-curl -fL https://get.k3s.io | sh -s - server --storage-endpoint='value_here'
-```
-
-Substitute the value for `--storage-endpoint` with different strings for PostgreSQL, MySQL, or etcd accordingly. Below are examples of the `--storage-endpoint` flag for each type of database:
-
-### PostgreSQL
-
-```
--storage-endpoint='postgres://username:password@hostname:5432/dbname'
-```
-
-### MySQL
-
-```
--storage-endpoint='mysql://username:password@tcp(hostname:3306)/dbname''
-```
-
-### etcd
-
-```
--storage-endpoint='https://etcd_hostname:2379'
-```