[Feature] why this workflowrun demo failed.
- Dominant language
- Go
- Stars
- 126
- Forks
- 66
- Avg merge
- 1h 40m
- Merged PRs (30d)
- 1
Description
I use this demo
https://github.com/kubevela/workflow/blob/main/examples/workflow-run/apply-applications.yaml
yaml is
```
apiVersion: core.oam.dev/v1alpha1
kind: WorkflowRun
metadata:
name: apply-applications
namespace: default
annotations:
workflowrun.oam.dev/debug: "true"
spec:
workflowSpec:
steps:
- name: apply-app2
type: apply-app
properties:
ref:
name: my-app
key: application
type: configMap
---
apiVersion: v1
kind: ConfigMap
metadata:
name: my-app
namespace: default
data:
application: |
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: webservice-app2
spec:
components:
- name: express-server2
type: webservice
properties:
image: crccheck/hello-world
ports:
- port: 8000
```
kubevela version : v1.8.1
workflow version: v0.5.0
result:
the workflowrun status is failed
error message :
```
run step(provider=kube,do=apply): the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml
```
but webservice-app2 application is running and have a pod express-server2-58f7474c55-txqxk is runing
the next ,The yaml file I use under configMap is in another namespace test
```
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: webservice-app2
namespace: test
spec:
components:
- name: express-server2
type: webservice
properties:
image: crccheck/hello-world
ports:
- port: 8000
```
the application in namespace test is successed and running ,
why apply-applications workflowrun prompt messaget is unknown format and status is failed
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with examples/workflow-run/apply-applications.yaml and reproduce the failure using KubeVela v1.8.1 and workflow v0.5.0. Compare the reported apply error with the successful applications in the default and test namespaces; done means identifying why the WorkflowRun is marked failed and documenting or correcting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100