README
¶
E2E Test Suite
The e2e test suite is used to test common scenarios in each supported dns provider. The suite contains tests for single instance tests (single_record) where only a single running controller are expected as well as multi instance tests (multi_record) that are intended to test scenarios where multiple instances of the dns operator are running, each reconciling DNSRecord resources contributing to the same shared dns zone. The suite allows runtime configuration to alter the number of instances that are under test allowing stress testing scenarios to be executed using more extreme numbers of instances and records.
Local Setup
Cluster scoped on single cluster
Deploy the operator on a single kind cluster with one operator instance watching all namespaces:
make local-setup DEPLOY=true
Namespace scoped on single cluster
Deploy the operator on a single kind cluster with two operator instances in two namespaces watching their own namespace only:
make local-setup DEPLOY=true DEPLOYMENT_SCOPE=namespace DEPLOYMENT_COUNT=2
The above will create two dns operator deployments on the kind cluster, each configured to watch its own namespace, with the development managedzones (Assuming you have configured them locally) created in each deployment namespace.
DNS Operator Deployments:
kubectl get deployments -l app.kubernetes.io/part-of=dns-operator -A
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
dns-operator-1 dns-operator-controller-manager-1 1/1 1 1 96s
dns-operator-2 dns-operator-controller-manager-2 1/1 1 1 96s
ManagedZones:
kubectl get managedzones -A
NAMESPACE NAME DOMAIN NAME ... READY
dns-operator-1 dev-mz-aws mn.hcpapps.net ... True
dns-operator-1 dev-mz-gcp mn.google.hcpapps.net ... True
dns-operator-2 dev-mz-aws mn.hcpapps.net ... True
dns-operator-2 dev-mz-gcp mn.google.hcpapps.net ... True
dnstest dev-mz-aws mn.hcpapps.net
dnstest dev-mz-gcp mn.google.hcpapps.net
Cluster scoped on multiple clusters
Deploy the operator on two kind clusters each with one operator instance watching all namespaces:
make local-setup DEPLOY=true CLUSTER_COUNT=2
Namespace scoped on multiple clusters
Deploy the operator on two local kind clusters with two operator instances in two namespaces watching their own namespace only:
make local-setup DEPLOY=true DEPLOYMENT_SCOPE=namespace DEPLOYMENT_COUNT=2 CLUSTER_COUNT=2
Run the test suite
Cluster scoped on single cluster
make test-e2e TEST_DNS_MANAGED_ZONE_NAME=dev-mz-aws TEST_DNS_NAMESPACES=dnstest
Namespace scoped on single cluster
make test-e2e TEST_DNS_MANAGED_ZONE_NAME=dev-mz-aws TEST_DNS_NAMESPACES=dns-operator DEPLOYMENT_COUNT=2
Cluster scoped on multiple clusters
make test-e2e TEST_DNS_MANAGED_ZONE_NAME=dev-mz-aws TEST_DNS_NAMESPACES=dnstest TEST_DNS_CLUSTER_CONTEXTS=kind-kuadrant-dns-local CLUSTER_COUNT=2
Namespace scoped on multiple clusters
make test-e2e TEST_DNS_MANAGED_ZONE_NAME=dev-mz-aws TEST_DNS_NAMESPACES=dns-operator DEPLOYMENT_COUNT=2 TEST_DNS_CLUSTER_CONTEXTS=kind-kuadrant-dns-local CLUSTER_COUNT=2
Tailing operator pod logs
It's not possible to tail logs across namespaces with kubectl logs -f, but third party plugins such as stern can be used instead.
kubectl stern -l control-plane=dns-operator-controller-manager --all-namespaces
If development mode is disabled and json logs are being used you can pipe the logs into jq:
kubectl stern -l control-plane=dns-operator-controller-manager --all-namespaces -i 'logger' -o raw | jq .
Use jq to select the filter down to the logs you care about:
kubectl stern -l control-plane=dns-operator-controller-manager --all-namespaces -i 'logger' -o raw | jq 'select(.logger=="dnsrecord_controller")'
Directories