Documentation access

[lchunleo]

Wish to know how to access the documentation for weavenet. thanks

[apiwat-chantawibul]

Seems the old documentation site went down with weaveworks the company.

There are some documentation in the repo itself, but it is not the same.

I am using snapshot on webarchive in the meanwhile.

Hopefully, someone can point out a better solution.

[rajch]

The weave net documentation part of the old site can be found in raw form in the site folder of the repo.

[kucerarichard]

It's too bad weaveworks went chasing after flux now we will lose the only layer 2 CNI

[rajch]

We are maintaining a fork over at https://github.com/rajch/weave. We've created a new build process, upgraded to Go 1.20, eliminated some of the vulnerabilities, and upgraded CNI compliance. Come on over, and help keep our beloved layer 2 CNI alive.

[rajch]

The Weave Net documentation is now available at: https://rajch.github.io/weave

[medicol69]

just a general question, is this project still maintained? Can we use it in newer kubernetes versions? Thanks

[rajch]

just a general question, is this project still maintained? Can we use it in newer kubernetes versions? Thanks

A community-maintained fork exists at https://github.com/rajch/weave. We have released a few new versions, re-hosted the documentation, and continue to perform maintenance. The new releases can be used with newer kubernetes version.

[kingdonb]

Weaveworks is closed and out of business. rajch has taken up the mantle, and we gave his fork the nod, you can find it now in the Kubernetes docs about CNI.

There are a couple of places where translations may need the updated link, and I think another section about add-ons where weave net is mentioned and the old reference pointing to Weaveworks website is still there.

If anyone wants to get your first contributions in Kubernetes/website you can fix them, @ me on the PR to get confirmation for the merging reviewer, in case they are skeptical of a personal fork. Raj has also posted a new version of the docs which is part of the fork.

I'm using this and I will continue to maintain a (probably virtual) kubeadm cluster in the future to be able to test new releases on. (I worked at Weaveworks until it closed down in January.)