gansheer commented on issue #4923:
URL: https://github.com/apache/camel-k/issues/4923#issuecomment-1823050083
This error is due to the `helm upgrade` command not updating the CRDs
(Custome Resource Definitions).
You should see in your integrationkit Custom Resource that it contains in
`.spec.task` a `{}` where the new `package` task should be:
```yaml
...
spec:
tasks:
- builder:
...
- {}
- spectrum:
...
```
(the last task could be any other publish strategy name)
The fact that the `helm upgrade` command does not update the CRDs is a
[design choice](https://github.com/helm/helm/issues/7735) from Helm so there is
no bug on their side.
For now I suggest you use the workaround of manually updating the CRDs in
your procedure (this example use kustomize):
1. Install camel-k 2.0.0 with helm
`helm install camel-k -f myValues.yaml camel-k/camel-k --version 2.0.0`
2. Update the CRDs to the target version:
`kubectl apply -k
"https://github.com/apache/camel-k/main/helm/camel-k/crds?ref=v2.1.0"`
3. Upgrade to version 2.1.0 with helm
`helm upgrade -f myValues.yaml camel-k camel-k/camel-k --version 2.1.0
--force`
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
