Helm install command failing for same deployment yaml #64

Activity

1. sishida commented on May 9, 2019

   

   sishida

   on May 9, 2019

   Collaborator

   More actions

   Thank you for bringing this issue to our attention. The Microclimate team has been notified.
2. arjunsbabu commented on May 9, 2019

   

   arjunsbabu

   on May 9, 2019

   Last edited by arjunsbabu

   Author

   More actions

   the same deployment.yaml is working for another branch . I can fix the error above . But like to know why the same error is not happening for a different branch
   issue deployment.yaml is as follows

   apiVersion: extensions/v1beta1
   kind: Deployment
   metadata:
     name: "{{  .Chart.Name }}-deployment"
     labels:
       chart: '{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}'
   spec:
     replicas: {{ .Values.replicaCount }}
     template:
       metadata:
         labels:
           app: "{{ .Chart.Name }}-selector"
           version: "current"
       spec:
         containers:
         - name: "{{ .Chart.Name }}"
           image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
           imagePullPolicy: {{ .Values.image.pullPolicy }}
           ports:
           - containerPort: {{ .Values.service.servicePort }}
   
   

   values.yaml

   # Default values for templateExample.
   # This is a YAML-formatted file.
   # Declare variables to be passed into your templates.
   
   replicaCount: 1
   
   image:
     repository: sample
     tag: v0.1.0
     pullPolicy: Always
   
   service:
     name: http
     type: ClusterIP
     servicePort: 80
     targetPort: 3000
   
   resources:
     cpu: 100m
     memory: 128Mi
     requests:
       cpu: 100m
       memory: 128Mi
   

   I have tryed manual helm install command using the above files and it worked.
   The fix for the above is to add an "" in values.replicacount. After i have done it another error is coming in the microclimate deploy

   ie

   Error: release dohmhc-1eae8af9-978d-466a-9d67-3880463f6dcd failed: Deployment in version "v1beta1" cannot be handled as a Deployment: v1beta1.Deployment.Spec: v1beta1.DeploymentSpec.Replicas: readUint32: unexpected character: �, error found in #10 byte of ...|eplicas":"{ { .Value|..., bigger context ...|mespace":"dev-myhealthcoach"},"spec":{"replicas":"{ { .Values.replicaCount } }","template":{"metadat|...
   
   

   I have used the same deployment.yaml , values.yaml in another branch and its working. Infact what we have done is while we seen one branch working we merged the changes to another branch. ..But not working in new branch. Please help me find the route cause of tiller behaving differently in same situation. I have kept the issue branch for any testing
   @jagraj
3. arjunsbabu commented on May 9, 2019

   

   arjunsbabu

   on May 9, 2019

   Author

   More actions

   i believe the reason is some other values provided by the microclimate to tiller..
4. sishida commented on May 13, 2019

   

   sishida

   on May 13, 2019

   Collaborator

   More actions

   I am following up with the team again today to see if I can obtain more info for this question.
5. jagraj commented on May 13, 2019

   

   jagraj

   on May 13, 2019

   More actions

   Arjun seems to be sick, I just had slack conversation with Arjun and requested test case so that we can reproduce in our environment. This will help to capture logs and debug this problem. He is going to share more information tomorrow.
6. rajivnathan commented on May 13, 2019

   

   rajivnathan

   on May 13, 2019

   More actions

   I think there are 2 things related to naming that we should clarify:

   1. The helm chart folder name and the name in the Chart.yaml. I think those need to match because of helm limitations as I noted.
   2. The second is project name and the chart name. That's the one that I believe Arjun is talking about and those shouldn't need to match. It should work with Microcimate today.

   Steps to reproduce would help clarify whether that covers what Arjun is asking for and we can help verify it is working as expected.
7. jagraj commented on May 14, 2019

   

   jagraj

   on May 14, 2019

   Last edited by jagraj

   More actions

   I verified issue "2" above and this has been resolved in 18.06 release and the fix should be in your MC version 1.10 as well. I opened issue against our docs to take out the limitation that we currently documented in the current release of the docs.
8. sishida commented on May 15, 2019

   

   sishida

   on May 15, 2019

   Collaborator

   More actions

   Thanks for opening the issue, Jag! I have merged a pull request that removes the limitation in our docs. The changes should appear with the next Microclimate release.