The DNS Operator is a kubernetes based controller responsible for reconciling DNS Record and Managed Zone custom resources. It interfaces with cloud DNS providers such as AWS and Google to bring the DNS zone into the state declared in these CRDs.
+
The DNS Operator is a kubernetes based controller responsible for reconciling DNS Record custom resources. It interfaces with cloud DNS providers such as AWS and Google to bring the DNS zone into the state declared in these CRDs.
One of the key use cases the DNS operator solves, is allowing complex DNS routing strategies such as Geo and Weighted to be expressed allowing you to leverage DNS as the first layer of traffic management. In order to make these strategies valuable, it also works across multiple clusters allowing you to use a shared domain name balance traffic based on your requirements.
make local-setup-aws-mz-clean local-setup-aws-mz-generate AWS_ZONE_ROOT_DOMAIN=<MY AWS Zone Root Domain> AWS_DNS_PUBLIC_ZONE_ID=<My AWS DNS Public Zone ID> AWS_ACCESS_KEY_ID=<My AWS ACCESS KEY> AWS_SECRET_ACCESS_KEY=<My AWS Secret Access Key>
+make local-setup-aws-clean local-setup-aws-generate AWS_ACCESS_KEY_ID=<My AWS ACCESS KEY> AWS_SECRET_ACCESS_KEY=<My AWS Secret Access Key>
GCP Provider
-make local-setup-gcp-mz-clean local-setup-gcp-mz-generate GCP_ZONE_NAME=<My GCP ZONE Name> GCP_ZONE_DNS_NAME=<My Zone DNS Name> GCP_GOOGLE_CREDENTIALS='<My GCP Credentials.json>' GCP_PROJECT_ID=<My GCP PROJECT ID>
+make local-setup-gcp-clean local-setup-gcp-generate GCP_GOOGLE_CREDENTIALS='<My GCP Credentials.json>' GCP_PROJECT_ID=<My GCP PROJECT ID>
AZURE Provider
-make local-setup-azure-mz-clean local-setup-azure-mz-generate KUADRANT_AZURE_CREDENTIALS='<My Azure Credentials.json>' KUADRANT_AZURE_DNS_ZONE_ID=<My Azure Zone ID> KUADRANT_AZURE_ZONE_ROOT_DOMAIN='<My Azure Domain Name>'
+make local-setup-azure-clean local-setup-azure-generate KUADRANT_AZURE_CREDENTIALS='<My Azure Credentials.json>'
Info on generating service principal credentials here
+Get your resource group ID like so:
+
az group show --resource-group <resource group name> | jq ".id" -r
+
Also give traffic manager contributor role:
+
az role assignment create --role "Traffic Manager Contributor" --assignee $EXTERNALDNS_SP_APP_ID --scope <RESOURCE_GROUP_ID>
+
Getting the zone ID can be achieved using the below command:
-
az network dns zone show --name <my domain name> --resource-group <my resource group> --query "{id:id,domain:name}"
+az network dns zone show --name <my domain name> --resource-group <my resource group> --query "{id:id,domain:name}"
Running controller locally (default)
-
Create local environment(creates kind cluster)
-
make local-setup
+
-
Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):
-make run
+
Running controller on the cluster
-
Create local environment(creates kind cluster)
-
make local-setup DEPLOY=true
+make local-setup DEPLOY=true
-
Verify controller deployment
-
kubectl logs -f deployments/dns-operator-controller-manager -n dns-operator-system
+kubectl logs -f deployments/dns-operator-controller-manager -n dns-operator-system
-
-
-
-
-
-
-
-
-
+
+
+
+
The Kuadrant Custom Resource Definition (CRD)
kuadrant
-
- Note on Limitador
-The Kuadrant operator creates a Limitador CR named `limitador` in the same namespace as the Kuadrant CR. If there is a pre-existing Limitador CR of the same name the kuadrant operator will take ownership of that Limitador CR.
-
-
@@ -4042,7 +3311,7 @@ kuadrant
| No |
-The specification for Kuadrant custom resource. |
+Blank specification |
status |
@@ -4053,279 +3322,7 @@ kuadrant
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-limitador |
-Limitador |
-No |
-Configure limitador deployments. |
-
-
-
-Limitador
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-affinity |
-Affinity |
-No |
-Describes the scheduling rules for limitador pods. |
-
-
-replicas |
-Number |
-No |
-Sets the number of limitador replicas to deploy. |
-
-
-resourceRequirements |
-ResourceRequirements |
-No |
-Set the resource requirements for limitador pods. |
-
-
-pdb |
-PodDisruptionBudgetType |
-No |
-Configure allowed pod disruption budget fields. |
-
-
-storage |
-Storage |
-No |
-Define backend storage option for limitador. |
-
-
-
-PodDisruptionBudgetType
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-maxUnavailable |
-Number |
-No |
-An eviction is allowed if at most "maxUnavailable" limitador pods are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable". |
-
-
-minAvailable |
-Number |
-No |
-An eviction is allowed if at least "minAvailable" limitador pods will still be available after the eviction, i.e. even in the absence of the evicted pod. So for example you can prevent all voluntary evictions by specifying "100%". |
-
-
-
-Storage
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-redis |
-Redis |
-No |
-Uses Redis to store limitador counters. |
-
-
-redis-cached |
-RedisCached |
-No |
-Uses Redis to store limitador counters, with an in-memory cache |
-
-
-disk |
-Disk |
-No |
-Counters are held on disk (persistent). Kubernetes Persistent Volumes will be used to store counters. |
-
-
-
-Redis
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-configSecretRef |
-LocalObjectReference |
-No |
-ConfigSecretRef refers to the secret holding the URL for Redis. |
-
-
-
-RedisCached
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-configSecretRef |
-LocalObjectReference |
-No |
-ConfigSecretRef refers to the secret holding the URL for Redis. |
-
-
-options |
-Options |
-No |
-Configures a number of caching options for limitador. |
-
-
-
-Options
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-ttl |
-Number |
-No |
-TTL for cached counters in milliseconds [default: 5000] |
-
-
-ratio |
-Number |
-No |
-Ratio to apply to the TTL from Redis on cached counters [default: 10] |
-
-
-flush-period |
-Number |
-No |
-FlushPeriod for counters in milliseconds [default: 1000] |
-
-
-max-cached |
-Number |
-No |
-MaxCached refers to the maximum amount of counters cached [default: 10000] |
-
-
-
-Disk
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-persistentVolumeClaim |
-PVCGenericSpec |
-No |
-Configure resources for PVC. |
-
-
-Optimize |
-String |
-No |
-Defines optimization option of the disk persistence type. Valid options: "throughput", "disk" |
-
-
-
-PVCGenericSpec
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-storageClassName |
-String |
-No |
-Storage class name |
-
-
-resources |
-PersistentVolumeClaimResources |
-No |
-Resources represent the minimum resources the volume should have |
-
-
-volumeName |
-String |
-No |
-VolumeName is the binding reference to the PersistentVolume backing the claim |
-
-
-
-PersistentVolumeClaimResources
-
-
-
-| Field |
-Type |
-Required |
-Description |
-
-
-
-
-requests |
-Quantity |
-Yes |
-Storage resources requests to be used on the persisitentVolumeClaim |
-
-
-
+Currently blank specification.
KuadrantStatus
diff --git a/dev/kuadrant-operator/doc/reference/ratelimitpolicy/index.html b/dev/kuadrant-operator/doc/reference/ratelimitpolicy/index.html
index c89a7234..09e3410b 100644
--- a/dev/kuadrant-operator/doc/reference/ratelimitpolicy/index.html
+++ b/dev/kuadrant-operator/doc/reference/ratelimitpolicy/index.html
@@ -598,7 +598,7 @@
- ManagedZone
+ TLSPolicy
@@ -607,91 +607,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
-
-
-
-
-
-
+
+
+
+
+
@@ -2160,24 +2040,24 @@
-
+
-