From fdb4de9b1b0c5f168463af7fb93789d73eb200cd Mon Sep 17 00:00:00 2001 From: Ciaran Moran Date: Fri, 31 Mar 2023 12:38:49 +0100 Subject: [PATCH 1/4] docs:wksctl is deprecated, link to Weave GitOps (Enterprise) instead --- docs/cluster.md | 71 -------------------- docs/development.md | 46 ------------- docs/faq.md | 18 ----- docs/get-started.md | 69 ------------------- docs/index.md | 48 ++----------- docs/releasing.md | 26 -------- docs/wks-and-firekube.md | 7 -- docs/wks-and-footloose.md | 137 -------------------------------------- docs/wks-and-vagrant.md | 26 -------- docs/wks-on-gce.md | 91 ------------------------- mkdocs.yml | 9 --- 11 files changed, 4 insertions(+), 544 deletions(-) delete mode 100644 docs/cluster.md delete mode 100644 docs/development.md delete mode 100644 docs/faq.md delete mode 100644 docs/get-started.md delete mode 100644 docs/releasing.md delete mode 100644 docs/wks-and-firekube.md delete mode 100644 docs/wks-and-footloose.md delete mode 100644 docs/wks-and-vagrant.md delete mode 100644 docs/wks-on-gce.md diff --git a/docs/cluster.md b/docs/cluster.md deleted file mode 100644 index e580bce2..00000000 --- a/docs/cluster.md +++ /dev/null @@ -1,71 +0,0 @@ -# Cluster Definition - -Here's an example of the cluster definition. It is spread across two -objects: a `Cluster` which is defined by Kubernetes ClusterAPI and a -`ExistingInfraCluster` defined by Weaveworks. Here, both objects have the -same name `example`, and the field `infrastructureRef` points from one -to the other. - -``` -apiVersion: cluster.x-k8s.io/v1alpha3 -kind: Cluster -metadata: - name: example -spec: - clusterNetwork: - services: - cidrBlocks: [10.96.0.0/12] - pods: - cidrBlocks: [192.168.0.0/16] - serviceDomain: cluster.local - infrastructureRef: - apiVersion: cluster.weave.works/v1alpha3 - kind: ExistingInfraCluster - name: example ---- -apiVersion: cluster.weave.works/v1alpha3 -kind: ExistingInfraCluster -metadata: - name: example -spec: - sshKeyPath: cluster-key - user: root - os: - files: - - source: - configmap: repo - key: kubernetes.repo - destination: /etc/yum.repos.d/kubernetes.repo - - source: - configmap: repo - key: docker-ce.repo - destination: /etc/yum.repos.d/docker-ce.repo - - source: - configmap: docker - key: daemon.json - destination: /etc/docker/daemon.json - cri: - kind: docker - package: docker-ce - version: 19.03.8 - apiServer: - extraArguments: - - name: alsologtostderr - value: "true" - - name: audit-log-maxsize - value: "10000" - kubeletArguments: - - name: alsologtostderr - value: "true" - - name: container-runtime - value: docker -``` - -## Passing extra arguments to the API Server - -`spec.providerSpec.value.apiServer.extraArguments` is where we specify extra arguments for the API servers. Each pair of `name` and `value` is used to form an argument as `name=value`. From the example, we'll have `alsologtostderr=true` and `audit-log-maxsize=10000` as extra arguments for every API server. - -## Passing extra arguments to Kubelet - -`spec.providerSpec.value.kubeletArguments` is the place to specify extra arguments for Kubelet. From the above example, we'll have `alsologtostderr=true` and `container-runtime=docker` as extra arguments. - diff --git a/docs/development.md b/docs/development.md deleted file mode 100644 index 4e85e0d5..00000000 --- a/docs/development.md +++ /dev/null @@ -1,46 +0,0 @@ -# Development - -## Build - -```console -make -``` - -### Upgrading the build image - -- Update `build/Dockerfile` as required. -- Test the build locally: - -```console -rm build/.uptodate -make !$ -``` - -- Push this change, get it reviewed, and merge it to `master`. -- Run: - -```console -git checkout master ; git fetch origin master ; git merge --ff-only master -rm build/.uptodate -make !$ -> [...] -> Successfully built deadbeefcafe -> Successfully tagged docker.io/weaveworks/wksctl-build:latest -> docker tag docker.io/weaveworks/wksctl-build docker.io/weaveworks/wksctl-build:master-XXXXXXX -> touch build/.uptodate -docker push docker.io/weaveworks/wksctl-build:$(tools/image-tag) -``` - -- Update `.circleci/config.yml` to use the newly pushed image. -- Push this change, get it reviewed, and merge it to `master`. - -## Adding docs - -Docs live in the [`docs` directory](https://github.com/weaveworks/wksctl/tree/master/docs) -and we use Markdown for everything. Every new commit will be published at -. - -A few things to be aware of: - -- Use `make serve-docs` to serve the docs locally and point a webbrowser to the URL in the output, e.g. `localhost:8000`, to check out if your changes worked out. -- Upon pushing a PR to this repository, links in the docs will be automatically tested. diff --git a/docs/faq.md b/docs/faq.md deleted file mode 100644 index 1f812138..00000000 --- a/docs/faq.md +++ /dev/null @@ -1,18 +0,0 @@ -# Frequently asked questions - -## Checkpoint and how to disable it - -`wksctl` contacts Weaveworks servers for available versions. When a new version is available, `wksctl` will print out a message along with a URL to download it. - -The information sent in this check is: - -- wksctl version -- Machine Architecture -- Operating System -- Host UUID hash - -To disable this check, run the following before executing `wksctl`: - -```console -export CHECKPOINT_DISABLE=1 -``` diff --git a/docs/get-started.md b/docs/get-started.md deleted file mode 100644 index d00a8ac6..00000000 --- a/docs/get-started.md +++ /dev/null @@ -1,69 +0,0 @@ -# Get started with wksctl - -Using `wksctl` you have two modes of operation. **Standalone** mode and **GitOps** mode. The latter will enable you to keep the state of the cluster itself in Git too. - -## Modes of use - -In **standalone mode**, `wksctl` builds a static cluster based on the contents of `cluster.yaml` and `machines.yaml` files passed on the command line; in **GitOps mode**, changes to `cluster.yaml` and `machines.yaml` files stored in Git will cause updates to the state of the live cluster. - -### Standalone mode - -Run `wksctl apply` and pass in the paths to `cluster.yaml` and `machines.yaml` - -```console -wksctl apply \ - --cluster cluster.yaml \ - --machines machines.yaml -``` - -### GitOps mode - -We will create a cluster by pulling the cluster and machine yaml from git. - -The following are commandline arguments to `wksctl apply` which will result in a cluster being created. - -- **git-url** The git repo url containing the `cluster.yaml` and `machine.yaml` -- **git-branch** The branch within the repo to pull the cluster info from -- **git-deploy-key** The deploy key configured for the GitHub repo -- **git-path** Relative path to files in Git (optional) - -The git command line arguments are passed instead of `--cluster` and `--machines`. - -```console -wksctl apply \ - --git-url git@github.com:$YOUR_GITHUB_ORG/config-repo.git \ - --git-branch dev \ - --git-deploy-key ./deploy-key -``` - -Using the url, branch, and deploy key, `wksctl` will clone the repo and create the cluster. - -These `--git` arguments are then used to set up and configure [flux](https://www.weave.works/oss/flux/) to automate cluster management via Git aka [GitOps](https://www.weave.works/technologies/gitops/) - -We will rely on the user installing [fluxctl](https://docs.fluxcd.io/en/latest/references/fluxctl#installing-fluxctl) to interact with flux directly. `wksctl` does not replicate this functionality. - -### wksctl apply -A complete description of the apply command - -```console -wksctl apply --help -Create or update a Kubernetes cluster - -Usage: - wksctl apply [flags] - -Flags: - --cluster string Location of cluster manifest (default "cluster.yaml") - --config-directory string Directory containing configuration information for the cluster (default ".") - --git-branch string Git branch WKS should use to sync with your cluster (default "master") - --git-deploy-key string Path to the Git deploy key - --git-path string Relative path to files in Git (default ".") - --git-url string Git repo containing your cluster and machine information - -h, --help help for apply - --machines string Location of machines manifest (default "machines.yaml") - --namespace string namespace override for WKS components (default "weavek8sops") - --sealed-secret-cert string Path to a certificate used to encrypt sealed secrets - --sealed-secret-key string Path to a key used to decrypt sealed secrets - --ssh-key string Path to a key authorized to log in to machines by SSH (default "./cluster-key") - --use-manifest-namespace use namespaces from supplied manifests (overriding any --namespace argument) -``` diff --git a/docs/index.md b/docs/index.md index 80efba26..4616eb1f 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,46 +1,6 @@ -# wksctl Documentation +# ⚠️ [Weave Kubernetes System has been retired](https://eol.weave.works/). ⚠️ -`wksctl` allows simple creation of a Kubernetes cluster given a **set of IP addresses** and an **SSH key**. It can be run in a standalone environment but is best used via a [GitOps approach](https://www.weave.works/technologies/gitops/) in which cluster and machine descriptions are stored in Git and the state of the cluster tracks changes to the descriptions. +Please see the previous versions if you still need documentation for the legacy +`wksctl`. -Its features include: - -- simple creation of Kubernetes clusters -- manage cluster and machine descriptions using Git -- manage addons like Weave Net or Flux -- Sealed Secret integration - -## Install wksctl binary - -1. Download the OS specific `wksctl` release package from the [release page](https://github.com/weaveworks/wksctl/releases) -1. Unpack and add the `wksctl` binary to your path - - For example: - - ```console - cd - tar xfz wksctl-0.7.0-linux-x86_64.tar.gz - chmod +x wksctl - sudo mv wksctl /usr/local/bin/ - ``` - -## Table of contents - -- [Get started](get-started.md) -- [WKS and Firekube](wks-and-firekube.md) -- [WKS and Footloose](wks-and-footloose.md) -- [WKS and Vagrant](wks-and-vagrant.md) -- [WKS on GCE](wks-on-gce.md) -- [FAQ](faq.md) -- [Development](development.md) -- [Releasing](releasing.md) - - -## Getting Help - -If you have any questions about, feedback for or problems with `wksctl`: - -- Invite yourself to the Weave Users Slack. -- Ask a question on the [#wksctl](https://weave-community.slack.com/messages/wksctl/) slack channel. -- [File an issue](https://github.com/weaveworks/wksctl/issues/new). - -Your feedback is always welcome! +Please see [Weave GitOps](https://www.weave.works/product/gitops/) and [ Weave GitOps Enterprise ](https://www.weave.works/product/gitops-enterprise/) for alternatives. diff --git a/docs/releasing.md b/docs/releasing.md deleted file mode 100644 index c4349459..00000000 --- a/docs/releasing.md +++ /dev/null @@ -1,26 +0,0 @@ -# Releasing - -We use [GoReleaser](https://goreleaser.com/) to generate release artifacts, which is initiated when a tag pushed to the repository. - -## Tagging -The tag we use in the repository follows [semver](https://github.com/semver/semver/blob/master/semver.md) with the leading **v** - -``` shell -git checkout -git fetch -git reset --hard origin/ -git tag -s -a vMajor.Minor.patch[-(alpha,beta,rc).#] -git push origin -``` - -## New minor release -When we are ready to release a new minor version of `wksctl`, we will need a branch to enable changes to the minor release and enable work to continue on the next release. -1. Create a branch named release-Major.Minor, e.g., `release-0.8`. Notice the branch doesn't have the leading v or include the patch number. -1. Work with Weaveworks corp to make this branch protected and require PR reviews. - -When creating changes for the release, we prefer they are merged into the master branch and then cherry-picked to the release branch. If the master branch has changed to where this isn't possible or practical, the changeset can be merged into the release branch. If you encounter this situation, please open a ticket to ensure the changes are re-applied to the master branch, and we don't have a regression in future releases. - -## Patch release -Follow the tagging process identified. The intention is for the minor release to have patch builds, and we won't use release branches for patch releases. i.e., the branch is moving forward, and we will create versioned patch releases as necessary. - - diff --git a/docs/wks-and-firekube.md b/docs/wks-and-firekube.md deleted file mode 100644 index a827ce59..00000000 --- a/docs/wks-and-firekube.md +++ /dev/null @@ -1,7 +0,0 @@ -# WKS and Firekube - -## Firekube - -[Firekube](https://github.com/weaveworks/wks-quickstart-firekube) is a project that will quickly get you up and running with `wksctl`, a git repo for [GitOps](https://www.weave.works/technologies/gitops/), and [footloose](https://github.com/weaveworks/footloose) with an [Ignite](https://ignite.readthedocs.io/en/stable/) backend. It automates several of the steps you see in the `wksctl` documentation. - -For more information see the [Firekube quickstart](https://github.com/weaveworks/wks-quickstart-firekube) diff --git a/docs/wks-and-footloose.md b/docs/wks-and-footloose.md deleted file mode 100644 index b72f45a0..00000000 --- a/docs/wks-and-footloose.md +++ /dev/null @@ -1,137 +0,0 @@ -# WKS and Footloose - -## Pre-requisites - -1. Pick a distro of your choice: - - 1. `centos7` (At the moment of writing, `centos7` is more mature) - 2. `ubuntu1804` - - ```console - export DISTRO=centos7 - ``` - -1. Pick a backend of your choice: - - 1. `docker` (not real VMs, but can be used on Mac) - 2. `ignite` (requires [Ignite](https://ignite.readthedocs.org) to be installed, and KVM functioning) - - ```console - export BACKEND=docker - ``` - -1. Install [footloose](https://github.com/weaveworks/footloose): - - - Using Linux: - - ```console - VERSION=$(curl -sSf https://api.github.com/repos/weaveworks/footloose/releases | jq -r '.[0].name') - curl -Lo footloose "https://github.com/weaveworks/footloose/releases/download/$VERSION/footloose-$VERSION-linux-x86_64" - chmod +x footloose - sudo mv footloose /usr/local/bin/ - ``` - - - Using macOS: - - On macOS we provide a direct download and a homebrew tap: - - ```console - VERSION=$(curl -sSf https://api.github.com/repos/weaveworks/footloose/releases | jq -r '.[0].name') - curl --silent --location "https://github.com/weaveworks/footloose/releases/download/$VERSION/footloose-$VERSION-darwin-x86_64.tar.gz" | tar xz - sudo mv footloose /usr/local/bin - ``` - - or - - ```console - brew tap weaveworks/tap - brew install weaveworks/tap/footloose - ``` - -## Getting started - -### Starting the machines - -Here we will start two machines using `footloose`: - -These commands assume you are in the `examples/footloose` directory. - -```console -$ footloose create -c ${DISTRO}/${BACKEND}/singlemaster.yaml -INFO[0000] Image: quay.io/footloose/centos7 present locally -INFO[0000] Creating machine: centos-singlemaster-node0 ... -INFO[0001] Creating machine: centos-singlemaster-node1 ... -``` - -You should now see the Container Machines running with `docker ps` or `ignite ps` (depending on your backend): - -```console -$ docker ps -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -ab4f4b75f63d quay.io/wksctl/vm-centos7 "/sbin/init" 5 seconds ago Up 4 seconds 0.0.0.0:2223->22/tcp, 0.0.0.0:6444->6443/tcp cluster-node1 -0ce280129e79 quay.io/wksctl/vm-centos7 "/sbin/init" 6 seconds ago Up 5 seconds 0.0.0.0:6443->6443/tcp, 0.0.0.0:2222->22/tcp cluster-node0 -``` - -or: - -```console -$ ignite ps -VM ID IMAGE KERNEL SIZE CPUS MEMORY CREATED STATUS IPS PORTS NAME -3fbe4611682b3e16 weaveworks/ignite-centos:latest weaveworks/ignite-kernel:4.19.47 4.0 GB 2 1024.0 MB 10m ago Up 10m 172.17.0.3 0.0.0.0:30444->30443/tcp, 0.0.0.0:30081->30080/tcp, 0.0.0.0:2223->22/tcp, 0.0.0.0:6444->6443/tcp centos-singlemaster-node1 -b4fdde36eb122804 weaveworks/ignite-centos:latest weaveworks/ignite-kernel:4.19.47 4.0 GB 2 1024.0 MB 10m ago Up 10m 172.17.0.2 0.0.0.0:2222->22/tcp, 0.0.0.0:6443->6443/tcp, 0.0.0.0:30443->30443/tcp, 0.0.0.0:30080->30080/tcp centos-singlemaster-node0 -``` - -In case you would like to ssh into a machine e.g. `node0`, run: - -```console -footloose ssh -c ${DISTRO}/${BACKEND}/singlemaster.yaml root@node0 -``` - -as the default user name is `root` for both backends. - -### Starting the cluster - - -1. Run `wksctl apply`: - - ```console - wksctl apply \ - --machines=machines.yaml \ - --cluster=cluster.yaml \ - --verbose - ``` - -1. Run `wksctl kubeconfig` to be able to connect to the cluster: - - ```console - $ wksctl kubeconfig --cluster=cluster.yaml - The kubeconfig file at "/home/dinos/.kube/config" has been updated - $ kubectl get nodes - NAME STATUS ROLES AGE VERSION - b4fdde36eb122804 Ready master 77s v1.14.1 - $ kubectl get pods --all-namespaces - NAMESPACE NAME READY STATUS RESTARTS AGE - kube-system coredns-86c58d9df4-26gv9 1/1 Running 0 55s - kube-system coredns-86c58d9df4-mb4h9 1/1 Running 0 55s - kube-system etcd-13e2dc14bf30 1/1 Running 0 6s - kube-system kube-apiserver-13e2dc14bf30 1/1 Running 0 8s - kube-system kube-proxy-l2fv7 1/1 Running 0 55s - kube-system kube-scheduler-13e2dc14bf30 1/1 Running 0 9s - kube-system weave-net-n7lqb 2/2 Running 0 55s - system wks-controller-654d7cfb7c-47f9g 1/1 Running 0 54s - ``` - -## Multi-masters - -Follow the above steps, but pass the multi-master manifests: - -```console -footloose create -c ${DISTRO}/${BACKEND}/multimaster.yaml -``` - -```console -$ wksctl apply \ - --machines=machines-multimaster.yaml \ - --cluster=cluster.yaml \ - [...] -``` diff --git a/docs/wks-and-vagrant.md b/docs/wks-and-vagrant.md deleted file mode 100644 index 94b9f3eb..00000000 --- a/docs/wks-and-vagrant.md +++ /dev/null @@ -1,26 +0,0 @@ -# WKS and Vagrant - -```console -$ cd examples/vagrant -$ vagrant up -$ wksctl apply --ssh-key=$HOME/.vagrant.d/insecure_private_key -INFO[0000] installing CRI implementation -INFO[0054] installing Kubernetes -INFO[0079] initializing Kubernetes cluster with kubeadm -INFO[0164] installing CNI implementation -INFO[0165] applying cluster API's custom resource definitions -INFO[0166] applying cluster's manifest -INFO[0166] applying machines' manifest -INFO[0166] applying WKS controller's manifests -INFO[0167] adding SSH key to WKS secret and applying its manifest -$ vagrant ssh kube-01 -$ sudo -i -# It takes a few minutes for the controller to create the second node. -# kubectl get nodes -NAME STATUS ROLES AGE VERSION -kube-01 Ready master 8m8s v1.13.3 -kube-02 Ready 4m53s v1.13.3 - -At any time, one can look at what the controller is doing: -# kubectl logs --tail 100 -f -n weavek8sops -l name=wks-controller -``` diff --git a/docs/wks-on-gce.md b/docs/wks-on-gce.md deleted file mode 100644 index 26ef1820..00000000 --- a/docs/wks-on-gce.md +++ /dev/null @@ -1,91 +0,0 @@ -# WKS on GCE - -## Prerequisites - -1. Install: - - [`gcloud`](https://cloud.google.com/sdk/docs/#install_the_latest_cloud_tools_version_cloudsdk_current_version) - - [`jk`](https://github.com/jkcfg/jk) - - [`direnv`](https://direnv.net/) - -1. [Configure `gcloud`](https://cloud.google.com/sdk/gcloud/#configurations). - -1. If you have never used direnv, you need to [set it up](https://github.com/direnv/direnv#setup). - It hooks itself into your shell to set/unset environment variables when you - enter or leave a directory. - - ```console - eval "$(direnv hook bash)" - ``` - -1. Create an `.envrc` file with, for example, the following content (or change to appropriate values where relevant): - - ```console - export project="wks-tests" - export zone="europe-west1-b" - export user="$(whoami)" - export network="${user}-demo" - export image_project="centos-cloud" - export image_family="centos-7" - export network_interface="eth0" - ``` - - (see also: [GCP images](https://cloud.google.com/compute/docs/images#images_without_shielded_vm_name_support)) - and run: - - ```console - direnv allow - ``` - -## Create the WKS cluster - -1. Create the GCE network and instances: - - ```console - ./create-network.sh && ./create-instances.sh - ``` - - > **Note:** In case cluster capacity for number of instances is reached, try using another zone in `.envrc`. - -1. Generate `machines.yaml`: - - ```console - ./generate-machines-manifest.sh - ``` - -1. Create & configure the WKS cluster: - - ```console - wksctl apply - ``` - -1. Generate the kubeconfig file - - ```console - wksctl kubeconfig - ``` - - This will print a line to the console similar to `$ export KUBECONFIG=/[path to kubeconfig file]`. Copy that line and paste it into any terminal you are using `kubectl` in. - -1. Ensure that everything's working: - - ```console - kubectl get namespaces - ``` - - should return something like - - ```console - NAME STATUS AGE - default Active 1m59s - kube-public Active 1m59s - kube-system Active 1m59s - system Active 1m54s - ``` - -## Delete the WKS cluster - -To delete your WKS cluster, run: - -```console -./delete-instances.sh && ./delete-network.sh -``` diff --git a/mkdocs.yml b/mkdocs.yml index d3b801e4..5009adab 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -31,12 +31,3 @@ markdown_extensions: - pymdownx.superfences - toc: permalink: true - -nav: - - Get started with wksctl: get-started.md - - WKS and Firekube: wks-and-firekube.md - - WKS and Footloose: wks-and-footloose.md - - WKS and Vagrant: wks-and-vagrant.md - - WKS on GCE: wks-on-gce.md - - Frequently asked questions: faq.md - - Development: development.md From 0627b083e2b19fb66392a95a8ed37fabae5da3e7 Mon Sep 17 00:00:00 2001 From: Ciaran Moran Date: Fri, 31 Mar 2023 12:49:21 +0100 Subject: [PATCH 2/4] beautify --- .python-version | 1 + docs/index.md | 8 +++++--- 2 files changed, 6 insertions(+), 3 deletions(-) create mode 100644 .python-version diff --git a/.python-version b/.python-version new file mode 100644 index 00000000..d5cd4cce --- /dev/null +++ b/.python-version @@ -0,0 +1 @@ +3.10.10 diff --git a/docs/index.md b/docs/index.md index 4616eb1f..b5f6b8e6 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,6 +1,8 @@ -# ⚠️ [Weave Kubernetes System has been retired](https://eol.weave.works/). ⚠️ +# wksctl Documentation -Please see the previous versions if you still need documentation for the legacy -`wksctl`. +!!! important "Deprecation notice" + [Weave Kubernetes System has been retired](https://eol.weave.works/). + Please see the previous versions if you still need documentation for the + legacy `wksctl`. Please see [Weave GitOps](https://www.weave.works/product/gitops/) and [ Weave GitOps Enterprise ](https://www.weave.works/product/gitops-enterprise/) for alternatives. From fbfbafa67d91267ccae5c8742f0c93af447d6ac0 Mon Sep 17 00:00:00 2001 From: Ciaran Moran Date: Fri, 31 Mar 2023 12:58:15 +0100 Subject: [PATCH 3/4] redirects --- mkdocs.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/mkdocs.yml b/mkdocs.yml index 5009adab..ffedf78d 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -31,3 +31,17 @@ markdown_extensions: - pymdownx.superfences - toc: permalink: true + +plugins: + - redirects: + redirect_maps: + 'cluster.md': 'index.md' + 'development.md': 'index.md' + 'faq.md': 'index.md' + 'get-started.md': 'index.md' + 'releasing.md': 'index.md' + 'requirements.md': 'index.md' + 'wks-and-firekube.md': 'index.md' + 'wks-and-footloose.md': 'index.md' + 'wks-and-vagrant.md': 'index.md' + 'wks-on-gce.md': 'index.md' From fd2bf06370d608a8ebc78c741fdb9af051ba96af Mon Sep 17 00:00:00 2001 From: Ciaran Moran Date: Fri, 31 Mar 2023 12:58:25 +0100 Subject: [PATCH 4/4] bump deps for redirects --- docs/requirements.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/requirements.txt b/docs/requirements.txt index fc651f8e..6ea3908d 100644 --- a/docs/requirements.txt +++ b/docs/requirements.txt @@ -1,3 +1,4 @@ -mkdocs == 1.1 -mkdocs-material == 5.1.5 -pymdown-extensions >= 7.1 +mkdocs == 1.4.2 +mkdocs-material == 9.1.5 +pymdown-extensions == 9.10 +mkdocs-redirects == 1.2.0 \ No newline at end of file