Take a look at https://github.com/dlmarion/accumulo-k8s. You can put the Accumulo config in a ConfigMap (accumulo-config.yaml), then mount it at the correct location in another container (see the server process yaml files). I used a job to do the init phase, see accumulo-init.yaml.
From: Samudrala, Ranganath [USA] via user <user@accumulo.apache.org> Sent: Thursday, February 2, 2023 4:11 PM To: Samudrala, Ranganath [USA] via user <user@accumulo.apache.org> Subject: Init accumulo with custom properties file Hello I see there is an option to start an Accumulo component with a different properties file using -p, -props or --props option. Any reason same feature does not exist while performing init? The problem I am trying to solve is as below: I am trying to configure Accumulo with S3 using instructions here: https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html . This instructions calls for following steps: 1. Run "init" or "init --upload-accumulo-props" 2. Run "init --add-volumes" option 3. Start all Accumulo components. I am trying to configure the setup in K8S and would like to merge all these steps into one deployment invocation task. In K8S, we can attempt to do the first two steps using "initContainers" but the "accumulo.properties" need to be different for each step. So, let us say, I create 2 properties files, accumulo-init.properties and accumulo.properties. In the first step we should be able to specify accumulo-init.properties and for remaining steps, we should be able to use accumulo.properties. Problem is there is no option to specify a property file during the "init" process. thanks Ranga
