xshipeng opened a new pull request, #530: URL: https://github.com/apache/flink-kubernetes-operator/pull/530
<!-- *Thank you very much for contributing to the Apache Flink Kubernetes Operator - we are happy that you want to help us improve the project. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.* ## Contribution Checklist - Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue. - Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component. Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix][docs] Fix typo in event time introduction` or `[hotfix][javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`. - Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review. - Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can read more on how we use GitHub Actions for CI [here](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/development/guide/#cicd). - Each pull request should address only one issue, not mix up code from multiple issues. - Each commit in the pull request has a meaningful commit message (including the JIRA id) - Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below. **(The sections below can be removed for hotfixes of typos)** --> ## What is the purpose of the change Since [e2e test](https://github.com/apache/flink-kubernetes-operator/actions/runs/3895555690/jobs/6662337363) is flaky with latest busybox image in init container, we [pinned] (https://github.com/apache/flink-kubernetes-operator/commit/8e41ed5ec1adda9ae06bc0b6203abf42939fbf2b) the image version to a relatively old version. ## Brief change log - Add log printing for init container if e2e test is failed. - Upgrade the busybox version to the latest in a pinned way. ## Verifying this change <!-- Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing --> This change is already covered by existing tests, such as `e2e-tests/test_application_kubernetes_ha.sh`. To reproduce the failed tests locally and test modified init container log printing code: - Change the init container command in `e2e-tests/data/flinkdep-cr.yaml` to `command: [ 'wget', 'https://repo1.maven.org/maven2/org/apache/flink/flink-examples-streaming_2.12/1.14.4/flink-examples-streaming_2.12-1.14.4.jar', '-O', '/flink-artifact/myjob.jar' ]`. - Run `./e2e-tests/test_application_kubernetes_ha.sh`. - Part of the print log will be ``` ... Flink logs: Current logs for flink-example-statemachine-dddb4d664-m6n5b:artifacts-fetcher: Connecting to repo1.maven.org (198.18.3.208:443) wget: note: TLS certificate validation not implemented saving to '/flink-artifact/myjob.jar' myjob.jar 100% |********************************| 267k 0:00:00 ETA '/flink-artifact/myjob.jar' saved test error msg Previous logs for flink-example-statemachine-dddb4d664-m6n5b:artifacts-fetcher: Connecting to repo1.maven.org (198.18.3.208:443) wget: note: TLS certificate validation not implemented saving to '/flink-artifact/myjob.jar' myjob.jar 100% |********************************| 267k 0:00:00 ETA '/flink-artifact/myjob.jar' saved test error msg Current logs for flink-example-statemachine-dddb4d664-m6n5b:flink-main-container: Current logs for flink-kubernetes-operator-9744c66bd-27q2r:flink-kubernetes-operator: Starting Operator ... ``` ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changes to the `CustomResourceDescriptors`: no - Core observer or reconciler logic that is regularly executed: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org