Closed arjunkrishnasb closed 3 years ago
marcogschmidt
commented
3 years ago Hi @arjunkrishnasb, I moved the issue to this repository, since this is where we track issues that are specific to Gloo Portal.
This message in the logs jumped out at me:
got runtime.Object without object metadata
Could you share the YAML for your portal (kubectl get portals -A -oyaml)?
arjunkrishnasb
commented
3 years ago Hi @marcogschmidt , Apologies for the delayed reply. Here you go.
(base) ARJSRIRA-M-L0XP:~ arjsrira$ kubectl get portals -A -oyaml
apiVersion: v1
items:
- apiVersion: devportal.solo.io/v1alpha1
kind: Portal
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"devportal.solo.io/v1alpha1","kind":"Portal","metadata":{"annotations":{},"name":"petstore-portal","namespace":"default"},"spec":{"banner":{"fetchUrl":"https://i.imgur.com/EXbBN1a.jpg"},"customStyling":{},"description":"The Gloo Portal for the Petstore API","displayName":"Petstore Portal","domains":["portal.petstore.com:30001"],"favicon":{"fetchUrl":"https://i.imgur.com/QQwlQG3.png"},"primaryLogo":{"fetchUrl":"https://i.imgur.com/hjgPMNP.png"},"publishedEnvironments":[{"name":"dev","namespace":"default"}],"staticPages":[]}}
creationTimestamp: "2021-05-26T05:25:10Z"
generation: 1
managedFields:
- apiVersion: devportal.solo.io/v1alpha1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:kubectl.kubernetes.io/last-applied-configuration: {}
f:spec:
.: {}
f:banner:
.: {}
f:fetchUrl: {}
f:customStyling: {}
f:description: {}
f:displayName: {}
f:domains: {}
f:favicon:
.: {}
f:fetchUrl: {}
f:primaryLogo:
.: {}
f:fetchUrl: {}
f:publishedEnvironments: {}
manager: kubectl
operation: Update
time: "2021-05-26T05:25:10Z"
- apiVersion: devportal.solo.io/v1alpha1
fieldsType: FieldsV1
fieldsV1:
f:status:
.: {}
f:observedGeneration: {}
f:publishedEnvironments: {}
f:state: {}
manager: dev-portal
operation: Update
time: "2021-05-30T21:29:24Z"
name: petstore-portal
namespace: default
resourceVersion: "53288865"
selfLink: /apis/devportal.solo.io/v1alpha1/namespaces/default/portals/petstore-portal
uid: 08165b42-259e-45a7-be57-7ad4040c34b6
spec:
banner:
fetchUrl: https://i.imgur.com/EXbBN1a.jpg
customStyling: {}
description: The Gloo Portal for the Petstore API
displayName: Petstore Portal
domains:
- portal.petstore.com:30001
favicon:
fetchUrl: https://i.imgur.com/QQwlQG3.png
primaryLogo:
fetchUrl: https://i.imgur.com/hjgPMNP.png
publishedEnvironments:
- name: dev
namespace: default
staticPages: []
status:
observedGeneration: 1
publishedEnvironments:
- apiProducts:
- name: petstore-product
namespace: default
name: dev
namespace: default
state: Succeeded
kind: List
metadata:
resourceVersion: ""
selfLink: ""Hi @arjunkrishnasb , sorry for the late reply. I looked into this and figured out what is going on:
"portals":{} list to always be empty and the got runtime.Object without object metadata message to be logged. host property on the request and then compare the result with the domains on all of the available portals without stripping the port from them. In your case this will cause portal.petstore.com to be compared with portal.petstore.com:30001, which obviously will never be a match.I just merged a fix for both these issues. It will be included in the next version (0.7.6), which will be released by the end of this week. For now you should be able to work around this by just updating the domains property in your portal to also include portal.petstore.com (no port).
marcogschmidt
commented
3 years ago Fix has been released.
Hi,
I deployed Gloo enterprise with trial license and doing a POC on Gloo portal now. After i create all the resources to create the portal following the official docs, when i go to the portal it is giving me a 404 after loading the page for few seconds.
Kuberetes version:
In our environment we deployed Gloo using NodePort:
DevPortal is deployed:
Portal resource deployed and in succeeded state:
In logs:
Kindly help me out if i am doing something wrong here or guide me with better troubleshooting.