reference
51 pagesAccess policy reference
The following hosts are by default accessible for every workload: You do not need to specify these hosts in your access policies.
aiven command
The aiven commands can be used to give access to an already existing Aiven service by creating a AivenApplication in your specified namespace and extract credentials. Specifically the aiven create…
Auth reference
In some cases, you want to locally develop and test against a secured API in the development environments. You will need a token to access said API.
Buckets reference
There is no automatic backup enabled for buckets. I.e. the files can not be restored in the event of accidental deletion or storage system failure.
CDN Upload Action
This is the reference documentation for the CDN Upload GitHub action. The action accepts the following inputs:
Container security
The following settings are applied to all containers running in Nais: To override these settings, see the following how-to guides:
Default workload variables
These environment variables will be injected into your workload container
Deploy action configuration
The available configuration options for the Nais deploy GitHub action. Note that OWNER and REPOSITORY corresponds to the two parts of a full repository identifier. If that name is…
device command
The device command can be used to connect to, disconnect from, and view the connection status of naisdevice. Currently, the command requires the processes naisdevice-agent and naisdevice-helper to…
DQL Reference
Dashboards Query Language (DQL) Reference for filtering data in nav-logs (OpenSearch Dashboards).
Entra ID reference
For all possible configuration options, see the 📚 Nais application reference. Your application will automatically be injected with the following environment variables at runtime.
Environment variables for Kafka
These variables are made available to your application when Kafka is enabled. Aiven has written several articles on how to configure your application. We use SSL, so ignore the SASL-SSL examples:
Environments
This is a overview over the different environments and their available domains. Environments are sometimes also called clusters.
Global Metrics
This is a list of metrics exposed by nais for all applications. The following labels are common to most metrics:
Grafana Glossary
This glossary contains terms and concepts related to Grafana. A dashboard is a collection of panels arranged in a grid layout. Each panel is a single visualization or a single query result. You can…
ID-porten reference
For all possible configuration options, see the 📚 Nais application reference. Your application will automatically be injected with the following environment variables at runtime.
Ingress reference
This is the reference documentation for ingresses in Nais. Ingress is the only way to expose your application to the outside world, this is not the recommended way to communicate between applications…
Kafka Pools
This is a list of available Kafka pools for topics and applications. Topic resources can only be specified in GCP clusters. Applications can access topics from any cluster, including on-premises.
kubeconfig command
Create a kubeconfig file for connecting to available clusters for you. This requires that you have the gcloud command line tool installed, configured and logged in. You can log in with gcloud auth…
Log Destinations
Available log destinations for application logging in Nais.
LogQL Reference
LogQL reference documentation for querying logs in Grafana Loki.
Loki Labels Reference
Loki label reference documentation for querying logs in Grafana Loki.
Maskinporten reference
See the 📚 Nais application reference. Your application will automatically be injected with environment variables at runtime.
Metrics reference
When using Prometheus the retention is 30 days. If you need data stored longer than what Prometheus support, we recommend using BigQuery. Then you have full control of the database and retention.
Nais Application example YAML
This is a complete example of an Application resource, commonly known as the nais.yaml file. For an in-depth explanation of each field, head over to the reference documentation.
Nais Application reference
This document describes all possible configuration values in the Application spec, commonly known as the nais.yaml file.
Nais Job example YAML
This is a complete example of an Naisjob resource. For an in-depth explanation of each field, head over to the reference documentation.
Nais Job reference
This document describes all possible configuration values in the Naisjob spec. By default, no traffic is allowed between naisjobs inside the cluster. Configure access policies to explicitly allow…
Nais Postgres example YAML
This is a complete example of a Postgres resource, commonly known as the postgres.yaml file. For an in-depth explanation of each field, head over to the reference documentation.
Nais Postgres reference
This document describes all possible configuration values in the Postgres spec, commonly known as the postgres.yaml file.
Nais Topic example YAML
This is a complete example of an Topic resource, commonly known as the topic.yaml file. For an in-depth explanation of each field, head over to the reference documentation.
Nais Topic reference
This document describes all possible configuration values in the Topic spec, commonly known as the topic.yaml file.
Observability Glossary
Observability is the art of understanding how a system behaves by adding instrumentation such as logs, metrics, and traces.
OpenSearch reference
The spec.openSearch configuration allows you to reference a single OpenSearch instance with a desired access mode.
OpenTelemetry Auto-Instrumentation Configuration
When you enable auto-instrumentation in your application the following OpenTelemetry configuration will become available to your application as environment variables:
OpenTelemetry Metrics
This is a list of metrics exported by the OpenTelemetry SDKs and auto-instrumentation libraries. The OpenTelemetry SDKs and auto-instrumentation libraries export the following general metrics:
OpenTelemetry Trace Semantic Conventions
OpenTelemetry Trace Semantic Conventions can be found at opentelemetry.io.
postgres command
The postgres command can be used to connect to a cloudsql postgres database with your personal user It includes subcommands for granting personal access to an instance, setting up a cloudsql proxy,…
Postgres reference
The full configuration options for the Postgres instance can be found in the application spec reference.
Postgres reference
The full configuration options for the Postgres instance can be found in the Postgres resource reference.
Prometheus Alerting Rule Reference
PrometheusRule resource specification for defining alerts in Prometheus.
PromQL Reference
PromQL reference documentation for querying metrics in Prometheus.
Secrets reference
This is the reference documentation for secrets on the Nais platform. Visit Nais Console to find and manage your team's user-defined secrets.
Span Metrics
Span metrics are collected for each span and provide insight into the performance of your application. On our platform, these metrics are generated by the Grafana Tempo metrics generator and exported…
TokenX reference
See the 📚 Nais application reference. Your application will automatically be injected with environment variables at runtime.
TraceQL Reference
TraceQL reference documentation for querying traces in Grafana Tempo.
validate command
Use multiple arguments to validate multiple files: Available flags:
Validation and autocompletion in editors
We expose two JSON schemas intended for use with editors to help the developer experience. These can be used for validation, autocompletion and documentation in supported editors.
Valkey reference
The spec.valkey field takes a list of records of two fields, instance and access: For details, see the manifest reference for your workload type:
Vulnerability reference
Due to Trivy, you'll receive a simplified dependency graph, as Trivy doesn't support Gradle or Maven's dependency resolution.
Webproxy
In Navs on-premises environments, workloads that need to make external HTTP(S) requests must set webproxy to true in their application spec.