migrating_from_naisd.md

Migration from naisd to naiserator

Converting the manifest

Your nais manifest, commonly known as nais.yaml, needs to be converted from its current format into the new format.

The old format looks like this:

image: navikt/nais-testapp
team: teamName
port: 8080
(...)

The new format looks like this. We also provide a complete example of a nais application spec.

apiVersion: "nais.io/v1alpha1"
kind: "Application"
metadata:
  name: nais-testapp
  namespace: default
  labels:
    team: teamName
spec:
  image: navikt/nais-testapp:1.2.3
  port: 8080
(...)

Follow the checklist to complete the migration:

• Use the apiVersion, kind, metadata and spec fields.
• Include the version of your Docker container in the .spec.image field.
• healthcheck is removed, and liveness and readiness has been moved to the top-level.
• The redis field has been removed (#6)
• The alerts field has been removed (#7)
• The ingress field has been replaced by ingresses and need to specified explicitly (#14)
• The fasitResources field has been removed (#15)

Cluster access

Your converted manifest is a Kubernetes custom resource, and as such, it needs to be deployed directly to a Kubernetes cluster. This means you need to have kubectl access, which in turn requires:

• Install and configure kubectl
• Create an Azure AD group for your team, for human access to the cluster
• Request a machine (deploy) user for your CI pipeline in the #nais Slack channel.

Deploying applications

Once everything is set up:

kubectl apply -f nais.yaml