Open shadab109 opened 4 months ago
Hi there, appreciate an update please.
Hi there, appreciate an update please.
@shadab109 It seems to be a problem with how the Docker
image is created. Comparing the build version vs the Docker one I get the following result. As you can see in the build version (red) there is the flag, but in the Docker one (green) there isn't.
Also, there seems to be [EXPERIMENTAL] options so maybe there is a Docker image that contains these ones...
178,184c178,182
< ibmcloud, inmemory, linode, ns1, oci, ovh,
< pdns, pihole, plural, rcodezero, rdns, rfc2136,
< safedns, scaleway, skydns, tencentcloud,
< transip, ultradns, vinyldns, vultr, webhook)
< ($EXTERNAL_DNS_PROVIDER)
< --provider-cache-time=0s The time to cache the DNS provider record list
< requests. ($EXTERNAL_DNS_PROVIDER_CACHE_TIME)
---
> ibmcloud, infoblox, inmemory, linode, ns1,
> oci, ovh, pdns, pihole, plural, rcodezero,
> rdns, rfc2136, safedns, scaleway, skydns,
> tencentcloud, transip, ultradns, vinyldns,
> vultr, webhook) ($EXTERNAL_DNS_PROVIDER)
234,235d231
< --aws-profile= ... When using the AWS provider, name of the
< profile to use ($EXTERNAL_DNS_AWS_PROFILE)
385a382,424
> --infoblox-grid-host="" When using the Infoblox provider,
> specify the Grid Manager host
> (required when --provider=infoblox)
> ($EXTERNAL_DNS_INFOBLOX_GRID_HOST)
> --infoblox-wapi-port=443 When using the Infoblox provider,
> specify the WAPI port (default: 443)
> ($EXTERNAL_DNS_INFOBLOX_WAPI_PORT)
> --infoblox-wapi-username="admin"
> When using the Infoblox provider,
> specify the WAPI username (default: admin)
> ($EXTERNAL_DNS_INFOBLOX_WAPI_USERNAME)
> --infoblox-wapi-password="" When using the Infoblox provider,
> specify the WAPI password (required
> when --provider=infoblox)
> ($EXTERNAL_DNS_INFOBLOX_WAPI_PASSWORD)
> --infoblox-wapi-version="2.3.1"
> When using the Infoblox provider,
> specify the WAPI version (default: 2.3.1)
> ($EXTERNAL_DNS_INFOBLOX_WAPI_VERSION)
> --[no-]infoblox-ssl-verify When using the Infoblox provider, specify
> whether to verify the SSL certificate (default:
> true, disable with --no-infoblox-ssl-verify)
> ($EXTERNAL_DNS_INFOBLOX_SSL_VERIFY)
> --infoblox-view="" DNS view (default: "")
> ($EXTERNAL_DNS_INFOBLOX_VIEW)
> --infoblox-max-results=0 Add _max_results as query parameter to
> the URL on all API requests. The default
> is 0 which means _max_results is not set
> and the default of the server is used.
> ($EXTERNAL_DNS_INFOBLOX_MAX_RESULTS)
> --infoblox-fqdn-regex="" Apply this regular expression as a filter for
> obtaining zone_auth objects. This is disabled
> by default. ($EXTERNAL_DNS_INFOBLOX_FQDN_REGEX)
> --infoblox-name-regex="" Apply this regular expression as a filter
> on the name field for obtaining infoblox
> records. This is disabled by default.
> ($EXTERNAL_DNS_INFOBLOX_NAME_REGEX)
> --[no-]infoblox-create-ptr When using the Infoblox provider,
> create a ptr entry in addition to an entry
> ($EXTERNAL_DNS_INFOBLOX_CREATE_PTR)
> --infoblox-cache-duration=0 When using the Infoblox provider,
> set the record TTL (0s to disable).
> ($EXTERNAL_DNS_INFOBLOX_CACHE_DURATION)
518,519d556
< --[no-]rfc2136-create-ptr When using the RFC2136 provider, enable PTR
< management ($EXTERNAL_DNS_RFC2136_CREATE_PTR)
676,677c713,714
< The URL of the remote endpoint
< to call for the webhook provider
---
> [EXPERIMENTAL] The URL of the remote
> endpoint to call for the webhook provider
681c718
< The read timeout for the webhook
---
> [EXPERIMENTAL] The read timeout for the webhook
685,686c722,724
< The write timeout for the webhook
< provider in duration format (default: 10s)
---
> [EXPERIMENTAL] The write timeout
> for the webhook provider in
> duration format (default: 10s)
688,690c726,728
< --[no-]webhook-server When enabled, runs as a webhook server
< instead of a controller. (default: false).
< ($EXTERNAL_DNS_WEBHOOK_SERVER)
---
> --[no-]webhook-server [EXPERIMENTAL] When enabled, runs as a webhook
> server instead of a controller. (default:
> false). ($EXTERNAL_DNS_WEBHOOK_SERVER)
Hi thanks for the reply. Believe we need to wait for the next release then? Any idea when is it going to be the next release? OR would be nice to have the instruction on how to build it ourselves if we don't wish to wait for next release.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
What happened: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md#generate-reverse-dns-records
We are trying to generate reverse dns using this and passing "--rfc2136-create-ptr " flag as an argument, however, we are receiving the below error:
"time="**" level=fatal msg="flag parsing error: unknown long flag '--rfc2136-create-ptr'""
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
external-dns --version
): external-dns:v0.14.2