You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Shipeng Xie (Jira)" <ji...@apache.org> on 2023/02/07 06:48:00 UTC
[jira] [Commented] (FLINK-30757) Ugrade busybox version to a pinned version for operator
[ https://issues.apache.org/jira/browse/FLINK-30757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685076#comment-17685076 ]
Shipeng Xie commented on FLINK-30757:
-------------------------------------
Hi [~gaborgsomogyi] [~gyfora] , I am using the Flink k8s opeartor in production environment during work and want to learn and contribute to the Flink k8s operator. Can I take this task as the starter?
> Ugrade busybox version to a pinned version for operator
> -------------------------------------------------------
>
> Key: FLINK-30757
> URL: https://issues.apache.org/jira/browse/FLINK-30757
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gabor Somogyi
> Priority: Minor
> Labels: starter
>
> It has been seen that the operator e2e tests were flaky when used the latest version of the busybox so we've pinned it to a relatively old version. https://github.com/apache/flink-kubernetes-operator/commit/8e41ed5ec1adda9ae06bc0b6203abf42939fbf2b
> It would be good to do 2 things
> * Upgrade the busybox version to the latest in a pinned way
> * Add debug logs of the busybox pod in case of failure (to see why failed)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)