baimafeima-yf commented on code in PR #25944:
URL: https://github.com/apache/flink/pull/25944#discussion_r1921705143
##########
flink-kubernetes/src/main/java/org/apache/flink/kubernetes/configuration/KubernetesConfigOptions.java:
##########
@@ -510,6 +510,23 @@ public class KubernetesConfigOptions {
"Whether to enable HostNetwork mode. "
+ "The HostNetwork allows the pod could
use the node network namespace instead of the individual pod network namespace.
Please note that the JobManager service account should have the permission to
update Kubernetes service.");
+
+
+ public static final ConfigOption<String> KUBERNETES_LOG_VOLUME_HOSTPATH =
+ key("kubernetes.log.volume.hostpath")
+ .stringType()
+ .defaultValue("/apps/log/flink")
+ .withDescription("flink host machine log path");
+
+
+ public static final ConfigOption<String>
KUBERNETES_LOG_VOLUMES_MOUNT_MOUNTPATH =
+ key("kubernetes.log.volumemounts.mountpath")
Review Comment:
Thank you very much for your review. Yes, we can configure a container's
PersistentVolume (PV) and PersistentVolumeClaim (PVC) to achieve log mounting.
However, when starting a Flink application via code invocation, we found
that the log mounting was not effective. Therefore, we modified this section of
the code to implement log mounting and added a toggle
kubernetes.decorator.log-mount.enabled. If users encounter the same situation
as us, they only need to enable this toggle to achieve log mounting; it is
disabled by default.
--
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]
