Open svollath opened 4 years ago
I had a quick look into this and saw similar failures in the backend. It looks like there's multiple issues when trying to pass helm's manfiest
for KubeCf's.
Err was: Object 'Kind' is missing in
- These are issues with KubeCf, they have objects without kinds. We'd need to chase them and see if this is expectedErr was: no kind "QuarksStatefulSet" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery
- These are due to non-standard resources, not sure we can do anything about these.. would need to know at build time and add them to the schema we use to pass the manifest (see https://github.com/kubernetes/client-go/issues/193#issuecomment-594440015)To solve this we'd probably need to manually chop up the kubecf manifest returned by helm and parse in ever smaller chunks to narrow down on the issue.
Frontend Deployment type
Backend (Jet Stream) Deployment type
SUSE CaaSP4 added as "CaaSP Endpoint" (Name: CaaSP4-tf4)
Expected behaviour
When I visit "Workloads > kubecf", status for pods is shown like for other workloads.
Actual behaviour
While information for kubecf is filled, it's incomplete - e.g. for pods it reports "0".
Steps to reproduce the behavior
Log output covering before error and any error statements
kubectl logs stratos-0 proxy -n stratos
snippet