haanhvu commented on PR #3185:
URL: https://github.com/apache/camel-k/pull/3185#issuecomment-1122228868
> Hi @haanhvu I think here it is complaining about not correctly installed
CRDS. Can you run the following and get the output:
>
> ```
> kubectl get crd integrationplatforms.camel.apache.org -o yaml | grep
settings
> ```
>
> What we need to do is to install the proper CRDs into the cluster in order
to have your changes applied. As a last resort, if the above does not show any
`settingsSecurity` you can install the CRDs you can find in your local
`config/crd/bases/` manually.
@squakez yeah manually install the crd could be the last simple choice. I
just wanted to inspect if my environment has any problems with the `make`
commands. Anyway I'll dig deeper into this later...
I set up the crd manually and it worked:
```
minikube kubectl -- get crd integrationplatforms.camel.apache.org -o yaml |
grep settings
settings:
contains the Maven settings.
settingsSecurity:
contains the security of the Maven settings.
settings:
contains the Maven settings.
settingsSecurity:
contains the security of the Maven settings.
```
```
minikube kubectl -- apply -f ip.yaml
Warning: resource integrationplatforms/camel-k is missing the
kubectl.kubernetes.io/last-applied-configuration annotation which is required
by kubectl apply. kubectl apply should only be used on resources created
declaratively by either kubectl create --save-config or kubectl apply. The
missing annotation will be patched automatically.
```
```
minikube kubectl -- get ip
NAME PHASE
camel-k
```
Should I add this example to the PR and we merge it now? I'll add the e2e
test in a later PR.
--
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]
