From code to deploy in 30 minutes 🚀

This playbook helps you quickly deploy your first application to the developer platform.

By the end of this session, you will have:

  • Access to IDP
  • Your code packaged as a container
  • Deployed via GitOps with visibility in ArgoCD
  • Monitoring via Prometheus, logging via Loki, and visualization in Grafana
  • You comply with the platform’s security requirements
  • You are ready to use IDP in your daily work

🚨 The examples use Politiken-specific domains and variables.
Make sure to replace all values with values relevant to your own organization.

Example: https://github.com/jppol-idp/apps-pol → https://github.com/jppol-idp/apps-yourdomain

⏱️ Prerequisites

Before you begin, make sure you have the following in place:

🪛 Step-by-Step: Deploy Your First Workload

1. 📁 Create an app in your code repository (se example https://github.com/Politiken/idp-test)

Tip: Name the app after yourself to make it easy to identify.

mkdir app-name && cd app-name
echo 'print("Hello, IDP!")' > app-name.py

Add a Dockerfile:

FROM python:3.11-slim
WORKDIR /app-name
COPY app-name.py .
CMD ["python", "app-name.py"]

2. 🐳 Build and optionally test your image locally 

docker build . -t app-name.py:0.1.0
docker run app-name.py:0.1.0

3. Upload your image to the IDP ECR repository

🚨 You typically don’t have permission to upload images directly — but Politiken’s GitHub organization does.

This GitHub Action builds, tags, and uploads your image to ECR in our idp-shared account: 354918371398 https://github.com/Politiken/idp-test/blob/master/.github/workflows/build-push-deploy.yaml

uses: jppol-idp/tag-and-push-ecr@a7bb367d9e4393d243da605e4c4b700c18e2c34d
namespace: pol
image_tags: $

The ECR repository allows GitHub Actions from Politiken’s organization to upload images here: arn:aws:ecr:eu-west-1:354918371398:repository/pol/*

You can verify the image upload by assuming the IDP-client-read-access role in the AWS account aws-jppol-idp-shared aws-jppol-idp-shared

Automatic deployment

Once the image is uploaded, deployment can be triggered directly from your code repository using GitHub secrets configured in Politiken’s org:

  • IDP_DEPLOY_APP_ID
  • IDP_DEPLOY_APP_KEY
        uses: actions/create-github-app-token@v1
        with:
          app-id: $
          private-key: $
          owner: $
          repositories: apps-pol

GitHub app installation link https://github.com/organizations/jppol-idp/settings/installations/61380040

4. Create deployment configuration

Prepare a Helm chart in the deploy repo: https://github.com/jppol-idp/apps-pol

git clone https://github.com/jppol-idp/apps-pol.git
cd apps-pol/apps/pol-test
mkdir app-name

A deployment typically consists of two files:

application.yaml - describes the Helm chart:

apiVersion: v2
name: app-name
description: my first idp app
version: 0.1.0    # <-- version af deployment definition

helm:
  chart: helm/idp-advanced
  chartVersion: "0.1.14"    # <-- version af helm chart

The chart helm/idp-advanced refers to jppol-idp/helm-idp-advanced

values.yaml- defines deployment-specific variables:

image:
  repository: 354918371398.dkr.ecr.eu-west-1.amazonaws.com/pol/app 
  pullPolicy: IfNotPresent
  tag: "0.1.0"

You can go here and find a list of all configurable variables

5. 📦 Commit and push to your GitOps repo and see deployment in ArgoCD

After committing your chart.yaml and values.yaml files to your “apps-pol” github repository deployment will start.

Check in ArgoCD if your app has been synchronised and deployed and a certificate been issued.

Go to ArgoCD for deployment https://argocd.pol-test.idp.jppol.dk

6. Confirm log output in Grafana

Metrics are automatically exposed with Prometheus and Loki and are visible in Grafana.

Go to Grafana for monitoring (https://grafana.pol-test.idp.jppol.dk)

Go to drilldown to see your Prometheus stats image

Go and drilldown and filter your logs with Loki image

7. 🏁 Congratulations

You’re now up and running! 💪

You are always very welcome to ask questions in Slack - we’re happy to help!

Also, feel free to explore our FAQ for answers to frequently asked questions and onboarding guidance.

Last updated: 2025-06-23