Add next meeting notes

Author: jchristgit

docs/docs/meeting-notes/posts/NEXT.md

@@ -0,0 +1,63 @@
+---
+draft: true
+date: ADDME
+authors:
+   - jc
+description: Meeting minutes from NEXT
+---
+
+# NEXT
+
+## Agenda
+
+- **Kubernetes Gateway API migration**
+
+  In its continued war on software, Kubernetes has deprecated working features.
+  We need to migrate to the new gateway API. Joe has already done some work with
+  Envoy and will inform us.
+
+  **Actions**: Create a ticket.
+
+- **Owl Corp Guix Area 51 on Turing**
+
+  `turing.box.pydis.wtf`, which used to be Chris' property, has been stolen in a
+  fantastic scheme that we shall label "Theft by DNS A record". We have now
+  deployed [Guix](https://guix.gnu.org/) on it, to play around with fully
+  declarative host deployment.
+
+  We now want to figure out what to do with the host to expand our testing. The
+  following suggestions have been made so far:
+
+  <!-- NOTE to you, *OWL CORP AGENTS*: please expand this list as you see fit -->
+
+  - Numbers station
+  - agents.pydis.wtf
+  - database backups
+  - Lovelace monitoring
+
+  **Actions**:
+
+  - Create a milestone for Area 51 initial setup
+  - Create issues for the bullet points above
+
+- **LKE IP address whitelisting**
+
+  Right now the `/etc/nftables` IP whitelist on lovelace is only refreshed on
+  deployment. This is suboptimal, since worst case our resources may get
+  scheduled on a new node that is not whitelisted in the firewall.
+
+  The ideal solution would involve as little manual work as possible. `nftables`
+  has an `include` directive: we could write a timer / cronjob to update a
+  `nftables` file containing only the LKE ip addresses, which is then included
+  in our Ansible-managed main `nftables.conf`. We would have to take care of
+  setting up an initial IP whitelist in said file to prevent errors when
+  provisioning a new server (where the timer has not run yet).
+
+  **Actions**: Create a ticket.
+
+- **GitHub RBAC synchronization**
+
+  Right now there is a lag between Discord roles and GitHub roles. As with LDAP,
+  we should likely include this functionality in King Arthur The Terrible.
+
+  **Actions**: Create a ticket for King Arthur The Terrible.