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
Port forwarding on port 8092: kubectl port-forward service/egeria-presentation 8092:8091
Then accessed the UI from local Chrome browser: https://localhost:8092/org/
The UI was accessible, but there's this popup saying localhost 8092 says: Could not get servers (status : 404). OMAG-MULTI-TENANT-404-001 The OMAG Server view1 is not available to service a request from user garygeeke. System detail: The system is unable to process the request because the server is not running on the called platform.
Expected Behavior
Was hoping to have a smooth deployment with a functioning OMAG server.
To debug, I checked the running servers on the Platform: kubectl port-forward svc/egeria-platform 9443:9443
Response of above command: { "timestamp":"2024-10-08T05:52:36.680+00:00", "status":404, "error":"Not Found", "path":"/open-metadata/admin-services/users/garygeeke/servers/view1/start" }
Looks like the view1 server is not setup at all.
eashanroy7
changed the title
[BUG] <I installed the Egeria base chart with default values.yaml in a private GKE cluster with Cloud NAT for outbound Internet connectivity. On getting deployed, I can access the UI on localhost by port forwarding, but there's this popup saying 'localhost 8092 says: Could not get servers (status : 404). OMAG-MULTI-TENANT-404-001 The OMAG Server view1 is not available to service a request from user garygeeke. System detail: The system is unable to process the request because the server is not running on the called platform.'>
[BUG] <Egeria base chart installed with default values.yaml in a private GKE cluster with Cloud NAT for outbound Internet connectivity. UI can be accessed on localhost by port forwarding, but there's this popup saying 'localhost 8092 says: Could not get servers (status : 404). OMAG-MULTI-TENANT-404-001 The OMAG Server view1 is not available to service a request from user garygeeke. System detail: The system is unable to process the request because the server is not running on the called platform.'>
Oct 8, 2024
But this gives me Image Pull Back Off errors for the pods, so I guess there is some compatibility issues with egeria 5.1 and docker images with tag 'latest'?
Oh thank you @mandy-chessell for letting me know that.
Is there any recommended way for deploying Egeria in production?
eashanroy7
changed the title
[BUG] <Egeria base chart installed with default values.yaml in a private GKE cluster with Cloud NAT for outbound Internet connectivity. UI can be accessed on localhost by port forwarding, but there's this popup saying 'localhost 8092 says: Could not get servers (status : 404). OMAG-MULTI-TENANT-404-001 The OMAG Server view1 is not available to service a request from user garygeeke. System detail: The system is unable to process the request because the server is not running on the called platform.'>
[BUG] <OMAG Server Not Available in Egeria UI on Private GKE with Default Chart Deployment (404 Error)>
Oct 8, 2024
Existing/related issue?
No response
Current Behavior
Used the documentation guide, and executed the following commands inside the private GKE cluster:
After deployment:
kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
egeria-platform ClusterIP 34.118.228.176 9443/TCP 142m
egeria-presentation ClusterIP 34.118.239.161 8091/TCP 142m
egeria-strimzi-kafka-0 NodePort 34.118.230.154 9094:31268/TCP 141m
egeria-strimzi-kafka-bootstrap ClusterIP 34.118.230.254 9091/TCP,9092/TCP 141m
egeria-strimzi-kafka-brokers ClusterIP None 9090/TCP,9091/TCP,8443/TCP,9092/TCP 141m
egeria-strimzi-kafka-external-bootstrap NodePort 34.118.229.108 9094:32000/TCP 141m
egeria-strimzi-zookeeper-client ClusterIP 34.118.230.54 2181/TCP 142m
egeria-strimzi-zookeeper-nodes ClusterIP None 2181/TCP,2888/TCP,3888/TCP 142m
kubernetes ClusterIP 34.118.224.1 443/TCP 163m
kubectl get pods
NAME READY STATUS RESTARTS AGE
egeria-autostart-f9mhc 0/1 Completed 0 86m
egeria-base-platform-0 1/1 Running 0 86m
egeria-base-presentation-79f574749c-zjtpb 1/1 Running 0 86m
egeria-config-p27wd 0/1 Completed 0 86m
egeria-strimzi-entity-operator-68c5bfd9df-t9pgm 3/3 Running 0 84m
egeria-strimzi-kafka-0 1/1 Running 0 84m
egeria-strimzi-zookeeper-0 1/1 Running 0 85m
strimzi-cluster-operator-b98874885-7qcxk 1/1 Running 0 86m
Port forwarding on port 8092:
kubectl port-forward service/egeria-presentation 8092:8091
Then accessed the UI from local Chrome browser:
https://localhost:8092/org/
The UI was accessible, but there's this popup saying localhost 8092 says: Could not get servers (status : 404). OMAG-MULTI-TENANT-404-001 The OMAG Server view1 is not available to service a request from user garygeeke. System detail: The system is unable to process the request because the server is not running on the called platform.
Expected Behavior
Was hoping to have a smooth deployment with a functioning OMAG server.
To debug, I checked the running servers on the Platform:
kubectl port-forward svc/egeria-platform 9443:9443
Response of above command:
{ "timestamp":"2024-10-08T05:52:36.680+00:00", "status":404, "error":"Not Found", "path":"/open-metadata/admin-services/users/garygeeke/servers/view1/start" }
Looks like the view1 server is not setup at all.
Steps To Reproduce
No response
Environment
Any Further Information?
https://egeria-project.org/guides/operations/kubernetes/charts/base/
The text was updated successfully, but these errors were encountered: