You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i try to add same backend (with same name - hostname) i have got
{
"error": "specified object already exists"
}
For example, i'm trying to have one host/backend in multiple services for http 80 and https 443. So hostname/backend the same, but i must "create" for the same host/backend different "name" ...
The global uniqueness of backend name is not necessary - if i look at this from "perspective", or am i missing something..?
As workaround i'm creating backend name as hostname_portnumber, which is also "Bad" because one hostname with same port should be member of multiple services.. so as actual workaround of this i must creating backend name like servicename_hostname_port - it is ugly...
The text was updated successfully, but these errors were encountered:
Since services and backends are maintained as two separate maps, trying to create a new backend with the same particulars as the existing one would fail yeah. I think the right approach here would be to allow backends to be a part of multiple services, what do you think?
When i try to add same backend (with same name - hostname) i have got
For example, i'm trying to have one host/backend in multiple services for http 80 and https 443. So hostname/backend the same, but i must "create" for the same host/backend different "name" ...
The global uniqueness of backend name is not necessary - if i look at this from "perspective", or am i missing something..?
As workaround i'm creating backend name as hostname_portnumber, which is also "Bad" because one hostname with same port should be member of multiple services.. so as actual workaround of this i must creating backend name like servicename_hostname_port - it is ugly...
The text was updated successfully, but these errors were encountered: