Open bak-fts opened 2 months ago
Hi, @bak-fts, thank you for bringing up this, we would appreciate it if you would like to contribute.
We have a guide on adding new resources here, some parts may be out of date, if you have any questions feel free to ask.
We can also consider combining this issue with https://github.com/crossplane-contrib/provider-upjet-azure/issues/732
+1
Anyway, we handled it by installing the flux as a Helm provider Release:
- name: flux2
base:
apiVersion: helm.crossplane.io/v1beta1
kind: Release
spec:
forProvider:
chart:
name: flux2
repository: https://fluxcd-community.github.io/helm-charts
version: "2.12.2"
namespace: flux-system
wait: true
waitTimeout: "300s"
patches:
- type: PatchSet
patchSetName: metadata
- type: PatchSet
patchSetName: providerConfig
Maybe it can help you @bak-fts
What resource do you need?
Terraform Resource Name:
azurerm_kubernetes_cluster_extension
What is your use case?
Enabling the Flux extension in an AKS cluster in a Crossplane-native way. Currently enabling it via the Terraform provider, which often causes issues due to very long reconciliation times of the Terraform workspace, leading to timeouts and dangling leases that require manual cleanup.