I want to deploy a configmap component and parameterize its value e.g.
-
apiVersion: core.oam.dev/v1alpha2
kind: Component
metadata:
name: test-configmap
namespace: test-config
spec:
workload:
apiVersion: v1
kind: ConfigMap
metadata:
name: test-cm
namespace: test-config
data:
config-properties.yaml: |
greeting: Hello
parameters:
- name: config-data
required: false
fieldPaths:
- data-
and
-
apiVersion: core.oam.dev/v1alpha2
kind: ApplicationConfiguration
metadata:
name: test-appconf
namespace: test-config
annotations:
version: v1.0.0
description: "Test Config application"
spec:
components:
- componentName: test-configmap
parameterValues:
- name: config-data
value:
config-properties.yaml: |
greeting: Howdy-
But this fails to deploy with
The ApplicationConfiguration "test-appconf" is invalid:
- spec.components.parameterValues.value: Invalid value: "object": spec.components.parameterValues.value in body must be of type integer,string: "object"
- : Invalid value: "": "spec.components.parameterValues.value" must validate at least one schema (anyOf)
- spec.components.parameterValues.value: Invalid value: "object": spec.components.parameterValues.value in body must be of type integer: "object"
-
ConfigMap/Secret as part of the component via CUE or Helm templates.
", the value should be decoded. Also, you need to: - parameterize every data item by its key
- name: config-data
required: false
fieldPaths:
- data.config-properties # do not use config.properties- set its value by string like this:
- name: config-data
value: "enemies=aliens\nsecret.code.lives=30 \n"
1 reply
11 replies
XxxDefinition are now implemented).
Was working through the KubeVela 1.0 install and quick start docs. Tried both KinD and minikube versions. The health check is reporting an error.
$ kubectl get application first-vela-app -o yaml
...
- lastTransitionTime: "2021-05-25T22:14:40Z"
message: 'app=first-vela-app, comp=express-server, trait=ingress, check health
error: get template context: failed to get obj express-server with gvk networking.k8s.io/v1beta1,
Kind=Ingress : ingresses.networking.k8s.io "express-server" not found'
reason: ReconcileError
status: "False"
type: HealthCheckThe ingress appears to be present.
$ kubectl get ingresses -n vela-system express-server
NAME CLASS HOSTS ADDRESS PORTS AGE
express-server <none> testsvc.example.com 192.168.49.2 80 34mThe app is working.
$ curl -H "Host:testsvc.example.com" http://192.168.49.2
<xmp>
Hello World
[removed whale ASCII art]
</xmp>Looks like a version mismatch (i.e. v1 vs v1beta1)? Does the ingress trait definition need to be updated or a different ingress-nginx version installed?
$ kubectl get ingresses -n vela-system express-server -o yaml | more
apiVersion: networking.k8s.io/v1
kind: Ingress
...@resouer Will the issue above prevent rollout from working? I may be misunderstanding how this is supossed to work but I can't make this app roll the pods from image stefanprodan/podinfo:5.2.0 to stefanprodan/podinfo:5.2.1 with these two versions of the application YAML.
First version
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: rollout-app
spec:
components:
- name: rollout-comp
type: webservice
properties:
image: stefanprodan/podinfo:5.2.0
port: 9898
traits:
- type: ingress
properties:
domain: rollout.example.com
http:
"/": 9898
rolloutPlan:
rolloutStrategy: "IncreaseFirst"
rolloutBatches:
- replicas: 50%
- replicas: 50%
targetSize: 3Second version
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: rollout-app
spec:
components:
- name: rollout-comp
type: webservice
properties:
image: stefanprodan/podinfo:5.2.1
port: 9898
traits:
- type: ingress
properties:
domain: rollout.example.com
http:
"/": 9898
rolloutPlan:
rolloutStrategy: "IncreaseFirst"
rolloutBatches:
- replicas: 50%
- replicas: 50%
targetSize: 3
~ >>> helm install --create-namespace -n vela-system kubevela kubevela/vela-core
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "ScopeDefinition" in version "core.oam.dev/v1beta1", unable to recognize "": no matches for kind "TraitDefinition" in version "core.oam.dev/v1beta1", unable to recognize "": no matches for kind "WorkloadDefinition" in version "core.oam.dev/v1beta1"]
3 replies
13 replies
hello all, i just started exploring kubevela. Had a noob question. How does one add app configuration declaratively in an app yaml file, I understand that one can use the vela cli. But I am wondering if its possible to app yaml. for example if I have a worker component
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: app-worker
spec:
components:
- name: myworker
type: worker
properties:
image: "busybox"
cmd:
- sleep
- "1000"how does one add app configuration to this yaml and also how about opaque secrets like passwords like db password?
3 replies
Hi, I tried KubeVela quick-start in AKS, I follow this document to enable ingress. But after I deployed first-vela-app, I got below error:
services:
- healthy: true
name: express-server
traits:
- healthy: true
message: |
No loadBalancer found, visiting by using 'vela port-forward first-vela-app'
type: ingress-1-20
workloadDefinition:
apiVersion: apps/v1
kind: Deployment
status: runninghow do I resolve this issue?
1 reply
7 replies
