chore: archive kubernetes-sigs/blixt

Signed-off-by: Shane Utt <[email protected]>

Author: shaneutt

communication/slack-config/channels.yaml

@@ -33,6 +33,7 @@ channels:
   - name: bazel
   - name: bindings-discuss
   - name: blixt
+    archived: true
   - name: bootkube
     archived: true
   - name: bpfman

sig-network/README.md

@@ -100,7 +100,6 @@ The following [subprojects][subproject-definition] are owned by sig-network:
   - Shane Utt (**[@shaneutt](https://github.com/shaneutt)**), Red Hat
   - Nick Young (**[@youngnick](https://github.com/youngnick)**), Isovalent
 - **Owners:**
-  - [kubernetes-sigs/blixt](https://github.com/kubernetes-sigs/blixt/blob/main/OWNERS)
   - [kubernetes-sigs/gateway-api](https://github.com/kubernetes-sigs/gateway-api/blob/master/OWNERS)
   - [kubernetes-sigs/gwctl](https://github.com/kubernetes-sigs/gwctl/blob/main/OWNERS)
   - [kubernetes-sigs/ingate/heads/main](https://github.com/kubernetes-sigs/ingate/blob/refs/heads/main/OWNERS)
@@ -229,4 +228,19 @@ remains important prior art for any future attempts to revise kube-proxy.
 [kpng]: https://github.com/kubernetes-sigs/kpng
 [kube-proxy]: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/
 
+### Blixt
+
+[Blixt] was a Kubernetes L4 load-balancer that started in the early 2020's at a
+time when eBPF technology was a huge buzz for Kubernetes, and members of the
+Kubernetes SIG Network community wanted to experiment with and explore the
+technology on K8s. The project operated primarily as an experimental sandbox.
+
+We had a lot of fun working on this while it was active. It was great to create
+the first official Kubernetes project in [Rust], and experimenting with eBPF in
+its nascence was exciting. All things must come to an end however. Thank you to
+all contributors!
+
+[Blixt]:https://github.com/kubernetes-sigs/blixt
+[Rust]:https://github.com/rust-lang/
+
 <!-- END CUSTOM CONTENT -->

sig-network/charter.md

@@ -31,7 +31,7 @@ The following topics fall under ownership of this SIG:
   - Reference implementations (i.e. [kube-proxy]).
 - Ingress
   - APIs for defining ingress loadbalancing (i.e. [Ingress], [Gateway API], [Gateway API Inference Extension])
-  - API Implementations (i.e. [ingress-nginx], [InGate], [Blixt])
+  - API Implementations (i.e. [ingress-nginx], [InGate])
 - Network Policy
   - APIs for defining network policies (i.e. [NetworkPolicy], [AdminNetworkPolicy], [BaselineAdminNetworkPolicy])
   - Reference implementations (i.e. [kube-network-policies])
@@ -86,7 +86,6 @@ SIG Technical Leads
 [Gateway API Inference Extension]: https://github.com/kubernetes-sigs/gateway-api-inference-extension
 [ingress-nginx]: https://github.com/kubernetes/ingress-nginx/
 [InGate]: https://github.com/kubernetes-sigs/ingate
-[Blixt]: https://github.com/kubernetes-sigs/blixt
 
 [NetworkPolicy]: https://kubernetes.io/docs/concepts/services-networking/network-policies/
 [AdminNetworkPolicy]: https://network-policy-api.sigs.k8s.io/api-overview/#the-adminnetworkpolicy-resource

sigs.yaml

@@ -2400,7 +2400,6 @@ sigs:
     contact:
       slack: sig-network-gateway-api
     owners:
-    - https://raw.githubusercontent.com/kubernetes-sigs/blixt/main/OWNERS
     - https://raw.githubusercontent.com/kubernetes-sigs/gateway-api/master/OWNERS
     - https://raw.githubusercontent.com/kubernetes-sigs/gwctl/main/OWNERS
     - https://raw.githubusercontent.com/kubernetes-sigs/ingate/refs/heads/main/OWNERS