nicolaferraro commented on issue #1691:
URL: https://github.com/apache/camel-k/issues/1691#issuecomment-690314360
I've tested your exact scenario and everything works in my case on Minikube.
But I've found out that some tools consider the CRD validation part of the
build custom resource as invalid.
Can you try, as workaround to replace the build resource with this one?
```yaml
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: builds.camel.apache.org
labels:
app: "camel-k"
spec:
additionalPrinterColumns:
- JSONPath: .status.phase
description: The build phase
name: Phase
type: string
- JSONPath: .metadata.creationTimestamp
description: The time at which the build was created
name: Age
type: date
- JSONPath: .status.startedAt
description: The time at which the build was last (re-)started
name: Started
type: date
- JSONPath: .status.duration
description: The build last execution duration
name: Duration
type: string
- JSONPath: .status.failure.recovery.attempt
description: The number of execution attempts
name: Attempts
type: integer
group: camel.apache.org
names:
kind: Build
listKind: BuildList
plural: builds
shortNames:
- ikb
singular: build
categories:
- kamel
- camel
scope: Namespaced
subresources:
status: {}
version: v1
versions:
- name: v1
served: true
storage: true
```
Just `k apply -f newcrd.yaml`. It's the same CRD, without validation.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
