surahman edited a comment on pull request #3710:
URL: https://github.com/apache/incubator-heron/pull/3710#issuecomment-924531062


   Hi @nicknezis, could you please clarify whether this is what a `ConfigMap` 
with a `Pod Template` would look like, and if not could you please provide an 
example?
   
   ```yaml
   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: some-config-map-name
   data:
     heron.kubernetes.pod.template.configmap.name: |
       apiVersion: apps/v1
       kind: Deployment
       metadata:
         name: heron-tracker
         namespace: default
       spec:
         selector:
           matchLabels:
             app: heron-tracker
         template:
           metadata:
             labels:
               app: heron-tracker
           spec:
             containers:
               - name: heron-tracker
                 image: apache/heron:latest
                 ports:
                   - containerPort: 8888
                     name: api-port
                 command: ["sh", "-c"]
                 args:
                   - >-
                     heron-tracker
                     --type=zookeeper
                     --name=kubernetes
                     --hostport=zookeeper:2181
                     --rootpath="/heron"
                 resources:
                   requests:
                     cpu: "100m"
                     memory: "200M"
                   limits:
                     cpu: "400m"
                     memory: "512M"
   ```
   
   I am in the final stages of testing the code and need to make sure I have 
the correct format for the `ConfigMap`s in case I need to make tweaks. The 
`heron.kubernetes.pod.template.configmap.name` is the key variable in the Java 
code but in the actual document, it will be the value associated with the key.


-- 
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]


Reply via email to