---
# System prepended metadata

title: L/>pilot env

---

# L/>pilot env


* azure kubernetes service [**`DONE`**]
*-* 1x node **`1 D2 v3 (2 vCPU(s), 8 GB RAM) nodes x 730 Hours; Pay as you go; 0 managed OS disks – S4`**
*-* loadbalancer
*-* uksouth **`DONE`**
*-* single az **`DONE`**
*-* re-use cidr (re-used test2) **`UPDATED CIDR DOC`** **`DONE`**
*-* create spn **`DONE`** `need to validate with aks build` **`DONE`**
*-* create resource group (or check if existing is generic) **`DONE`**

* azure active directory b2c
*-* merchant **`DONE`**
*-* consumer **`DONE`**

hdinsight `DOING MONDAY - see DBA's`
azure keyvault **`DONE`**
azure cosmos DB **`DONE`**
azure sql server **`DONE`**
azure sql database(s)`DOING MONDAY - see DBA's`
azure cache for redis **`DONE`**
container registry **`DONE`**
data transfers
storage accounts **`DONE`**
azured databricks `DOING MONDAY - see DBA's` (not needed - mark lewis)



create rbac/aad groups (component access) <- maybe create aks reader group and helpdesk can then nest further groups/users???

create platform kv **`DONE`**

helmsman:
* create environment -- f/bow/loyalty-pilot (init) **`DONE`**
* mute selected microservices **`DONE`** ^
* apply appropriate build id's (dt03 but confirm)

imperva
create website

ingrsess/certs - nginx (standard process for now) <- feed output from istio tests (mtls)