design-proposal: dns probe name customize #1281
Conversation
kubevirt-bot
added
the
release-note-none
kubevirt-bot
added
dco-signoff: yes
|
|
||
| Support customize kubernetes-nmstate DNS resolving probes at NMState CR. | ||
|
|
||
| ## Motivation |
There was a problem hiding this comment.
Please also list the alternatives in this document. e.g. making the probe smarter, and having this configured on NNCP-level
There was a problem hiding this comment.
I will add an alternative about probe doing fallaback to a global name, about NNCP is stated as non goal and if needed can be done a new enhancement, we want this one to be very specific to reduce the number of knobs that we really need.
At some users customizing globally the dns probe name to resolve is a must, this change add a design doc to do it at NMState CR. Signed-off-by: Enrique Llorente <[email protected]>
qinqon
force-pushed
the
design-proposal-customize-dns-probe-name
branch
from
e5d0d5e to
b19a3ed
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@qinqon: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What this PR does / why we need it:
At some users customizing globally the dns probe name to resolve is a must, this change add a design doc to do it at NMState CR.
Related but for default gw:
Release note: