Files
inbuxa-charts/.kube-linter.yaml
jcoffey-dev a427c7b179
ci / chart (pull_request) Successful in 52s
webmail, console and routes (K-C3)
The webmail and the console, each off by default: a Deployment, a
Service, an optional autoscaler and a PodDisruptionBudget, a read-only
root filesystem, all capabilities dropped.

The webmail runs with sealed-cookie sessions, so any replica serves any
request, signs in through the server's page, and talks to the server
inside the cluster. Its app and OAuth client secrets are a Secret the
chart makes once and keeps across upgrades, or webmail.existingSecret.
Every server pod gets INBUXA_WEBMAIL_URL, the client secret and
INBUXA_ADMIN_URL, so it registers both as OAuth clients and lets the
console's origin call the API.

routes: the server's, the webmail's and the console's addresses, by host
name, as Gateway API HTTPRoutes or one Ingress. kubeconform checks
HTTPRoute against the CRDs catalog's schema.
2026-11-18 14:52:50 -07:00

36 lines
1.5 KiB
YAML

# SPDX-FileCopyrightText: 2026 Coffey Labs LLC
# SPDX-License-Identifier: Apache-2.0
#
# Every built-in check, on everything the chart renders. A check is only
# left out here with a line saying why.
checks:
addAllBuiltIn: true
exclude:
# Style: Kubernetes' own docs order keys by meaning, not alphabetically
- sorted-keys
# An organisation's own conventions, for the operator to add
- required-annotation-email
- required-label-owner
# Cluster DNS defaults are right for the server
- dnsconfig-options
# Placement is the operator's choice (nodeSelector/affinity per group)
- no-node-affinity
# The groups spread with topologySpreadConstraints instead
- no-anti-affinity
# core runs exactly one replica by design, and front and mta default to 2
- minimum-three-replicas
# Likewise for the webmail's and the console's autoscalers: two across
# nodes, with a PDB, is the floor; an operator may raise it
- hpa-minimum-three-replicas
# The mail Service is a LoadBalancer on purpose: it is how mail gets in
- exposed-services
# TODO(K-C4): NetworkPolicies come with the security defaults; take this
# line out then
- non-isolated-pod
# The standard mail ports, on purpose. The pod listens on them with no
# capability, through the sysctl below.
- privileged-ports
# Flags net.ipv4.ip_unprivileged_port_start, which Kubernetes counts as a
# safe, namespaced sysctl since 1.22 and Pod Security "restricted" allows
- unsafe-sysctls