content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
`config.yaml` to deidentify data in BigQuery ```yaml project: project-id region: us-central1 job\_name: dlp-deid-pipeline service\_account: dlp-deid-pipeline-sa@project-id.iam.gserviceaccount.com machine\_type: n1-standard-2 max\_num\_workers: 30 job\_dir: gs://staging-bucket # DLP Params inspect\_template: projects/pr... | https://github.com/GoogleCloudPlatform/professional-services/blob/main/examples/dlp-deid-pipeline/README.md | main | gcp-professional-services | [
0.017984645441174507,
0.020984768867492676,
-0.01901850663125515,
-0.04785507544875145,
-0.04015230014920235,
-0.03245587646961212,
0.0029492611065506935,
0.01831778697669506,
-0.026257483288645744,
0.07051760703325272,
-0.0045660496689379215,
-0.10101428627967834,
0.00019905949011445045,
... | 0.003418 |
# DLP Templates [Templates](https://cloud.google.com/sensitive-data-protection/docs/concepts-templates) are reusable configurations that tell DLP how to inspect, de-identify, or re-identify your data. This solution considers the following as sensitive data and provides the expected outcome: | PII Info Type | Original |... | https://github.com/GoogleCloudPlatform/professional-services/blob/main/examples/dlp-deid-pipeline/src/dlp/templates/README.md | main | gcp-professional-services | [
-0.10603044182062149,
0.10905270278453827,
0.05150607228279114,
-0.02881558984518051,
0.008370704017579556,
0.058089856058359146,
0.07085699588060379,
-0.07524988800287247,
0.0472831092774868,
-0.04262349009513855,
0.04018917679786682,
-0.05101865157485008,
0.004501932300627232,
-0.1001758... | -0.045918 |
# Sentiment analysis using TensorFlow RNNEstimator on Google Cloud Platform. ### Overview. This code aims at providing a simple example of how to train a RNN model using TensorFlow [RNNEstimator](https://www.tensorflow.org/api\_docs/python/tf/contrib/estimator/RNNEstimator) on Google Cloud Platform. The model is design... | https://github.com/GoogleCloudPlatform/professional-services/blob/main/examples/cloudml-sentiment-analysis/README.md | main | gcp-professional-services | [
-0.13002192974090576,
-0.06574466079473495,
-0.023815317079424858,
0.026636967435479164,
0.04031883552670479,
0.05377316474914551,
0.003213605610653758,
-0.03165517747402191,
0.005543617997318506,
-0.05479970946907997,
-0.02142784744501114,
-0.03720702975988388,
0.020663591101765633,
0.032... | 0.103084 |
# Pi-hole This tutorial describes how to setup ExternalDNS to sync records with Pi-hole's Custom DNS. Pi-hole has an internal list it checks last when resolving requests. This list can contain any number of arbitrary A, AAAA or CNAME records. There is a pseudo-API exposed that ExternalDNS is able to use to manage these... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/pihole.md | master | external-dns | [
-0.10573084652423859,
-0.0720718502998352,
-0.014831389300525188,
0.013374587520956993,
-0.1193699985742569,
-0.026844633743166924,
-0.03689199686050415,
-0.02888289839029312,
0.06694298982620239,
0.04167380928993225,
-0.01039726473391056,
-0.02248646505177021,
0.04948301985859871,
-0.0530... | -0.007645 |
can be used to verify Services work. For services ExternalDNS will look for the annotation `external-dns.kubernetes.io/hostname` on the service and use the corresponding value. ```yaml --- apiVersion: v1 kind: Service metadata: name: nginx annotations: external-dns.kubernetes.io/hostname: nginx.external-dns-test.homela... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/pihole.md | master | external-dns | [
-0.0797446146607399,
0.013810819014906883,
0.027617091313004494,
-0.050746988505125046,
-0.04050741717219353,
-0.03185427561402321,
-0.03328729793429375,
-0.05582638457417488,
0.12013955414295197,
0.031235674396157265,
-0.06541240960359573,
-0.060322005301713943,
-0.00943568255752325,
0.00... | 0.091397 |
# GKE with default controller This tutorial describes how to setup ExternalDNS for usage within a [GKE](https://cloud.google.com/kubernetes-engine) ([Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)) cluster. Make sure to use \*\*>=0.11.0\*\* version of ExternalDNS for this tutorial ## Single proje... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md | master | external-dns | [
-0.0691114142537117,
-0.0269785113632679,
0.01697753369808197,
-0.02556326799094677,
-0.10166440904140472,
-0.015932824462652206,
0.013418808579444885,
-0.025920463725924492,
0.029376836493611336,
0.036737050861120224,
-0.034685567021369934,
-0.10769235342741013,
0.040891382843256,
-0.0319... | 0.029013 |
projects, and then use one of the three methods to grant access to ExternalDNS. Replace the environment variables to values that make sense in your environment. #### Configure Projects For this process, create projects with the appropriate APIs enabled. ```bash # set variables to appropriate desired values GKE\_PROJECT... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md | master | external-dns | [
-0.047182347625494,
-0.022442996501922607,
-0.02843979001045227,
-0.04049353674054146,
-0.07513032853603363,
-0.029256219044327736,
0.043198361992836,
0.00373379816301167,
0.008131677284836769,
0.06100120767951012,
-0.0674639642238617,
-0.09481173753738403,
0.031551577150821686,
0.00998865... | -0.047886 |
{ project\_id = var.gke-project } locals { member = "principal://iam.googleapis.com/projects/${data.google\_project.project.number}/locations/global/workloadIdentityPools/${var.gke-project}.svc.id.goog/subject/ns/${var.kns\_name}/sa/${var.ksa\_name}" } resource "google\_project\_iam\_member" "external\_dns" { member = ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md | master | external-dns | [
-0.04146910458803177,
-0.015208946540951729,
0.03270718827843666,
-0.016934754326939583,
-0.04452934488654137,
-0.07412246614694595,
0.05914654582738876,
-0.04018225893378258,
-0.015170393511652946,
0.030872078612446785,
-0.014777184464037418,
-0.11394265294075012,
-0.003696839092299342,
-... | -0.030694 |
away, and you should see info messages, such as: `All records are already up to date`. ## Deploy ExternalDNS Then apply the following manifests file to deploy ExternalDNS. ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: external-dns labels: app.kubernetes.io/name: external-dns --- apiVersion: rbac.authoriza... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md | master | external-dns | [
-0.01584029011428356,
-0.0604671873152256,
0.036825843155384064,
-0.013514215126633644,
-0.0016276249662041664,
-0.014736330136656761,
-0.026783820241689682,
-0.032597143203020096,
0.08668984472751617,
0.0833107978105545,
-0.014995047822594643,
-0.05545883625745773,
-0.016773540526628494,
... | 0.126292 |
Ingress works as well. Create the following Ingress. ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: nginx spec: rules: - host: server.example.com http: paths: - path: / pathType: Prefix backend: service: name: nginx port: number: 80 ``` Create the ingress objects with: ```bash kubectl create --n... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md | master | external-dns | [
-0.09596279263496399,
0.016642406582832336,
0.004785364028066397,
-0.03325924649834633,
-0.08547119051218033,
-0.0484209805727005,
-0.006727791391313076,
0.0016092812875285745,
0.03909161314368248,
0.07553692162036896,
-0.08185741305351257,
-0.06100178882479668,
0.04552963003516197,
-0.032... | 0.132517 |
# Plural This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Plural DNS. Make sure to use \*\*>=0.12.3\*\* version of ExternalDNS for this tutorial. ## Creating Plural Credentials A secret containing the a Plural access token is needed for this provider. You can get a token for ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/plural.md | master | external-dns | [
-0.04085970297455788,
-0.0382516048848629,
0.018388502299785614,
-0.029467854648828506,
-0.0902569442987442,
0.0013332413509488106,
-0.03976307436823845,
0.0231892429292202,
0.12621544301509857,
0.04212840273976326,
-0.04044300317764282,
-0.1311485469341278,
0.029860826209187508,
-0.017350... | 0.075834 |
By setting the TTL annotation on the service, you have to pass a valid TTL, which must be 120 or above. This annotation is optional, if you won't set it, it will be 1 (automatic) which is 300. ExternalDNS uses this annotation to determine what services should be registered with DNS. Removing the annotation will cause E... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/plural.md | master | external-dns | [
-0.08731146156787872,
-0.03062729723751545,
0.04952522739768028,
-0.10095778107643127,
-0.0859927162528038,
-0.042316921055316925,
-0.000012240357136761304,
-0.0520615428686142,
0.14992575347423553,
0.016680032014846802,
-0.038719482719898224,
-0.056141968816518784,
0.029412757605314255,
-... | 0.054386 |
# Akamai Edge DNS ## Prerequisites External-DNS v0.8.0 or greater. ### Zones External-DNS manages service endpoints in existing DNS zones. The Akamai provider does not add, remove or configure new zones. The [Akamai Control Center](https://control.akamai.com) or [Akamai DevOps Tools](https://developer.akamai.com/devops... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/akamai-edgedns.md | master | external-dns | [
-0.11102926731109619,
-0.021909847855567932,
-0.006695871241390705,
-0.03180890530347824,
-0.05265119671821594,
-0.036095909774303436,
-0.04625958576798439,
-0.01723392680287361,
0.009266468696296215,
0.07941648364067078,
0.006741363555192947,
-0.07916927337646484,
-0.02602868713438511,
-0... | 0.146358 |
name: EXTERNAL\_DNS\_AKAMAI\_ACCESS\_TOKEN valueFrom: secretKeyRef: name: AKAMAI-DNS key: EXTERNAL\_DNS\_AKAMAI\_ACCESS\_TOKEN ``` ### Manifest (for clusters with RBAC enabled) ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: external-dns --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadat... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/akamai-edgedns.md | master | external-dns | [
-0.05414385348558426,
-0.047084879130125046,
-0.03544967249035835,
-0.013553110882639885,
-0.0039088064804673195,
-0.017542021349072456,
0.026848632842302322,
-0.03326266631484032,
0.027509018778800964,
0.07160806655883789,
0.009383520111441612,
-0.054935891181230545,
0.019131546840071678,
... | 0.20105 |
# GoDaddy This tutorial describes how to set up ExternalDNS for use within a Kubernetes cluster using GoDaddy DNS. Make sure to use \*\*>=0.6\*\* version of ExternalDNS for this tutorial. ## Creating a zone with GoDaddy DNS If you are new to GoDaddy, we recommend you first read the following instructions for creating a... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/godaddy.md | master | external-dns | [
0.010209865868091583,
-0.05512164160609245,
0.018572285771369934,
-0.06457897275686264,
-0.05449065938591957,
0.0018605233635753393,
-0.07398337870836258,
0.021651284769177437,
0.11203592270612717,
0.04045039042830467,
-0.033271294087171555,
-0.10554032772779465,
0.028925133869051933,
-0.0... | 0.078699 |
zone (e.g. 'www.example.com'). The TTL annotation can be used to configure the TTL on DNS records managed by ExternalDNS and is optional. If this annotation is not set, the TTL on records managed by ExternalDNS will default to 10. ExternalDNS uses the hostname annotation to determine which services should be registered... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/godaddy.md | master | external-dns | [
-0.04111066833138466,
-0.010062494315207005,
0.05169755220413208,
-0.09568852186203003,
-0.046917591243982315,
-0.05356597900390625,
-0.044061072170734406,
-0.08952468633651733,
0.166826993227005,
0.001324392156675458,
-0.025340430438518524,
-0.015000391751527786,
0.03028147481381893,
-0.0... | 0.057188 |
# DNSimple This tutorial describes how to setup ExternalDNS for usage with DNSimple. Make sure to use \*\*>=0.4.6\*\* version of ExternalDNS for this tutorial. ## Create a DNSimple API Access Token A DNSimple API access token can be acquired by following the [provided documentation from DNSimple](https://support.dnsimp... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/dnsimple.md | master | external-dns | [
-0.11310376971960068,
-0.06074007228016853,
0.004970586393028498,
-0.01773185469210148,
-0.05358963459730148,
-0.0843036025762558,
-0.016681350767612457,
0.0607416070997715,
-0.027829114347696304,
0.02942865900695324,
-0.07986576855182648,
-0.07880911231040955,
0.004423540085554123,
0.0266... | 0.033662 |
your service it can take a little while for your cloud provider to create an external IP for the service. Check the status by running `kubectl get services nginx`. If the `EXTERNAL-IP` field shows an address, the service is ready to be accessed externally. Once the service has an external IP assigned, ExternalDNS will ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/dnsimple.md | master | external-dns | [
-0.12183830142021179,
-0.0237374696880579,
0.04397651180624962,
-0.04069697856903076,
-0.07677225768566132,
-0.05584922060370445,
-0.025109482929110527,
-0.073449045419693,
0.09919429570436478,
0.05744573473930359,
-0.05882205069065094,
-0.05216950178146362,
-0.012598264962434769,
-0.02119... | 0.068983 |
# ExternalName Services This tutorial describes how to setup ExternalDNS for usage in conjunction with an ExternalName service. ## Use cases The main use cases that inspired this feature is the necessity for having a subdomain pointing to an external domain. In this scenario, it makes sense for the subdomain to have a ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/externalname.md | master | external-dns | [
-0.11679858714342117,
-0.03233557567000389,
0.029530728235840797,
-0.05709118768572807,
-0.015498952940106392,
-0.09216942638158798,
-0.02284248173236847,
0.045732270926237106,
0.08186724781990051,
0.04630280286073685,
-0.023699820041656494,
-0.09038251638412476,
0.027886493131518364,
0.01... | 0.073267 |
# AWS Filters This document provides guidance on filtering AWS zones using various strategies and flags. ## Strategies for Scoping Zones > Without specifying these flags, management applies to all zones. In order to manage specific zones, there is a possibility to combine multiple options | Argument | Description | Flo... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-filters.md | master | external-dns | [
0.02158457413315773,
0.029609793797135353,
-0.021349191665649414,
-0.057385776191949844,
0.08295544981956482,
-0.047025151550769806,
-0.0012029760982841253,
-0.11511646211147308,
0.039997391402721405,
0.027107538655400276,
-0.05669063702225685,
-0.09769893437623978,
0.022067755460739136,
-... | -0.033803 |
V["Delete zone from zones map"] U -- Yes --> W["Keep zone in zones map"] V --> W W --> R R -- No --> X["Update zonesCache"] X --> Y["Return zones"] ``` \*\*\*Filtering Flow\*\*\* The is a sequence diagram that describes the interaction between `external-dns`, `AWSProvider`, and `Route53Client` during the filtering proc... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-filters.md | master | external-dns | [
-0.04061778262257576,
-0.011248941533267498,
-0.008713508024811745,
-0.03228432312607765,
0.06345220655202866,
-0.04379758611321449,
-0.018332822248339653,
-0.08832577615976334,
0.040597960352897644,
0.02582787349820137,
-0.016850672662258148,
-0.058730289340019226,
-0.014587290585041046,
... | 0.055279 |
# Alibaba Cloud This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster on Alibaba Cloud. Make sure to use \*\*>=0.5.6\*\* version of ExternalDNS for this tutorial ## RAM Permissions ```json { "Version": "1", "Statement": [ { "Action": "alidns:AddDomainRecord", "Resource": "\*", "Effect":... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/alibabacloud.md | master | external-dns | [
-0.044856779277324677,
-0.03458157181739807,
-0.0179237462580204,
0.010021314956247807,
-0.058936428278684616,
0.024117009714245796,
-0.012462274171411991,
-0.028400814160704613,
0.12864598631858826,
0.010268275626003742,
0.009133467450737953,
-0.056772008538246155,
-0.00451460387557745,
-... | 0.126937 |
zones matching provided domain, omit to process all available hosted zones - --provider=alibabacloud - --policy=upsert-only # would prevent ExternalDNS from deleting any records, omit to enable full synchronization - --alibaba-cloud-zone-type=public # only look at public hosted zones (valid values are public, private o... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/alibabacloud.md | master | external-dns | [
-0.05601081624627113,
-0.05692560225725174,
-0.05303845927119255,
0.007383532356470823,
0.01102216262370348,
-0.04651770740747452,
0.008900248445570469,
-0.10516247898340225,
0.061260808259248734,
0.05000220984220505,
0.006138097029179335,
-0.03965652734041214,
0.061861276626586914,
-0.106... | 0.00694 |
up the DNS records for you. Then delete the hosted zone if you created one for the testing purpose. ```console aliyun alidns DeleteDomain --DomainName external-dns-test.com ``` For more info about Alibaba Cloud external dns, please refer this [docs](https://yq.aliyun.com/articles/633412) | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/alibabacloud.md | master | external-dns | [
0.010181199759244919,
-0.05081533268094063,
-0.045419737696647644,
0.007616209331899881,
-0.019536107778549194,
-0.07933711260557175,
-0.062476176768541336,
-0.07964589446783066,
0.09695140272378922,
0.04137241840362549,
0.006023194640874863,
-0.004976514261215925,
0.041502777487039566,
-0... | -0.031115 |
# Using CRD Source for DNS Records This tutorial describes how to use the CRD source with ExternalDNS to manage DNS records. The CRD source allows you to define your desired DNS records declaratively using `DNSEndpoint` custom resources. ## Default Targets and CRD Targets ExternalDNS has a `--default-targets` flag that... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/crd.md | master | external-dns | [
-0.09469500929117203,
-0.051617175340652466,
0.019490770995616913,
-0.005885136779397726,
-0.035238172858953476,
-0.03259485214948654,
-0.001790681155398488,
-0.0143755367025733,
0.04321908578276634,
0.016856057569384575,
-0.026464834809303284,
-0.04802009463310242,
0.03646218031644821,
0.... | 0.031834 |
# Contour HTTPProxy This tutorial describes how to configure External DNS to use the Contour `HTTPProxy` source. Using the `HTTPProxy` resource with External DNS requires Contour version 1.5 or greater. ## Example manifests for External DNS ### Without RBAC ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: e... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/contour.md | master | external-dns | [
-0.13091184198856354,
-0.030605627223849297,
-0.03073863685131073,
-0.033738479018211365,
0.0007172984187491238,
-0.07254589349031448,
-0.03268149495124817,
0.003852227935567498,
0.03566008806228638,
0.07103008776903152,
-0.02929733321070671,
-0.06186835840344429,
0.01355300098657608,
0.00... | -0.011205 |
# CoreDNS - [Documentation](https://coredns.io/) ## Multi cluster support options The CoreDNS provider allows records from different CoreDNS providers to be separated in a single etcd by activating the setting `--coredns-strictly-owned` flag and set `txt-owner-id`. It will prevent any override (update/create/delete) of... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns.md | master | external-dns | [
-0.09835924953222275,
-0.020285019651055336,
0.012229577638208866,
-0.06437516212463379,
-0.017392726615071297,
-0.004610440228134394,
-0.07583501935005188,
-0.048935648053884506,
-0.05155590549111366,
-0.0031937623862177134,
0.042411383241415024,
-0.02379678376019001,
0.05274597182869911,
... | 0.075955 |
# Oracle Cloud Infrastructure This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using OCI DNS. Make sure to use the latest version of ExternalDNS for this tutorial. ## Creating an OCI DNS Zone Create a DNS zone which will contain the managed DNS records. Let's use `example.com` as a... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/oracle.md | master | external-dns | [
-0.06633967161178589,
-0.045556940138339996,
-0.004169851541519165,
-0.016916796565055847,
-0.08424083143472672,
-0.05765035003423691,
0.007219583727419376,
0.04190728813409805,
0.11068697273731232,
-0.015158267691731453,
-0.04125475510954857,
-0.08959214389324188,
0.01636091247200966,
-0.... | 0.103883 |
secret generic external-dns-config --from-file=oci.yaml ``` ## Manifest (for clusters with RBAC enabled) Apply the following manifest to deploy ExternalDNS. ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: external-dns --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: external-dn... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/oracle.md | master | external-dns | [
-0.06809675693511963,
-0.057487014681100845,
-0.01071107480674982,
-0.013790738768875599,
-0.011027757078409195,
-0.042923446744680405,
-0.004412745125591755,
-0.02082025445997715,
0.042355623096227646,
0.05172635614871979,
-0.020105192437767982,
-0.03243815526366234,
0.00014216256386134773,... | 0.127164 |
# Webhook provider The "Webhook" provider allows integrating ExternalDNS with DNS providers through an HTTP interface. The Webhook provider implements the `Provider` interface. Instead of implementing code specific to a provider, it implements an HTTP client that sends requests to an HTTP API. The idea behind it is tha... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/webhook-provider.md | master | external-dns | [
-0.12943097949028015,
0.054806046187877655,
-0.014793045818805695,
-0.06560104340314865,
-0.06339704245328903,
-0.0805751383304596,
-0.09718459099531174,
-0.0050414507277309895,
-0.0047741178423166275,
-0.03427540138363838,
-0.005844859406352043,
-0.03945725038647652,
-0.06489697098731995,
... | 0.107753 |
they affect DNS record management. ## Best practices for webhook provider authors ### Status codes Use the correct HTTP status codes — they directly control ExternalDNS retry behaviour: | Situation | Status code | Effect | | --------- | ----------- | ------ | | Success (`Records`, `AdjustEndpoints`) | `200 OK` | Accept... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/webhook-provider.md | master | external-dns | [
-0.1486799418926239,
0.039544228464365005,
-0.010803663171827793,
0.026212558150291443,
-0.008511622436344624,
-0.11196868121623993,
-0.04835006967186928,
-0.017949895933270454,
0.049266427755355835,
0.001952192629687488,
0.039429426193237305,
0.018070396035909653,
0.03305622562766075,
-0.... | 0.167878 |
# kOps dns-controller kOps includes a dns-controller that is primarily used to bootstrap the cluster, but can also be used for provisioning DNS entries for Services and Ingress. ExternalDNS can be used as a drop-in replacement for dns-controller if you are running a non-gossip cluster. The flag `--compatibility kops-dn... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/kops-dns-controller.md | master | external-dns | [
-0.10272177308797836,
-0.030448349192738533,
0.02059411257505417,
-0.02555696852505207,
0.032501645386219025,
0.017578473314642906,
-0.028953786939382553,
-0.03458059951663017,
0.10582751780748367,
-0.003821484511718154,
-0.004249374847859144,
-0.0014186067273840308,
-0.0488777682185173,
-... | 0.145308 |
# AWS Cloud Map API This tutorial describes how to set up ExternalDNS for usage within a Kubernetes cluster with [AWS Cloud Map API](https://docs.aws.amazon.com/cloud-map/). \*\*AWS Cloud Map\*\* API is an alternative approach to managing DNS records directly using the Route53 API. It is more suitable for a dynamic env... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-sd.md | master | external-dns | [
-0.05243711918592453,
-0.04097636044025421,
0.031138204038143158,
0.013478100299835205,
-0.09796865284442902,
0.03080836683511734,
-0.05269937589764595,
-0.019088629633188248,
0.10367641597986221,
0.07083386927843094,
-0.07114016264677048,
-0.055263686925172806,
0.036697402596473694,
-0.06... | 0.116705 |
external-dns template: metadata: labels: app: external-dns spec: containers: - name: external-dns image: registry.k8s.io/external-dns/external-dns:v0.21.0 env: - name: AWS\_REGION value: us-east-1 # put your CloudMap NameSpace region args: - --source=service - --source=ingress - --domain-filter=external-dns-test.my-org... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-sd.md | master | external-dns | [
-0.02736916020512581,
-0.0018762937979772687,
0.012720242142677307,
-0.021719876676797867,
-0.012108194641768932,
-0.0662975013256073,
-0.008646735921502113,
-0.019155075773596764,
0.055803585797548294,
0.051624514162540436,
-0.01511167362332344,
-0.11931432038545609,
0.016273362562060356,
... | 0.027536 |
nginx ``` Give ExternalDNS some time to clean up the DNS records for you. Then delete the remaining service and namespace. ```console $ aws servicediscovery list-services { "Services": [ { "Id": "srv-6dygt5ywvyzvi3an", "Arn": "arn:aws:servicediscovery:us-west-2:861574988794:service/srv-6dygt5ywvyzvi3an", "Name": "nginx... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-sd.md | master | external-dns | [
-0.07754284143447876,
-0.018542299047112465,
-0.01577002927660942,
-0.04484375938773155,
-0.01919151283800602,
-0.06999944895505905,
0.030860982835292816,
-0.10597549378871918,
0.1368519514799118,
0.10096389800310135,
-0.03380574285984039,
-0.0044361911714077,
0.01797213777899742,
0.026184... | 0.019928 |
# AWS and LocalStack ## Overview This tutorial demonstrates how to configure ExternalDNS to manage DNS records in LocalStack's Route53 service using a local Kind (Kubernetes in Docker) cluster. ### TL;DR After completing this lab, you will have a Kubernetes environment running as containers in your local development ma... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-localstack.md | master | external-dns | [
-0.031123140826821327,
-0.018809637054800987,
0.02873804233968258,
0.00914799515157938,
-0.06645458191633224,
-0.009354200214147568,
-0.0429401695728302,
0.007984400726854801,
0.05010334402322769,
0.06376529484987259,
-0.06807302683591843,
-0.059494245797395706,
-0.030111121013760567,
-0.0... | 0.044469 |
records that don't correspond to Kubernetes services - Managing complex DNS configurations (multiple targets, weighted routing) - Integrating with external systems or custom controllers Verify the CRD is installed ```sh kubectl get crd dnsendpoints.externaldns.k8s.io ``` ### Example 1: Multiple Records Create a simple ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-localstack.md | master | external-dns | [
-0.04495108127593994,
-0.009957046248018742,
0.014134305529296398,
-0.02620391920208931,
-0.05329246446490288,
-0.03886905685067177,
-0.023958880454301834,
-0.020925438031554222,
0.12314416468143463,
0.061541516333818436,
0.00690787797793746,
-0.10830455273389816,
0.03896237909793854,
-0.1... | 0.052418 |
LocalStack Route53 User->>K8s: kubectl apply -f service.yaml K8s->>K8s: Service created Note over ED: Watches for Service changes K8s->>ED: Service event detected ED->>ED: Parse annotation: nginx.example.com ED->>LS: Check existing records LS-->>ED: No record exists ED->>LS: Create A record nginx.example.com → LoadBala... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-localstack.md | master | external-dns | [
-0.10457827150821686,
-0.0020751545671373606,
0.013864134438335896,
-0.010614096187055111,
-0.004145985934883356,
-0.05105392634868622,
-0.022654853761196136,
-0.06494651734828949,
0.08721599727869034,
0.10262754559516907,
-0.02562444843351841,
-0.06425195932388306,
-0.02695951983332634,
-... | 0.099476 |
# AWS Load Balancer Controller This tutorial describes how to use ExternalDNS with the [aws-load-balancer-controller][1]. [1]: https://kubernetes-sigs.github.io/aws-load-balancer-controller ## Setting up ExternalDNS and aws-load-balancer-controller Follow the [AWS tutorial](aws.md) to setup ExternalDNS for use in Kuber... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-load-balancer-controller.md | master | external-dns | [
-0.08185671269893646,
0.005662940908223391,
-0.008070024661719799,
-0.017613431438803673,
-0.030729109421372414,
0.00040944264037534595,
0.06810019910335541,
-0.0005587316118180752,
0.09434754401445389,
0.05215766280889511,
-0.062438104301691055,
-0.11169987916946411,
0.027577174827456474,
... | 0.111001 |
for the resulting ALB. ## Dualstack Load Balancers AWS [supports both IPv4 and "dualstack" (both IPv4 and IPv6) interfaces for ALBs][4] and [NLBs][5]. The AWS Load Balancer Controller uses the `alb.ingress.kubernetes.io/ip-address-type` annotation (which defaults to `ipv4`) to determine this. ExternalDNS creates both A... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-load-balancer-controller.md | master | external-dns | [
-0.10384518653154373,
0.035337503999471664,
0.009992683306336403,
-0.02392631769180298,
-0.08542393893003464,
-0.0028771080542355776,
-0.01761781983077526,
-0.058479584753513336,
0.1226886436343193,
0.013059587217867374,
-0.06624013930559158,
-0.08520008623600006,
0.017849231138825417,
-0.... | 0.047016 |
# Headless Services This tutorial describes how to setup ExternalDNS for usage in conjunction with a Headless service. ## Use cases The main use cases that inspired this feature is the necessity for fixed addressable hostnames with services, such as Kafka when trying to access them from outside the cluster. In this sce... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/hostport.md | master | external-dns | [
-0.07161896675825119,
-0.03155918046832085,
-0.05859416350722313,
-0.004146039020270109,
-0.07000024616718292,
-0.010318798944354057,
-0.08374027162790298,
0.009014038369059563,
0.058177921921014786,
0.04489068314433098,
-0.018742170184850693,
-0.02052142284810543,
-0.015687482431530952,
-... | 0.121726 |
can omit the annotation. ```sh kafka-0.ksvc.example.org IP-0 kafka-1.ksvc.example.org IP-1 kafka-2.ksvc.example.org IP-2 ksvc.example.org IP-0,IP-1,IP-2 ``` #### Using pods' HostIPs as targets Add the following annotation to your `Service`: ```yaml external-dns.kubernetes.io/endpoints-type: HostIP ``` external-dns will... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/hostport.md | master | external-dns | [
-0.024210035800933838,
0.0027445729356259108,
0.016577957198023796,
-0.001216831267811358,
-0.006118507124483585,
-0.010070516727864742,
-0.020875614136457443,
-0.027744723483920097,
0.11112995445728302,
0.06473161280155182,
-0.04671238735318184,
-0.0603288933634758,
-0.024340491741895676,
... | 0.161112 |
# Exoscale ## Prerequisites Exoscale provider support was added via [this PR](https://github.com/kubernetes-sigs/external-dns/pull/625), thus you need to use external-dns v0.5.5. The Exoscale provider expects that your Exoscale zones, you wish to add records to, already exists and are configured correctly. It does not ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/exoscale.md | master | external-dns | [
-0.020575296133756638,
-0.035182952880859375,
0.030703796073794365,
-0.0352759025990963,
-0.06278566271066666,
-0.05335802584886551,
-0.024444881826639175,
0.007418374996632338,
0.0853886529803276,
0.10040926188230515,
-0.016818802803754807,
-0.0854606106877327,
-0.04750475287437439,
-0.01... | 0.096629 |
# GKE with nginx-ingress-controller This tutorial describes how to setup ExternalDNS for usage within a GKE cluster that doesn't make use of Google's [default ingress controller](https://github.com/kubernetes/ingress-gce) but rather uses [nginx-ingress-controller](https://github.com/kubernetes/ingress-nginx) for that t... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke-nginx.md | master | external-dns | [
-0.055094048380851746,
-0.00949817430227995,
0.006512794177979231,
-0.053210947662591934,
-0.044409818947315216,
-0.05964593216776848,
0.007688887882977724,
-0.02482893131673336,
0.011634411290287971,
0.04972528666257858,
-0.059214577078819275,
-0.1162392869591713,
0.043933331966400146,
-0... | 0.047614 |
put multiple IPs as targets in your Ingress objects in that case. It could also make sense to run it as a DaemonSet. However, we'll just run a single replica. You have to open the respective ports on all of your worker nodes to allow nginx to receive traffic. ```console gcloud compute firewall-rules create "allow-http"... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke-nginx.md | master | external-dns | [
-0.04555726796388626,
0.03146509453654289,
-0.010804113000631332,
-0.028012938797473907,
-0.0629037395119667,
-0.04338182508945465,
0.021163783967494965,
-0.0612679086625576,
-0.0036666356027126312,
0.08131766319274902,
-0.07529246062040329,
-0.08771108090877533,
0.06452663242816925,
-0.03... | 0.077186 |
on the first run. Note, that you will not see any records created when you are running in dry-run mode. You can, however, inspect the logs and watch what would have been done. ### Deploy a sample application Create the following sample application to test that ExternalDNS works. ```yaml apiVersion: networking.k8s.io/v1... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke-nginx.md | master | external-dns | [
-0.11007238924503326,
-0.02263525500893593,
-0.014423893764615059,
0.0006579376058652997,
-0.038697440177202225,
-0.13241063058376312,
-0.027558578178286552,
-0.06796278059482574,
0.041698165237903595,
0.04358596354722977,
-0.010645635426044464,
-0.021627001464366913,
-0.02164524421095848,
... | 0.059464 |
for this zone by adding the corresponding NS records there. Assuming the parent zone is "gcp-zalan-do" and the domain is "gcp.zalan.do" and that it's also hosted at Google we would do the following. ```console $ gcloud dns record-sets transaction start --zone=gcp-zalan-do $ gcloud dns record-sets transaction add ns-clo... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke-nginx.md | master | external-dns | [
-0.02349495328962803,
-0.03498360514640808,
-0.049028657376766205,
-0.02588968724012375,
-0.09309728443622589,
-0.07572805881500244,
0.037155356258153915,
-0.03707736358046532,
0.021543124690651894,
0.06358828395605087,
-0.026283588260412216,
-0.08856222033500671,
0.04754231125116348,
-0.0... | -0.002059 |
gcp-zalan-do $ gcloud dns record-sets transaction remove ns-cloud-e{1..4}.googledomains.com. \ --name=external-dns-test.gcp.zalan.do. --ttl 300 --type NS --zone=gcp-zalan-do $ gcloud dns record-sets transaction execute --zone=gcp-zalan-do ``` ## User Demo How-To Blogs and Examples \* Run external-dns on GKE with worklo... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke-nginx.md | master | external-dns | [
-0.09556526690721512,
0.03007342666387558,
0.03483766317367554,
-0.0348581038415432,
-0.08360922336578369,
-0.125763937830925,
0.027138810604810715,
-0.08084648102521896,
0.09280727803707123,
0.025680940598249435,
-0.033523187041282654,
-0.053356580436229706,
0.015248971059918404,
0.007546... | 0.0384 |
# AWS Route53 with same domain for public and private zones This tutorial describes how to setup ExternalDNS using the same domain for public and private Route53 zones and [nginx-ingress-controller](https://github.com/kubernetes/ingress-nginx). It also outlines how to use [cert-manager](https://github.com/jetstack/cert... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-public-private-route53.md | master | external-dns | [
-0.06199035048484802,
-0.02324567176401615,
-0.008209966123104095,
0.011008362285792828,
-0.019749954342842102,
-0.05047830566763878,
-0.002150407526642084,
-0.011719283647835255,
0.07357526570558548,
0.008643773384392262,
-0.041340526193380356,
-0.09634463489055634,
0.03711754456162453,
-... | 0.019728 |
1 selector: matchLabels: app: external-dns-private strategy: type: Recreate template: metadata: labels: app: external-dns-private spec: containers: - args: - --source=ingress - --provider=aws - --registry=txt - --txt-owner-id=dev.k8s.nexus - --ingress-class=internal-ingress - --aws-zone-type=private image: registry.k8s... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws-public-private-route53.md | master | external-dns | [
-0.05883076414465904,
0.03523201495409012,
0.011636747047305107,
-0.06863655894994736,
-0.02085660770535469,
-0.03834129497408867,
0.03055432438850403,
0.02435486391186714,
0.05164987966418266,
0.05019676685333252,
-0.02549978718161583,
-0.1137159988284111,
0.044210027903318405,
0.00262830... | 0.069204 |
# NS1 This tutorial describes how to setup ExternalDNS for use within a Kubernetes cluster using NS1 DNS. Make sure to use \*\*>=0.5\*\* version of ExternalDNS for this tutorial. ## Creating a zone with NS1 DNS If you are new to NS1, we recommend you first read the following instructions for creating a zone. [Creating ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ns1.md | master | external-dns | [
-0.024233805015683174,
-0.10778140276670456,
-0.004086249973624945,
-0.03464582562446594,
-0.10321560502052307,
-0.022214459255337715,
-0.03725677728652954,
0.010549508966505527,
0.03997785598039627,
0.037066493183374405,
-0.06350488215684891,
-0.10256411135196686,
0.016776585951447487,
0.... | 0.144032 |
external-dns spec: serviceAccountName: external-dns containers: - name: external-dns image: registry.k8s.io/external-dns/external-dns:v0.21.0 args: - --source=service # ingress is also possible - --domain-filter=example.com # (optional) limit to only example.com domains; change to match the zone created above. - --prov... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ns1.md | master | external-dns | [
-0.08281774818897247,
-0.00847453624010086,
0.010934881865978241,
-0.08929726481437683,
-0.02859044075012207,
-0.0890936404466629,
0.02022157423198223,
-0.011498954147100449,
0.055463701486587524,
0.05586909502744675,
-0.05109705775976181,
-0.06952717900276184,
-0.02441967837512493,
0.0335... | 0.071737 |
# TransIP This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using TransIP. Make sure to use \*\*>=0.5.14\*\* version of ExternalDNS for this tutorial, have at least 1 domain registered at TransIP and enabled the API. ## Enable TransIP API and prepare your API key To use the TransIP ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/transip.md | master | external-dns | [
-0.06560070067644119,
-0.07450928539037704,
-0.003623279510065913,
-0.014745152555406094,
-0.10365869849920273,
0.013088579289615154,
-0.00038431293796747923,
0.04909837618470192,
0.10813027620315552,
0.01378741767257452,
-0.010924337431788445,
-0.08487271517515182,
-0.003435970051214099,
... | 0.16038 |
Check your [TransIP Control Panel](https://transip.eu/cp) to view the records for your TransIP DNS zone. Click on the zone for the one created above if a different domain was used. This should show the external IP address of the service as the A record for your domain. | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/transip.md | master | external-dns | [
-0.03442399948835373,
-0.1029791608452797,
0.021055014804005623,
-0.0805925652384758,
-0.06355328112840652,
-0.07515131682157516,
-0.014906668104231358,
0.0034608698915690184,
0.10833633691072464,
-0.041283849626779556,
-0.019767852500081062,
0.020964154973626137,
-0.018427236005663872,
0.... | 0.015099 |
# IONOS Cloud This tutorial describes how to set up ExternalDNS for use within a Kubernetes cluster using IONOS Cloud DNS. For more details, visit the [IONOS external-dns webhook repository](https://github.com/ionos-cloud/external-dns-ionos-webhook). You can also find the [external-dns-ionos-webhook container image](ht... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ionoscloud.md | master | external-dns | [
-0.04902897775173187,
0.021769361570477486,
0.004530435428023338,
-0.028378715738654137,
-0.10133009403944016,
-0.025165759027004242,
0.00008694807911524549,
0.011838721111416817,
0.06212111562490463,
0.051187850534915924,
-0.04309816285967827,
-0.09519757330417633,
0.025218617171049118,
-... | 0.134999 |
the `echoserver` application within the cluster. The service will also include an annotation for ExternalDNS to create a DNS record for the specified hostname. Save the following content in a file named `echoserver-service.yaml`: ```yaml apiVersion: v1 kind: Service metadata: name: echoserver annotations: external-dns.... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ionoscloud.md | master | external-dns | [
-0.01432050485163927,
-0.014343447983264923,
-0.00488680973649025,
-0.06218666210770607,
-0.08312506973743439,
-0.03846200183033943,
-0.024848127737641335,
-0.033387620002031326,
0.08428654819726944,
0.05264316871762276,
-0.0466235876083374,
-0.07326941192150116,
0.0008912316407077014,
-0.... | 0.142062 |
resources created during this tutorial: ```bash kubectl delete -f echoserver-deployment.yaml kubectl delete -f echoserver-service.yaml kubectl delete -f echoserver-ingress.yaml ``` ## Summary In this tutorial, you successfully deployed ExternalDNS webhook with IONOS Cloud DNS as the provider. You created a Kubernetes d... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ionoscloud.md | master | external-dns | [
-0.06383411586284637,
0.04532095417380333,
0.014143465086817741,
-0.06870415806770325,
-0.0595862977206707,
-0.06729317456483841,
-0.002167709171772003,
-0.0506744347512722,
0.08364789932966232,
0.0381665863096714,
0.010272908955812454,
-0.065377376973629,
0.009392661042511463,
-0.03538651... | 0.145767 |
# kube-ingress-aws-controller This tutorial describes how to use ExternalDNS with the [kube-ingress-aws-controller][1]. [1]: https://github.com/zalando-incubator/kube-ingress-aws-controller ## Setting up ExternalDNS and kube-ingress-aws-controller Follow the [AWS tutorial](aws.md) to setup ExternalDNS for use in Kubern... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/kube-ingress-aws.md | master | external-dns | [
-0.05736041069030762,
-0.01387520506978035,
-0.03479532524943352,
0.005116582848131657,
-0.021441612392663956,
0.0008144849562086165,
0.046553097665309906,
-0.035516802221536636,
0.0809934064745903,
0.08086403459310532,
-0.017719093710184097,
-0.14516562223434448,
0.058831483125686646,
-0.... | 0.11862 |
no effect. If you would like ExternalDNS to not create AAAA records at all, you can add the following command line parameter: `--exclude-record-types=AAAA`. Please be aware, this will disable AAAA record creation even for dualstack enabled load balancers. Note that the above example makes use of the YAML anchor feature... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/kube-ingress-aws.md | master | external-dns | [
-0.11412157863378525,
0.023536715656518936,
0.011190022341907024,
-0.002453781431540847,
-0.08418770879507065,
-0.04861924797296524,
-0.0639176070690155,
-0.056596532464027405,
0.07339439541101456,
0.026713794097304344,
-0.013909302651882172,
-0.047373417764902115,
0.002508738311007619,
-0... | 0.073509 |
# Cloudflare DNS This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Cloudflare DNS. Make sure to use \*\*>=0.4.2\*\* version of ExternalDNS for this tutorial. ## Creating a Cloudflare DNS zone We highly recommend to read this tutorial if you haven't used Cloudflare before: [Cre... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md | master | external-dns | [
-0.016550373286008835,
-0.1167871356010437,
0.0045396569184958935,
-0.0450991615653038,
-0.08994413167238235,
0.00707201799377799,
-0.03435175493359566,
0.002460324903950095,
0.10373479127883911,
0.02748306281864643,
-0.025658555328845978,
-0.07412982732057571,
0.02605404704809189,
-0.0341... | 0.064878 |
deploy ExternalDNS. ### Using Helm Create a values.yaml file to configure ExternalDNS to use CloudFlare as the DNS provider. This file should include the necessary environment variables: ```yaml provider: name: cloudflare env: - name: CF\_API\_KEY valueFrom: secretKeyRef: name: cloudflare-api-key key: apiKey - name: CF... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md | master | external-dns | [
-0.0288663599640131,
-0.06485900282859802,
0.004547577816992998,
-0.07886958122253418,
-0.005121589172631502,
-0.020268600434064865,
-0.029782146215438843,
0.04642173647880554,
0.1316043883562088,
0.06815589964389801,
0.003827076405286789,
-0.07646965235471725,
-0.0021682654041796923,
-0.0... | 0.003281 |
image: nginx name: nginx ports: - containerPort: 80 --- apiVersion: v1 kind: Service metadata: name: nginx annotations: external-dns.kubernetes.io/hostname: example.com external-dns.kubernetes.io/ttl: "120" #optional spec: selector: app: nginx type: LoadBalancer ports: - protocol: TCP port: 80 targetPort: 80 ``` Note t... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md | master | external-dns | [
-0.060771625488996506,
-0.01180936023592949,
0.04654834046959877,
-0.11035048961639404,
-0.045479778200387955,
-0.01407872885465622,
0.008213193155825138,
-0.0501336008310318,
0.12300703674554825,
0.016928937286138535,
-0.05944334715604782,
-0.04098180681467056,
-0.02768830582499504,
0.016... | 0.044987 |
to `none`, which explicitly means no Certificate Authority (CA) is set when using the Cloudflare API. Specifying a custom CA is only possible for enterprise accounts. The custom hostname DNS must resolve to the Cloudflare DNS record (`external-dns.kubernetes.io/hostname`) for automatic certificate validation via the HT... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md | master | external-dns | [
-0.008764302358031273,
-0.05925431847572327,
-0.06812211871147156,
-0.03770243003964424,
-0.01229006890207529,
-0.0563494898378849,
-0.01344088651239872,
0.009264478459954262,
0.146107017993927,
-0.021527066826820374,
0.010494820773601532,
-0.10309086740016937,
0.06336908787488937,
0.01637... | 0.035531 |
# Myra ExternalDNS Webhook This guide provides quick instructions for setting up and testing the [Myra ExternalDNS Webhook](https://github.com/Myra-Security-GmbH/external-dns-myrasec-webhook) in a Kubernetes environment. ## Prerequisites - Kubernetes cluster (v1.19+) - `kubectl` configured to access your cluster - Dock... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/myra.md | master | external-dns | [
-0.07268770039081573,
0.005253379233181477,
-0.0486544594168663,
-0.04508887231349945,
0.013608140870928764,
-0.027791593223810196,
-0.04270098730921745,
0.0011332855792716146,
0.05990484356880188,
0.018521560356020927,
-0.0259210467338562,
-0.07970431447029114,
0.006863909773528576,
-0.03... | 0.12639 |
the webhook logs kubectl logs -l app=myra-externaldns -c myra-webhook | grep "Deleted DNS record" ``` ## Configuration Options The webhook can be configured through the ConfigMap: | Parameter | Description | Default | | ------------------------ | ------------------------------------------------- | --------- | | `disabl... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/myra.md | master | external-dns | [
-0.0446196049451828,
0.03091765008866787,
-0.03349562734365463,
-0.026189714670181274,
0.0043647149577736855,
-0.09109114110469818,
-0.04575162008404732,
-0.053308092057704926,
0.03626350313425064,
0.05320332199335098,
0.01893826760351658,
-0.11467168480157852,
-0.00918335560709238,
-0.083... | 0.11084 |
# AWS This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster on AWS. Make sure to use \*\*>=0.15.0\*\* version of ExternalDNS for this tutorial ## IAM Policy The following IAM Policy document allows ExternalDNS to update Route53 Resource Record Sets and Hosted Zones. You'll want to creat... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.043152354657649994,
-0.014956813305616379,
0.009933159686625004,
0.027010396122932434,
-0.024832919239997864,
0.002428838750347495,
-0.04102826490998268,
-0.05913063511252403,
0.0719492956995964,
0.11632555723190308,
-0.03690467029809952,
-0.07416534423828125,
0.007223552092909813,
-0.0... | 0.114186 |
to edit the `subjects[0].namespace` for the `ClusterRoleBinding` resource when deploying ExternalDNS with RBAC enabled. See [When using clusters with RBAC enabled](#when-using-clusters-with-rbac-enabled) for more information. Additionally, throughout this tutorial, the example domain of `example.com` is used. Change th... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.02024528570473194,
-0.050377149134874344,
-0.0031418446451425552,
0.04846324771642685,
-0.0681171864271164,
-0.00577270332723856,
-0.016165906563401222,
-0.03687320277094841,
0.04802943021059036,
0.08263400942087173,
-0.0694831907749176,
-0.07372631132602692,
0.046152371913194656,
-0.01... | 0.141971 |
InstanceProfiles[0].Arn --output text) # if there is an instance profile if [[ "$PROFILE\_ARN" != "None" ]]; then # get all the instances with this associated instance profile INSTANCES=$(aws ec2 describe-instances \ --filters Name=iam-instance-profile.arn,Values=$PROFILE\_ARN \ --query Reservations[\*].Instances[0].In... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
0.029253069311380386,
0.04793262109160423,
0.009899912402033806,
0.02850176766514778,
0.07609979808330536,
0.03056325763463974,
0.14038218557834625,
-0.02382642589509487,
-0.02137749083340168,
-0.035125330090522766,
0.04167420417070389,
-0.0836673304438591,
0.07127323001623154,
-0.02004954... | -0.007131 |
IAM user aws iam attach-user-policy --user-name "externaldns" --policy-arn $POLICY\_ARN ``` #### Create the static credentials ```bash SECRET\_ACCESS\_KEY=$(aws iam create-access-key --user-name "externaldns") ACCESS\_KEY\_ID=$(echo $SECRET\_ACCESS\_KEY | jq -r '.AccessKey.AccessKeyId') cat <<-EOF > credentials [defaul... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.01744936779141426,
0.04052424058318138,
-0.03565322607755661,
-0.05320558696985245,
-0.06796671450138092,
0.009789829142391682,
0.07520594447851181,
0.019784238189458847,
0.10321993380784988,
0.06990949809551239,
0.010801372118294239,
-0.11985520273447037,
0.037351131439208984,
-0.01186... | 0.055187 |
steps: 1. Create a role with a trust relationship to the cluster's OIDC provider 2. Attach the `AllowExternalDNSUpdates` policy to the role 3. Create the `external-dns` service account 4. Add annotation to the service account with the role arn ##### Use eksctl with eksctl created EKS cluster If `eksctl` was used to pro... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.08986452221870422,
-0.013058943673968315,
-0.03287142142653465,
0.029963241890072823,
-0.019546989351511,
-0.031078839674592018,
0.009073030203580856,
-0.03740144520998001,
0.09862539917230606,
0.07757684588432312,
-0.031171636655926704,
-0.11437292397022247,
0.06618265807628632,
0.0019... | 0.110427 |
created EKS cluster If `eksctl` was used to provision the EKS cluster, you can perform all of these steps with the following command: ```bash eksctl create podidentityassociation \ --cluster $EKS\_CLUSTER\_NAME \ --namespace ${EXTERNALDNS\_NS:-"default"} \ --service-account-name external-dns \ --role-name external-dns-... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.03766494616866112,
-0.004652432631701231,
0.002063443884253502,
-0.0038424592930823565,
-0.014377599582076073,
-0.0388883613049984,
0.011865423992276192,
-0.04682781919836998,
0.09105820208787918,
0.08563773334026337,
0.01992371492087841,
-0.12627990543842316,
0.017739463597536087,
0.02... | 0.158963 |
kubectl create namespace $EXTERNALDNS\_NS ``` ## Using Helm (with OIDC) Create a values.yaml file to configure ExternalDNS: ```shell provider: name: aws env: - name: AWS\_DEFAULT\_REGION value: us-east-1 # change to region where EKS is installed ``` Finally, install the ExternalDNS chart with Helm using the configurati... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.03017069399356842,
-0.04660812392830849,
0.0025142321828752756,
-0.03357870876789093,
-0.034732386469841,
-0.0036478901747614145,
-0.08218296617269516,
-0.005818254314363003,
0.1159537211060524,
0.062086500227451324,
-0.017742758616805077,
-0.08231057226657867,
-0.020750604569911957,
-0... | 0.052747 |
force external-dns to use the specified hosted zone when creating an ALIAS target. ### aws-zone-match-parent `aws-zone-match-parent` allows support subdomains within the same zone by using their parent domain, i.e --domain-filter=x.example.com would create a DNS entry for x.example.com (and subdomains thereof). ```yaml... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.08719843626022339,
-0.05002451315522194,
0.048988256603479385,
-0.06608577817678452,
-0.006270148325711489,
-0.09417484700679779,
-0.01995915174484253,
0.01630222797393799,
0.08493673801422119,
0.022196613252162933,
-0.07233870774507523,
-0.1298804134130478,
0.021836400032043457,
0.0244... | 0.029541 |
parent zone correctly you can use `curl` to access your site. ```bash curl nginx.example.com. ``` This should show something like: ```html Welcome to nginx! ... # Welcome to nginx! ... ``` ## Verify ExternalDNS works (Ingress example) With the previous `deployment` and `service` objects deployed, we can add an `ingress... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.08003341406583786,
0.0001330917584709823,
-0.01124063041061163,
-0.03617755323648453,
-0.04626009985804558,
-0.031154120340943336,
0.007242937106639147,
0.009044697508215904,
0.08036334067583084,
0.06546856462955475,
-0.05034225806593895,
-0.07872998714447021,
0.014723580330610275,
-0.0... | 0.123272 |
"20" spec: type: LoadBalancer ``` > ExternalDNS will create two Route53 weighted record sets for `app.example.com`, sending 80% of traffic to `my-service-v1` and 20% to `my-service-v2`. #### Failover Routing Designate a primary and secondary record for active/passive failover: ```yaml apiVersion: networking.k8s.io/v1 k... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.07976405322551727,
-0.0508742593228817,
0.03849073499441147,
0.05039433389902115,
-0.023238135501742363,
-0.011409679427742958,
-0.024219432845711708,
0.03585822880268097,
0.06994013488292694,
0.038217976689338684,
-0.07774142175912857,
-0.07203201204538345,
0.03225927799940109,
-0.0475... | 0.140132 |
## Clean up Make sure to delete all Service objects before terminating the cluster so all load balancers get cleaned up correctly. ```bash kubectl delete service nginx ``` \*\*IMPORTANT\*\* If you attached a policy to the Node IAM Role, then you will want to detach this before deleting the EKS cluster. Otherwise, the r... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.046523887664079666,
0.04803687334060669,
0.005378768779337406,
0.004754736088216305,
0.008436430245637894,
-0.03961624577641487,
-0.0037743474822491407,
-0.11367301642894745,
0.06955645233392715,
0.08981220424175262,
-0.014165231958031654,
-0.0630304142832756,
0.046169500797986984,
-0.0... | 0.142587 |
they do not make their requests on the same second. A simple way to implement randomised startup is with an init container: ```yaml ... spec: initContainers: - name: init-jitter image: registry.k8s.io/external-dns/external-dns:v0.21.0 command: - /bin/sh - -c - 'FOR=$((RANDOM % 10))s;echo "Sleeping for $FOR";sleep $FOR'... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md | master | external-dns | [
-0.1140441745519638,
0.019843807443976402,
0.03613009303808212,
0.0540706031024456,
-0.027526356279850006,
-0.0730532631278038,
0.02399761788547039,
-0.04053656756877899,
0.13422837853431702,
0.045308493077754974,
-0.032550275325775146,
-0.015425074845552444,
0.010956832207739353,
-0.08349... | 0.136161 |
# RFC2136 provider This tutorial describes how to use the RFC2136 with either BIND or Windows DNS. ## Deploying BIND9 on Kubernetes with Kind This section walks through deploying BIND9 and ExternalDNS inside a local Kubernetes cluster using [Kind](https://kind.sigs.k8s.io/). It provides a self-contained lab environment... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md | master | external-dns | [
-0.0645352452993393,
-0.026052381843328476,
0.05469303950667381,
-0.023781877011060715,
-0.11594680696725845,
0.017540110275149345,
-0.04208465293049812,
0.03985193744301796,
0.03310094401240349,
0.026308268308639526,
-0.05182640999555588,
-0.052883509546518326,
-0.02235753834247589,
-0.04... | 0.118567 |
Verify DNS records Query the forward zone for A records: ```sh dig @127.0.0.1 -p 5354 +tcp app.example.local A +short ❯❯ 192.168.49.10 dig @127.0.0.1 -p 5354 +tcp api.example.local A +short ❯❯ 192.168.49.20 dig @127.0.0.1 -p 5354 +tcp svc.example.local A +short ❯❯ 192.168.49.50 ``` Query the reverse zone for PTR record... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md | master | external-dns | [
-0.05173759534955025,
0.03403256833553314,
0.033356085419654846,
-0.05309449881315231,
-0.015434975735843182,
-0.07937350124120712,
-0.02042889967560768,
-0.01354944333434105,
0.006471527740359306,
0.09490235149860382,
0.003998676780611277,
-0.036949239671230316,
-0.02563568390905857,
-0.0... | 0.004563 |
AXFR and the sync policy When using the `sync` policy, ExternalDNS requires AXFR (zone transfer) to be explicitly enabled via the `--rfc2136-tsig-axfr` flag. This is necessary for ExternalDNS to list all existing DNS records and determine which ones should be lifecycled. Without `--rfc2136-tsig-axfr`, ExternalDNS canno... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md | master | external-dns | [
-0.1339477002620697,
-0.07882724702358246,
-0.002088242908939719,
-0.032006412744522095,
0.024990351870656013,
-0.06975502520799637,
-0.017636273056268692,
-0.07271359860897064,
0.060007818043231964,
0.04613202065229416,
-0.027737030759453773,
-0.0472380667924881,
-0.007507708389312029,
-0... | 0.078821 |
apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: external-dns subjects: - kind: ServiceAccount name: external-dns namespace: external-dns --- apiVersion: apps/v1 kind: Deployment metadata: name: external-dns namespace: external-dns spec: selector: matchLabels: app: external-dns template: metadata: labels: ap... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md | master | external-dns | [
-0.05602233484387398,
-0.02810659445822239,
-0.03573589771986008,
-0.016167495399713516,
-0.05152135342359543,
-0.037523962557315826,
-0.034708403050899506,
-0.017311790958046913,
0.034718528389930725,
0.04389467090368271,
-0.02681851200759411,
-0.062236983329057693,
0.01044224388897419,
0... | 0.112854 |
to the host's domain name or IP address. However, it also determines the name of the Kerberos principal which is used during authentication. This means that Active Directory might only work if this is set to a specific domain name, possibly leading to errors like this: `KDC\_ERR\_S\_PRINCIPAL\_UNKNOWN Server not found ... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md | master | external-dns | [
0.006632522214204073,
-0.056922245770692825,
-0.059919893741607666,
-0.05077939108014107,
-0.06066375970840454,
-0.06778500974178314,
-0.033409636467695236,
-0.023369427770376205,
0.008600790053606033,
0.11460448056459427,
-0.03632932901382446,
-0.07987236231565475,
0.04595771059393883,
0.... | -0.042063 |
# Civo DNS This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Civo DNS Manager. Make sure to use \*\*>0.13.5\*\* version of ExternalDNS for this tutorial. ## Managing DNS with Civo If you want to learn about how to use Civo DNS Manager read the following tutorials: [An Introduc... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/civo.md | master | external-dns | [
-0.06795655936002731,
-0.0811602920293808,
0.009000957012176514,
-0.04085438326001167,
-0.15125524997711182,
-0.009585508145391941,
-0.06926655024290085,
0.06590970605611801,
0.08163672685623169,
0.035509977489709854,
-0.05085911601781845,
-0.12378723919391632,
-0.0060220449231565,
-0.0338... | 0.156169 |
can delete the tutorial's example: ```sh kubectl delete service -f nginx.yaml kubectl delete service -f externaldns.yaml ``` | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/civo.md | master | external-dns | [
-0.07472976297140121,
0.010448737069964409,
0.009906075894832611,
-0.0749872624874115,
-0.0005186315975151956,
-0.030191974714398384,
-0.04107847809791565,
-0.08368413895368576,
0.08259883522987366,
0.026878926903009415,
0.011446680873632431,
-0.012670999392867088,
-0.02300228737294674,
-0... | 0.096051 |
# OVHcloud This tutorial describes how to setup ExternalDNS for use within a Kubernetes cluster using OVHcloud DNS. Make sure to use \*\*>=0.6\*\* version of ExternalDNS for this tutorial. ## Creating a zone with OVHcloud DNS If you are new to OVHcloud, we recommend you first read the following instructions for creatin... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ovh.md | master | external-dns | [
-0.030982472002506256,
-0.04367360100150108,
-0.008549627847969532,
0.019359789788722992,
-0.06980907171964645,
-0.017291568219661713,
-0.048953402787446976,
0.01849295012652874,
0.10468719154596329,
-0.03365733474493027,
-0.0295877568423748,
-0.10823462158441544,
-0.025705037638545036,
-0... | 0.036666 |
external-dns.kubernetes.io/hostname: example.com external-dns.kubernetes.io/ttl: "120" #optional spec: selector: app: nginx type: LoadBalancer ports: - protocol: TCP port: 80 targetPort: 80 ``` \*\*A note about annotations\*\* Verify that the annotation on the service uses the same hostname as the OVHcloud DNS zone cre... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/ovh.md | master | external-dns | [
-0.08560657501220703,
0.020131828263401985,
0.0377560518682003,
-0.07881529629230499,
-0.07968711853027344,
-0.05559154972434044,
-0.03136391192674637,
-0.017893318086862564,
0.16341057419776917,
-0.035319551825523376,
-0.048498060554265976,
-0.05510181188583374,
-0.028294987976551056,
-0.... | 0.114445 |
# CoreDNS with etcd backend ## Overview This tutorial describes how to deploy CoreDNS backed by etcd as a dynamic DNS provider for external-dns. It shows how to configure external-dns to write DNS records into etcd, which CoreDNS will then serve. ### TL;DR After completing this lab, you will have a Kubernetes environme... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns-etcd.md | master | external-dns | [
-0.04215347766876221,
0.003607065649703145,
0.05541224032640457,
-0.06668926775455475,
-0.09104957431554794,
0.0015294599579647183,
-0.0863996148109436,
-0.014144591987133026,
0.05168167129158974,
0.012205898761749268,
-0.04227776080369949,
-0.06499559432268143,
0.011178995482623577,
-0.03... | 0.039008 |
-n default ❯❯ Release "external-dns" does not exist. Installing it now. ``` Validate pod status and view logs ```sh kubectl get pods -l app.kubernetes.io/name=external-dns kubectl logs deploy/external-dns ``` Or run it on the host from sources ```sh export ETCD\_URLS="http://127.0.0.1:32379" # port mapping configured o... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns-etcd.md | master | external-dns | [
-0.01690567098557949,
-0.0233599916100502,
0.02263478934764862,
-0.042447663843631744,
-0.0389777235686779,
-0.004916059318929911,
-0.0885888934135437,
-0.0028425822965800762,
0.08113294094800949,
0.055051110684871674,
-0.0204493198543787,
-0.06570375710725784,
-0.09206528961658478,
0.0158... | 0.11953 |
# Azure Private DNS This tutorial describes how to set up ExternalDNS for managing records in Azure Private DNS. It comprises of the following steps: 1) Provision Azure Private DNS 2) Configure service principal for managing the zone 3) Deploy ExternalDNS 4) Expose an NGINX service with a LoadBalancer and annotate it w... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure-private-dns.md | master | external-dns | [
-0.10079936683177948,
-0.030812367796897888,
0.022517533972859383,
-0.0240409467369318,
-0.07589550316333771,
0.012337319552898407,
0.00017511491023469716,
-0.07913696765899658,
0.1045999750494957,
0.09397765249013901,
-0.025304866954684258,
-0.05768571421504021,
0.04164924845099449,
0.015... | 0.060919 |
with a value of 0s. Also, one can leverage the built-in retry policies of the Azure SDK. The flag --azure-maxretries-count can be specified in the manifest yaml to configure behavior. The default value of Azure SDK retry is 3. ## Deploy ExternalDNS Configure `kubectl` to be able to communicate and authenticate with you... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure-private-dns.md | master | external-dns | [
-0.03745012730360031,
0.009315445087850094,
0.0014520365511998534,
0.04620395973324776,
-0.08839721232652664,
0.034494027495384216,
0.02901601977646351,
-0.09002187103033066,
0.10225003957748413,
0.11588624864816666,
-0.04374024271965027,
-0.02997840754687786,
0.06874745339155197,
0.005495... | 0.087888 |
kubectl create -f externaldns.yaml ``` ## Create an nginx deployment This step creates a demo workload in your cluster. Apply the following manifest to create a deployment that we are going to expose later in this tutorial in multiple ways: ```yaml --- apiVersion: apps/v1 kind: Deployment metadata: name: nginx spec: se... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure-private-dns.md | master | external-dns | [
-0.03684442862868309,
-0.020910104736685753,
-0.011333873495459557,
-0.0025129017885774374,
-0.08563555777072906,
-0.001000711228698492,
-0.03029540739953518,
-0.0324261449277401,
0.06365980207920074,
0.09396465867757797,
-0.052442532032728195,
-0.08246002346277237,
0.004752141423523426,
-... | 0.121274 |
use `--domain-filter` together with `--zone-name-filter`, the behavior changes: `--domain-filter` then filters Ingress domains, not the Azure Private DNS zone name. When those hostnames are removed or renamed the corresponding DNS records are also altered. Create the deployment, service and ingress object: ```sh kubect... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure-private-dns.md | master | external-dns | [
-0.0575370118021965,
0.006506786681711674,
0.0367518775165081,
-0.020247681066393852,
-0.057003919035196304,
-0.05645480751991272,
0.031530123203992844,
-0.09831695258617401,
0.10134901851415634,
0.09996403753757477,
-0.03705984354019165,
-0.048906922340393066,
0.06466114521026611,
0.02963... | 0.010068 |
# Scaleway This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Scaleway DNS. Make sure to use \*\*>=0.7.4\*\* version of ExternalDNS for this tutorial. \*\*Warning\*\*: Scaleway DNS is currently in Public Beta and may not be suited for production usage. ## Importing a Domain int... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/scaleway.md | master | external-dns | [
-0.023999473080039024,
-0.08356863260269165,
0.007268446031957865,
-0.031202418729662895,
-0.10656353086233139,
-0.025395970791578293,
-0.07765030860900879,
0.042937520891427994,
0.04652418568730354,
0.01765384152531624,
-0.06334931403398514,
-0.08761019259691238,
0.019919509068131447,
0.0... | 0.075484 |
- --source=service # ingress is also possible - --domain-filter=example.com # (optional) limit to only example.com domains; change to match the zone created above. - --provider=scaleway env: - name: SCW\_ACCESS\_KEY value: "" - name: SCW\_SECRET\_KEY value: "" ### Set if configuring using a config file. Make sure to cr... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/scaleway.md | master | external-dns | [
-0.03007383458316326,
-0.021049566566944122,
-0.061540063470602036,
-0.024564972147345543,
0.018869472667574883,
-0.028256766498088837,
-0.026987221091985703,
-0.04701756685972214,
-0.022565217688679695,
0.05644349381327629,
-0.030968843027949333,
-0.06343904882669449,
0.037330519407987595,
... | -0.01208 |
# Linode This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Linode DNS Manager. Make sure to use \*\*>=0.5.5\*\* version of ExternalDNS for this tutorial. ## Managing DNS with Linode If you want to learn about how to use Linode DNS Manager read the following tutorials: [An Intr... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/linode.md | master | external-dns | [
-0.062344811856746674,
-0.05921038240194321,
0.035840243101119995,
-0.05629558488726616,
-0.06517287343740463,
-0.004363169427961111,
-0.03850186988711357,
0.027565669268369675,
0.08265931904315948,
0.01502007432281971,
-0.039708059281110764,
-0.08427821099758148,
-0.0003536632575560361,
-... | 0.112004 |
Linode DNS records, we can delete the tutorial's example: ```sh kubectl delete service -f nginx.yaml kubectl delete service -f externaldns.yaml ``` | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/linode.md | master | external-dns | [
-0.10981239378452301,
-0.0030336950439959764,
0.03173080086708069,
-0.09025678038597107,
0.0019438614835962653,
-0.03844249248504639,
-0.04712555557489395,
-0.10664597898721695,
0.07982655614614487,
0.02778616175055504,
0.0039812372997403145,
-0.005824644584208727,
-0.03698119521141052,
-0... | 0.092667 |
# PowerDNS ## Prerequisites The provider has been written for and tested against [PowerDNS](https://github.com/PowerDNS/pdns) v4.1.x and thus requires \*\*PowerDNS Auth Server >= 4.1.x\*\* PowerDNS provider support was added via [this PR](https://github.com/kubernetes-sigs/external-dns/pull/373), thus you need to use e... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/pdns.md | master | external-dns | [
-0.06352634727954865,
-0.03190551698207855,
0.05377955362200737,
-0.04650268331170082,
-0.08451028168201447,
-0.020052853971719742,
-0.0585491880774498,
-0.03429066017270088,
0.0798368826508522,
0.04071233049035072,
-0.006037023384124041,
-0.07508465647697449,
-0.02597387507557869,
-0.0165... | -0.006416 |
``` \*\*Important!\*\*: Don't run dig, nslookup or similar immediately (until you've confirmed the record exists). You'll get hit by [negative DNS caching](https://tools.ietf.org/html/rfc2308), which is hard to flush. Run the following to make sure everything is in order: ```bash kubectl get services echo kubectl get e... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/pdns.md | master | external-dns | [
-0.002328828675672412,
0.010060195811092854,
0.025257831439375877,
-0.06263880431652069,
-0.06011297553777695,
-0.07349161058664322,
-0.08773337304592133,
-0.0849515050649643,
0.10286544263362885,
0.038696158677339554,
-0.04019862040877342,
-0.062294382601976395,
-0.04630899056792259,
-0.0... | 0.077984 |
# Gandi This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using Gandi. Make sure to use \*\*>=0.7.7\*\* version of ExternalDNS for this tutorial. ## Creating a Gandi DNS zone (domain) Create a new DNS zone where you want to create your records in. Let's use `example.com` as an examp... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gandi.md | master | external-dns | [
-0.07478202879428864,
-0.11773049086332321,
-0.030679713934659958,
-0.02620704658329487,
-0.11123286187648773,
-0.031120702624320984,
-0.07062304764986038,
0.0244299229234457,
0.05519678816199303,
-0.007357679773122072,
-0.01678280346095562,
-0.11034968495368958,
0.0037644205149263144,
-0.... | 0.11112 |
created above if a different domain was used. This should show the external IP address of the service as the A record for your domain. ## Cleanup Now that we have verified that ExternalDNS will automatically manage Gandi DNS records, we can delete the tutorial's example: ```sh kubectl delete service -f nginx.yaml kubec... | https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gandi.md | master | external-dns | [
-0.11324077099561691,
-0.03465957194566727,
-0.025782793760299683,
-0.08012537658214569,
-0.04022650420665741,
-0.04992954432964325,
-0.046221498399972916,
-0.05784178525209427,
0.053153738379478455,
-0.028093399479985237,
-0.03509141877293587,
-0.04422386363148689,
-0.009810234420001507,
... | 0.063841 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.