This issue will sum up the scope/work required to migrate to angular & material v9.

Upgrading the library code itself is actually the small portion of the work required.
Most of the work will be on compatibility and refactoring of code used by the build process
of the library and the demo/docs application.

I will track the progress of upgrading to angular v9 (including material plugins)

Description

CloudFormation released resource import
How should we support it in the CDK?

Progress

There's a warning note in README.md detailing:

Warning - the AnalyzeDocument process from AWS Textract costs $50 per 1,000 PDF pages. Be careful when deploying this CDK stack as you could unintentionally rack up an expensive AWS bill quickly if you're not paying attention.

This might not be enough - if a user finds this project and doesn't read the documentation, they could inadvertently

The API docs that are auto generated are pathetic currently and it's mostly jsdoc2md's fault. LOTS of polish needs to be done here so it can be usable. Types must be added and more docs in the code level for constructs.

In the docs, clarify bits related to AD configuration including:

• "Start by creating a user for yourself". Should this user also be added to the CorporateVpnUsers group?
• AD group creation. What scope and group type should be used for these groups?

GPU version requires pre-requisites on AWS/GCP (Nvidia driver on host)
This requires specific documentation

Issue

I deployed a kubernetes-core cluster v1.11 cluster with Conjure up on LXD.

I deployed Rancher 2 on top of K8s cluster

juju config kubernetes-worker allow-privileged=true
juju config kubernetes-master allow-privileged=true
juju config kubernetes-master authorization-mode="RBAC,Node"

wget https://raw.githubusercontent.com/CanonicalLtd/canonical-kubernetes-third-party-integrati