You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "dmvolod (via GitHub)" <gi...@apache.org> on 2023/03/09 20:34:05 UTC
[GitHub] [camel-karavan] dmvolod opened a new issue, #674: Add operator E2E tests
dmvolod opened a new issue, #674:
URL: https://github.com/apache/camel-karavan/issues/674
It would be nice to have operator end-2-end test to validate at least basic reconcile logic.
Also complex Tekton deployment logic can be implemented with real operator build and deploy.
--
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: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-karavan] dmvolod commented on issue #674: Add operator E2E and integration tests
Posted by "dmvolod (via GitHub)" <gi...@apache.org>.
dmvolod commented on issue #674:
URL: https://github.com/apache/camel-karavan/issues/674#issuecomment-1464234453
Yes, sure.
Since, unlike the golang operator-sdk, OJSDK does not support dynamic event source inject and reloading, the only solution to get Tekton Pipelines and Tasks listeners after installing it is a complete reload of the entire operator Qaurkus application with sending exit code to it.
In this case, standard integration tests with running operator locally inside the surefire plugin `operator.start()` will not work and we need to build and install operator bundle before running e2e tests and than just run tests against already deployed operator in the Kubernetes cluster.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-karavan] mgubaidullin commented on issue #674: Add operator E2E and integration tests
Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin commented on issue #674:
URL: https://github.com/apache/camel-karavan/issues/674#issuecomment-1464201631
`As https://github.com/apache/camel-karavan/issues/567 introduces Quarkus application restart hack` could you explain more?
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-karavan] dmvolod commented on issue #674: Add operator E2E and integration tests
Posted by "dmvolod (via GitHub)" <gi...@apache.org>.
dmvolod commented on issue #674:
URL: https://github.com/apache/camel-karavan/issues/674#issuecomment-1463388819
> * What do we need for integration test? Kubernetes environment?
Exactly. As OJSDK doesn't support Fabric8 Kubernetes Mock Server for tests, we need a real Kubernetes cluster for that. For example, we can utilize following github action for that. Also, would be nice to filter test running by folder change in commit, to reduce resources and skip operator tests if others Karavan components changed only.
https://github.com/marketplace/actions/kubernetes-kind-cluster
> * I did not get the second. Care to elaborate
Yes, sure. As #567 introduces Quarkus application restart hack, real Karavan operator deployment into the Kubernetes cluster should be done. Also, we need to deploy whole Tekton pipelines, or only CRD's part to reduce resource consumption, as we don't need to tests a whole integration flow for now.
What do you think about it?
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-karavan] mgubaidullin closed issue #674: Add operator E2E and integration tests
Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin closed issue #674: Add operator E2E and integration tests
URL: https://github.com/apache/camel-karavan/issues/674
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-karavan] mgubaidullin commented on issue #674: Add operator E2E and integration tests
Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin commented on issue #674:
URL: https://github.com/apache/camel-karavan/issues/674#issuecomment-1462944996
1. What do we need for integration test? Kubernetes environment?
2. I did not get the second. Care to elaborate
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org