-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: CRD schema does not match with defined value.schema.json #43
Comments
What is the difference between the two? |
A valid values file for the one associated with the value.schema.json is: # @param {object} app Helm Chart parameters section
infra:
# @param {string} app Helm Chart service parameters section
env: dev
# @param {boolean} app Helm Chart service parameters section
svc: false
# @param {object} app Helm Chart parameters section
app:
# @param {object} app Helm Chart service parameters section
service:
# @param {enum{NodePort,LoadBalancer}} app Helm Chart service type
type: NodePort
# @param {integer{min=30000,max=32767}} app Helm Chart service port
port: 31180 But if I submit a CR, such as: apiVersion: composition.krateo.io/v0-0-10
kind: Xapp
metadata:
annotations:
krateo.io/connector-verbose: "true"
meta.helm.sh/release-namespace: krateo-system
labels:
app.kubernetes.io/managed-by: Helm
name: x
namespace: demo-system
spec:
app:
service:
type: LoadBalancer
port: 31555
infra:
env: dev
svc: false I got the following error: Error from server (BadRequest): error when creating "xapp.cr.yaml": Xapp in version "v0-0-10" cannot be handled as a Xapp: strict decoding error: unknown field "spec.app.service" Because the CRD has been installed on then cluster in a wrong way because it will accept a schema like: apiVersion: composition.krateo.io/v0-0-10
kind: Xapp
metadata:
annotations:
krateo.io/connector-verbose: "true"
meta.helm.sh/release-namespace: krateo-system
labels:
app.kubernetes.io/managed-by: Helm
name: x
namespace: demo-system
spec:
app:
env: dev
svc: false
infra:
env: dev
svc: false But this is not the schema defined in the submitted CompositionDefinition. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Once the CompositionDefinition is installed on the cluster, the CRD schema generated does not match with the one defined in value.schema.json.
To Reproduce
Steps to reproduce the behavior:
while the value.schema.json defined is:
The text was updated successfully, but these errors were encountered: