You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/06/29 04:46:30 UTC

[GitHub] [camel-k] tadayosi commented on pull request #3402: fix(#3393): Update to CronJob batch/v1

tadayosi commented on PR #3402:
URL: https://github.com/apache/camel-k/pull/3402#issuecomment-1169529203

   > beside that, should we really keep support for OpenShift 3
   
   I think we are ready to remove OpenShift 3 support. The workflow is kept only because right now `oc cluster up` is the only way to test the OpenShift aspects of the features on GitHub. We'll not be able to have an alternative until MicroShift becomes usable.
   
   >  oh, I was not even looking at the failed workflow job error and thought it to be a flaky test run. many thanks!
   
   A short while ago we restored stability in our test suite. Now there shouldn't be so many flaky tests, so let's keep an eye on it and try not to introduce more failing tests.
   
   > let me see what it takes to make this optional. I think it is not only the trait that is using the CronJob API. I saw references to this all over the place.
   
   We can also disable E2E tests for CronJob when they run on OpenShift 3, just like this:
   https://github.com/apache/camel-k/blob/main/e2e/common/cli/install_test.go#L101-L107


-- 
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