You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "dirkjkb (JIRA)" <ji...@apache.org> on 2019/01/08 13:30:00 UTC
[jira] [Updated] (NIFI-5857) Non deterministic behaviour in
Kubernetes by trying to inject custom properties
[ https://issues.apache.org/jira/browse/NIFI-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dirkjkb updated NIFI-5857:
--------------------------
Fix Version/s: 1.9.0
Attachment: 0001-NIFI-5857-Non-deterministic-behaviour-in-Kubernetes-.patch
Status: Patch Available (was: Open)
Updated as Proposed:
* Config Files will be added inside container instead of creating them on the fly
* The run Command will be started through the bin/nifi.sh
> Non deterministic behaviour in Kubernetes by trying to inject custom properties
> -------------------------------------------------------------------------------
>
> Key: NIFI-5857
> URL: https://issues.apache.org/jira/browse/NIFI-5857
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.8.0
> Environment: Kubernetes, Docker
> Reporter: dirkjkb
> Priority: Critical
> Fix For: 1.9.0
>
> Attachments: 0001-NIFI-5857-Non-deterministic-behaviour-in-Kubernetes-.patch
>
>
> I want to override some config files in Nifi via Kubernetes. In order to do so I am trying to replace the files after the start. It appears that the docker file is started through a start.sh script which calls several other scripts. This implementation Leeds to a non deterministic state, since the replacement time can differ from the start.sh runtime. Furthermore, after restarting a pod, the replacing command will be run each time again what also leeds to a fuzzy state.
> My proposal would be instead of injecting and running some sh files who will set some variables the customized config files should just be copy replaced in the building step. The run command can then be replaced through the ENTRYPOINT ["bin/nifi.sh", "run"] Command.
> In order to get the logging output to the console, a logback-test.xml file should be created and configured so that all the meaningful information will be piped to stdout.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)