The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

$ minishift status
Minishift:  Running
Profile:    minishift
OpenShift:  Stopped
DiskUsage:  ERR of

perhaps this is related to the error state from the OpenShift isRunning check

Description

Can't launch service with an empty procfile.

Location

• Browser
• CLI
• API

Steps to reproduce

1. Create an empty procfile in a repo
2. Attempt to launch on Porter

With raw kube approach, we can easily have a built-in ComponentDefinition to reference a Git repo as a component (using Flux Kustomization as example but there're many approaches indeed):

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: foo
  namespace: default
spec:
  workload: 
    definition: 
      apiVersion: apps/v1
      kind: Deployment # 

1、当没有API文档时的空数据提示
2、当没有搜索到API文档时的空数据提示