NAIS areas¶
To ensure that all parts of NAIS are well taken care of, we have created what we call "areas". Everything we create, have a home in one of these areas. Each area has one or two anchors. The anchors responsibility is to ensure that the area is well taken care of. They have oversight over the area, and are the go-to person for questions and discussions related to the area. E.g. if a initiative is proposed that affects the area, the anchor should be involved in the discussion.
NAIS is divided into several areas, each with its own anchor. The anchor is responsible for the area and is the go-to person for questions and discussions related to the area. The anchor is also responsible for keeping the area's board up to date.
naisdevice¶
Ankere: Vegar og Torbjørn
Persistence¶
Anchor: Morten
Components: DB, Kafka, Redis, OpenSearch, Bigquery, buckets
Board: https://github.com/orgs/nais/projects/23/views/1
Deploy¶
Anchor: Kim Tore
Components: hookd, naiserator, liberator, deploy-action
Auth¶
Anchor: Trong
Components: Digdirator, Azurerator, Wonderwall, TokenX, IAP / Forward Auth
Board: https://github.com/orgs/nais/projects/27/views/1
Sårbarheter¶
Ankere: Tommy og Youssef
Components: SLSA, DependencyTrack, Picante, vulnerability scanning, Security Champion, supply chain security
Observability¶
Anchor: Hans Kristian og Terje
Components: Prometheus, Grafana, Alertmanager, Loki, Tempo, Fluentd/fluentbit, node_exporter, kube-state-metrics, OpenTelemetry
Cluster¶
Anchor: Sten
Components: Nais-terraform-modules, nettverk(mesh, lb, peering), k8s
NAIS Tooling¶
Anchor: Thomas og Christer
Components: NAIS API, Console, NAIS CLI, Fasit
NAIS meta¶
Anchor: Frode, Johnny
Components: doc, nais.io, handbook¶
Misc: - KrakenD: Tommy og Sindre - Unleash: Hans Kristian - Gemini: Kim Tore - Vault: Trong (https://github.com/orgs/nais/projects/26/views/1)