Skip to content

Environments

This is a overview over the different environments and their available domains. Environments are sometimes also called clusters.

We also enumerate the external IPs used by the environments, so that you can provide them to services that require IP allow-listing.

Google Cloud Platform (GCP)

dev-gcp

Ingress domains

domain accessible from notes
ekstern.dev.nav.no internet URLs containing /metrics, /actuator or /internal are blocked
intern.dev.nav.no NAV internal networks (including naisdevice)
ansatt.dev.nav.no internet, only for authenticated humans on compliant devices URLs containing /metrics, /actuator or /internal are blocked

See explanation for exposing application for more information.

External IPs

  • 35.228.4.248
  • 34.88.219.93
  • 35.228.165.176

Kubectl access

Kubectl access to the cluster is available through naisdevice. You can access all namespaces in the cluster, but you can only modify resources in your team's namespace.

prod-gcp

Ingress domains

domain accessible from notes
nav.no internet URLs containing /metrics, /actuator or /internal are blocked
intern.nav.no NAV internal networks (including naisdevice)
ansatt.nav.no internet, only for authenticated humans on compliant devices URLs containing /metrics, /actuator or /internal are blocked

See explanation for exposing application for more information.

External IPs

  • 35.228.235.189
  • 35.228.12.134
  • 35.228.189.194

Kubectl access

Kubectl access to the cluster is available through naisdevice. You can only read or modify resources in your team's namespace.

On-prem

Warning

This is a legacy environment, and is not recommended for new workloads.

dev-fss

Ingress domains

domain accessible from description
intern.dev.nav.no naisdevice development ingress for internal applications. Also available in dev-gcp, use this to ease migration
dev-fss-pub.nais.io GCP See How do I reach an application found on-premises from my application in GCP?

Kubectl access

Kubectl access to the cluster is available through naisdevice. You can access all namespaces in the cluster, but you can only modify resources in your team's namespace.

prod-fss

Ingress domains

domain accessible from description
intern.nav.no naisdevice ingress for internal applications (supersedes nais.adeo.no). Also available in prod-gcp, use this to ease migration. Requires JITA to onprem-k8s-prod
prod-fss-pub.nais.io GCP See How do I reach an application found on-premises from my application in GCP?

Kubectl access

Kubectl access to the cluster is available through naisdevice with just in time access (jita). You can only read or modify resources in your team's namespace.