Lab examples

Generated by the documentation agent from the lab's Git repositories and regenerated by hand with aks-terraform's Lab examples workflow - never edit this page by hand. An example of the lab, not the design: the design does not link here and neither PDF holds it.

Internal - Sweden

Generated by the documentation agent of onek8s/aks-ai-agents (aks-agent docs lab) from Git alone: what Git deploys into the isolation zone int-se of the spoke dev-int. Do not edit by hand - aks-terraform’s Lab examples workflow regenerates it.

Back to the lab examples.

Placement

The zone’s nodes are classic node pools of aks-terraform (zone_node_pools), each scaled by the cluster autoscaler from zero, labelled and tainted platform/zone; an application states its architecture and capacity with pod labels only.

Traffic of the zone

What the hub firewall opens for the zone: every destination below is open to every application of the zone.

flowchart LR
    subgraph Z["Isolation zone int-se"]
        direction TB
        a_int_se_example["int-se-example<br/>team example"]
    end
    fw["Hub firewall<br/>source: IP group of zone int-se"]
    subgraph OUT["What the firewall opens for the zone"]
        direction TB
        d_api_ipify_org["api.ipify.org:443<br/>asked by int-se-example"]
        d_api_open_meteo_com["api.open-meteo.com:443<br/>asked by int-se-example"]
        z_login_microsoftonline_com["login.microsoftonline.com:443<br/>zone allow-list"]
        p___grafana_net["*.grafana.net:443<br/>platform rule, every cell"]
        p_stats_grafana_org["stats.grafana.org:443<br/>platform rule, every cell"]
    end
    a_int_se_example --> fw
    fw -->|"allowed"| d_api_ipify_org
    fw -->|"allowed"| d_api_open_meteo_com
    fw -->|"zone allow-list"| z_login_microsoftonline_com
    fw -->|"platform rule"| p___grafana_net
    fw -->|"platform rule"| p_stats_grafana_org
    none["Named by applications, no rule yet:<br/>hello.int-fi.dev.onek8s.lol"]
    fw -.-x|"denied"| none
    classDef ns fill:#e3f2fd,stroke:#1565c0,color:#000
    classDef platform fill:#eceff1,stroke:#455a64,color:#000
    classDef fw fill:#ede7f6,stroke:#5e35b1,color:#000
    classDef allowed fill:#e8f5e9,stroke:#2e7d32,color:#000
    classDef unexplained fill:#fff8e1,stroke:#ef6c00,color:#000
    classDef missing fill:#ffebee,stroke:#c62828,color:#000,stroke-dasharray: 5 5
    classDef proposed fill:#f3e5f5,stroke:#7b1fa2,color:#000,stroke-dasharray: 5 5
    classDef zone fill:#e0f2f1,stroke:#00695c,color:#000
    class fw fw
    class a_int_se_example ns
    class d_api_ipify_org,d_api_open_meteo_com allowed
    class z_login_microsoftonline_com zone
    class p___grafana_net,p_stats_grafana_org platform
    class none missing

aks-hello in int-se-example

From onek8s/aks-hello’s README: A .NET hello world website - the example application of OneK8s, one Kubernetes platform for every cloud. It is deployed by Flux to the example team namespace of the clusters built by aks-terraform and published through the platform’s Gateway (Traefik Proxy, Kubernetes Gateway API). The page shows which cluster answered: https://hello.onek8s.lol is served by every stateless cluster at once, and DNS hands out one or the other.

Services and routes

Environment

Endpoints of aks-hello

Egress

flowchart LR
    client["Corporate network and VPN clients"]
    subgraph CELL["Cell aks-dev-int-stateless-az3 - pod subnet + hub firewall: the firewall sees the pod's own address"]
        direction LR
        gw["Gateway int-se-gateway/int-se<br/>hello-aks-dev-int-stateless-az3.int-se.dev.onek8s.lol<br/>hello.int-se.dev.onek8s.lol"]
        subgraph NS["namespace int-se-example - team example"]
            direction TB
            svc_aks_hello["Service aks-hello"]
            wl_aks_hello["Deployment aks-hello x2<br/>acronek8sdev.azurecr.io/aks-hello:0.8.0@sha256:201cac9a95b8286e7861c7442ce11f09c495cee2802c8ae24abce07f6787cc1e"]
        end
        dns["CoreDNS"]
        eso["ESO int-se - Key Vault share int-se-example--*"]
    end
    fw["Hub firewall<br/>rule collection group dev-int-applications"]
    subgraph OUT["Outside the landing zone"]
        direction TB
        d_api_ipify_org["api.ipify.org:443"]
        d_api_open_meteo_com["api.open-meteo.com:443"]
        d_hello_int_fi_dev_onek8s_lol["hello.int-fi.dev.onek8s.lol:443"]
    end
    client --> gw
    gw --> svc_aks_hello
    svc_aks_hello --> wl_aks_hello
    wl_aks_hello --> dns
    eso -.->|"Secrets"| wl_aks_hello
    wl_aks_hello -->|"every flow leaving the cluster"| fw
    fw -->|"allowed"| d_api_ipify_org
    fw -->|"allowed"| d_api_open_meteo_com
    fw -.->|"proposed"| d_hello_int_fi_dev_onek8s_lol
    classDef ns fill:#e3f2fd,stroke:#1565c0,color:#000
    classDef platform fill:#eceff1,stroke:#455a64,color:#000
    classDef fw fill:#ede7f6,stroke:#5e35b1,color:#000
    classDef allowed fill:#e8f5e9,stroke:#2e7d32,color:#000
    classDef unexplained fill:#fff8e1,stroke:#ef6c00,color:#000
    classDef missing fill:#ffebee,stroke:#c62828,color:#000,stroke-dasharray: 5 5
    classDef proposed fill:#f3e5f5,stroke:#7b1fa2,color:#000,stroke-dasharray: 5 5
    classDef zone fill:#e0f2f1,stroke:#00695c,color:#000
    class gw,dns,eso platform
    class fw fw
    class svc_aks_hello,wl_aks_hello ns
    class d_api_ipify_org,d_api_open_meteo_com allowed
    class d_hello_int_fi_dev_onek8s_lol proposed

Legend

The status of a destination, from the traffic flow documentation:

• allowed - the application’s rule, named in its configuration
• unexplained - the application’s rule, but its configuration does not name it
• missing - the configuration names it, the firewall denies it
• proposed - in an open pull request, not allowed yet
• zone - open to every application of the zone
• platform - open from every cell of the exposure