Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

Conversation

@kevinschumacher
Copy link
Contributor

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 17, 2017
@dhilipkumars dhilipkumars removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Sep 18, 2017
@dhilipkumars
Copy link
Contributor

/assign
/ok-to-test

@dhilipkumars
Copy link
Contributor

/retest

2 similar comments
@dhilipkumars
Copy link
Contributor

/retest

@dhilipkumars
Copy link
Contributor

/retest

@dhilipkumars
Copy link
Contributor

@kevinschumacher Could you please check on this error?

@kevinschumacher
Copy link
Contributor Author

kevinschumacher commented Sep 23, 2017

@dhilipkumars the error is occurring because kube-lego cannot be deployed without the user providing the .Values.config.KUBE_LEGO

The chart decides NOT to specify a default and it is commented out in the default values.yaml

This is likely because you need to specify your own email address in order to sign up with letsencrypt.

edit: this issue occurs in the current stable/kube-lego chart.

@kevinschumacher
Copy link
Contributor Author

kevinschumacher commented Sep 23, 2017

$  cd charts/stable/kube-lego
$  helm template .
Error: render error in "kube-lego/templates/deployment.yaml": template: kube-lego/templates/deployment.yaml:36:15: executing "kube-lego/templates/deployment.yaml" at <required "config.LEG...>: error calling required: config.LEGO_EMAIL is a required field
$  helm template . --set [email protected]

---
# Source: kube-lego/templates/deployment.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: kube-lego
    chart: kube-lego-0.2.0
    heritage: Tiller
    release: RELEASE-NAME
  name: RELEASE-NAME-kube-lego
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: kube-lego
        release: RELEASE-NAME
    spec:
      serviceAccountName: "default"
      containers:
        - name: kube-lego
          image: "jetstack/kube-lego:0.1.4"
          imagePullPolicy: "IfNotPresent"
          env:
            - name: LEGO_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: LEGO_POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
          # [email protected]
            - name: "LEGO_EMAIL"
              value: "[email protected]"
    ...

@kevinschumacher
Copy link
Contributor Author

https://github.com/kubernetes/charts/tree/master/stable/kube-lego#configuration

Note that there is purposely no default value for LEGO_EMAIL as mentioned in the readme.

@dhilipkumars
Copy link
Contributor

Hi @jackzampolin and @mgoodness,
Is it possible to provide a default dummy email address so that this Chart passes in the CI henceforth?

@jackzampolin
Copy link
Contributor

[email protected]?

@dhilipkumars
Copy link
Contributor

@jackzampolin could you please fix that with a differnt PR please?

@dhilipkumars
Copy link
Contributor

/retest

add an extra new line at the end of Chart.yaml file
@dhilipkumars
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2017
@dhilipkumars dhilipkumars merged commit 813410b into helm:master Nov 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants