-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: support FQDN in upstream #2080
Comments
Hi, @liuxiran. |
I think at the same time we can give it a default value of port 80. XD |
Hi @foolwc , do you have time to take this issue? |
I'm willing to take. Just make the |
The upstream JSON schema shows that
|
nodes: {
"anyOf": [{
"patternProperties": {
".*": {
"description": "weight of node",
"minimum": 0,
"type": "integer"
}
},
"type": "object"
}, {
"items": {
"properties": {
"host": {
"pattern": "^\\*?[0-9a-zA-Z-._]+$",
"type": "string"
},
"metadata": {
"description": "metadata of node",
"type": "object"
},
"port": {
"description": "port of node",
"minimum": 1,
"type": "integer"
},
"priority": {
"default": 0,
"description": "priority of node",
"type": "integer"
},
"weight": {
"description": "weight of node",
"minimum": 0,
"type": "integer"
}
},
"required": ["host", "port", "weight"],
"type": "object"
},
"type": "array"
}]
} Hi @foolwc here is our upstream nodes schema, you can see that we support two type of nodes:
{
${host1}: ${weight1},
${host2}: ${weight2},
...
} |
There is a case: if we add two hosts, one is FQDN without port, the other is normal IP with port. How to deal with that, saved with Array or Object just like below ? Thanks for your explanation @liuxiran {
"httpbin.default.svc.cluster.local": 1
"httpbin2.default.svc.cluster.local:8080": 1
} |
Object is good for me, @tzssangglass @nic-chen for double check , thanks |
Hi @foolwc please use object as the data struct, no matter enter {
`${IP/host}${: port?}`: ${weight}
} any question please comment here, thanks |
LGTM |
LGTM |
LGTM. |
Hi @foolwc , do you still have any questions on this issue? or anything else I can do to help? |
No question, thanks. It's ok to assign to others if this feature is urgent or someone else can do :) I don't have much time on weekdays and maybe delay your work |
Thanks very much for your information, since it is one of our milestone task, and tomorrow is the deadline, I 'll assign to others, we have other issues you can try the one you want to, thanks again to drive this issue needs to be clear |
Feature request
Please describe your feature
Currently we can only configure upstream nodes in UI by
Address + (required) Port
, but in fact APISIX also support FQDN, see https://apisix.apache.org/docs/apisix/2.7/FAQ/#does-the-upstream-node-support-configuring-the-fqdn-address, we should update our UI to fit this option.Describe the solution you'd like
We can update our input constraints, make port an optional input, and at the same time we can also consider whether to change
host
to the suitable name.The text was updated successfully, but these errors were encountered: