https://github.com/dynatrace/demo-crossplane

Fully automated Dynatrace configuration as code using Kubernetes and Crossplane
https://github.com/dynatrace/demo-crossplane

configuration-as-code crossplane demo dynatrace kubernetes

Last synced: about 21 hours ago
JSON representation

Fully automated Dynatrace configuration as code using Kubernetes and Crossplane

• Host: GitHub
• URL: https://github.com/dynatrace/demo-crossplane
• Owner: Dynatrace
• License: apache-2.0
• Created: 2024-10-01T00:51:28.000Z (about 2 months ago)
• Default Branch: main
• Last Pushed: 2024-10-17T04:33:51.000Z (29 days ago)
• Last Synced: 2024-10-19T06:51:13.763Z (27 days ago)
• Topics: configuration-as-code, crossplane, demo, dynatrace, kubernetes
• Language: Shell
• Homepage: https://dynatrace.github.io/demo-crossplane/
• Size: 1.33 MB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Observability Lab: Using Crossplane to Automate Dynatrace Configuration as Code on Kubernetes

![logical flow](docs/images/auto-tags-dt-ui.png)

Dynatrace has long been compatible with [configuration as code](https://docs.dynatrace.com/docs/manage/configuration-as-code) using both [Monaco](https://docs.dynatrace.com/docs/manage/configuration-as-code/monaco) and [Terraform](https://docs.dynatrace.com/docs/manage/configuration-as-code/terraform).

Both Monaco and Terraform need to be triggered so usually this is handled by a pipeline, CRON Job or another regularly executing task.

Crossplane provides a way to have a 24/7 automated reconciliation loop without needing to trigger Monaco or Terraform on demand.

## Quick overview of Crossplane

[Crossplane](https://www.crossplane.io/) is a CNCF project which can bring true automated GitOps workflows to managing Dynatrace configuration.

Crossplane itself, of course, doesn't know how to talk to infrastructure providers like AWS or Dynatrace. So you need to install a Crossplane Provider.

These providers contain the "know how" to communicate with individual backends (like AWS) or in this case, Terraform.

This tutorial uses Crossplane with the [Terraform provider](https://marketplace.upbound.io/providers/upbound/provider-terraform/v0.18.0).

The tutorial also specifies [the Dynatrace terraform provider](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest) which "knows" how speak to Dynatrace.

> So, crossplane has a Terraform provider and the Terraform provider in turn has a Dynatrace provider.

Crossplane will be configured to watch a repository (your fork of this repository) for new Terraform configurations which it will then automatically apply to your Dynatrace environment.

![architecture diagram](docs/images/crossplane-architecture.jpg)

## Fork this repository

You will be making changes to the code in this repo. So begin by forking this repo to your own account.

Make all changes in your fork.

## [Start the hands-on here >>](https://dynatrace.github.io/demo-crossplane)