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 attempting to create an HTTP trigger (route) with the same name and URL in a different namespace using the Fission CLI, an error is encountered stating that a route with the same host, URL, and method already exists. This suggests that the uniqueness check is not considering the namespace, which should allow for the same route names to be used in different namespaces.
To Reproduce
Create a function and a route in the default namespace:
fission function create --name myfunction --env nodejs --code hello.js
fission route create --name myroute --function myfunction --url /myfunction --method GET
Create another function with the same name in a different namespace (mynamespace):
Error: Error while creating HTTP Trigger: HTTPTrigger with same Host, URL & method already exists (hello)
Expected result
Routes with the same name and URL should be creatable in different namespaces without conflict, following Kubernetes' namespace isolation principles.
Actual result
The attempt to create a route with the same name in a different namespace results in the following error message:
Error: Error while creating HTTP Trigger: HTTPTrigger with same Host, URL & method already exists (hello)
This issue hinders the management of multi-tenant environments within a Kubernetes cluster, where namespace isolation is critical for different tenants to use the same function names and routes.
The text was updated successfully, but these errors were encountered:
@thoma01
Creating routes with same name across different namespaces are allowed. However, creating routes with same URL across different namespaces are not supported.
Fission/Kubernetes version
$ fission version client: fission/core: BuildDate: "2023-11-30T15:47:54Z" GitCommit: 9b57f1f Version: v1.20.0 server: fission/core: BuildDate: "2023-11-30T15:47:54Z" GitCommit: 9b57f1f Version: v1.20.0 $ kubectl version Client Version: v1.28.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.27.4
Kubernetes platform (e.g. Google Kubernetes Engine)
minikube version: v1.31.2
commit: fd7ecd9c4599bef9f04c0986c4a0187f98a4396e
Describe the bug
When attempting to create an HTTP trigger (route) with the same name and URL in a different namespace using the Fission CLI, an error is encountered stating that a route with the same host, URL, and method already exists. This suggests that the uniqueness check is not considering the namespace, which should allow for the same route names to be used in different namespaces.
To Reproduce
mynamespace
):mynamespace
:Expected result
Routes with the same name and URL should be creatable in different namespaces without conflict, following Kubernetes' namespace isolation principles.
Actual result
The attempt to create a route with the same name in a different namespace results in the following error message:
Error: Error while creating HTTP Trigger: HTTPTrigger with same Host, URL & method already exists (hello)
This issue hinders the management of multi-tenant environments within a Kubernetes cluster, where namespace isolation is critical for different tenants to use the same function names and routes.
The text was updated successfully, but these errors were encountered: