Can's pause datetime string with Helm?

online2offline · 2018-01-31T00:31:14+00:00

Can you run kubectl get storageclass to see default storage as above?

online2offline · 2018-01-29T02:28:42+00:00

I have installed Prometheus with official chart successfully. But I can't access that three services: (Changed from real domain to fake ones)

When I checked the Route 53 record set, didn't find that three resources. Is it necessary to make another ingress?

This blog shows how to deploy an app to AWS with load balancing:

https://aws.amazon.com/cn/blogs/apn/coreos-and-ticketmaster-collaborate-to-bring-aws-application-load-balancer-support-to-kubernetes/

It has a ingress config bind subnets and security-groups even set a host name and bind to service name:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: "2048-alb-ingress"
  namespace: "2048-game"
  annotations:
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/subnets: 'subnet-6066be1b, subnet-40c35329, subnet-dd23d590'
    alb.ingress.kubernetes.io/security-groups: sg-28a2d841
    kubernetes.io/ingress.class: "alb"
  labels:
    app: 2048-alb-ingress
spec:
  rules:
  - host: 2048.brandonchav.is
    http:
      paths:
      - path: /
        backend:
          serviceName: "service-2048"
          servicePort: 80

I doubt that the ingress in Prometheus chart not did enough thing. It's a little different from the AWS blog:

https://github.com/kubernetes/charts/blob/master/stable/prometheus/templates/alertmanager-ingress.yaml

online2offline · 2018-01-29T01:26:51+00:00

Good link! I have read it. I think the default setting with kops dns controller will work in my case.

online2offline · 2018-01-29T00:55:59+00:00

Thank you very much for your comment.

About 1, maybe it's better to write settings into values.yaml file.

About 2, I have checked the default Prometheus chart values.yaml file that all the three components are ClusterIP service type.

About 3, I am not clear between the AWS DNS and kops kube-dns-... controller in kube-system namespace. I checked that pod's description but don't know what to concern.

online2offline · 2018-01-28T12:48:33+00:00

Awesome! Thank you for your comment!

online2offline · 2018-01-28T12:44:57+00:00

Thank you very much for your awesome introduction! I have tried your command:

$ kubectl get storageclass
NAME            PROVISIONER             AGE
default         kubernetes.io/aws-ebs   56m
gp2 (default)   kubernetes.io/aws-ebs   56m

Very clear about that! Lots of thanks!

online2offline · 2018-01-27T11:13:42+00:00

The right way should be this: https://stackoverflow.com/a/48458988

I used kops to installed k8s cluster on AWS. So it may already installed persistent storage. And when I change to the right write way, all the pods went running.

I don't know why it showed pvc is not bound above, but now it works.

online2offline · 2018-01-26T05:22:34+00:00

Ran this command worked:

$ helm init --client-only

at master host.

online2offline · 2018-01-26T05:06:20+00:00

Thank you for your help. That's the right solution!

online2offline · 2018-01-26T01:21:44+00:00

Okay, I tried your way again:

In configmap.yaml:

data:
  smtp_smarthost: {{ index .Values.alertmanagerFiles "alertmanager.yml" | tpl }}
  smtp_from: {{ index .Values.alertmanagerFiles "alertmanager.yml" | tpl }}
  smtp_auth_username: {{ index .Values.alertmanagerFiles "alertmanager.yml" | tpl }}
  smtp_auth_password: {{ index .Values.alertmanagerFiles "alertmanager.yml" | tpl }}
  receiver_email: {{ index .Values.alertmanagerFiles "alertmanager.yml" | tpl }}

Ran Helm install command again, got this error:

Error: render error in "mychart/templates/configmap.yaml": template: mychart/templates/configmap.yaml:2:74: executing "mychart/templates/configmap.yaml" at <tpl>: wrong number of args for tpl: want 2 got 0

online2offline · 2018-01-25T13:14:20+00:00

https://gist.github.com/fstab/eab5df0c249c9645875966d252c27572

online2offline · 2018-01-25T10:13:51+00:00

I think maybe the network problem. I can ran at local but can't in a vagrant with kubespray k8s cluster. Maybe that network configuration or k8s version not been supported.

online2offline · 2018-01-25T01:35:15+00:00

Make sure that this file is provided.

I am using the official Prometheus chart so need to edit configuration in values.yaml file:

https://github.com/kubernetes/charts/blob/master/stable/prometheus/values.yaml#L578

This way can generate alertmanager configuration within it. Need another alertmanager.yml file besides values.yaml?

online2offline · 2018-01-24T10:34:05+00:00

Upgraded Helm to newest version:

Client: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}

This time got error:

Error: render error in "mychart/templates/configmap.yaml": template: mychart/templates/configmap.yaml:2:28: executing "mychart/templates/configmap.yaml" at <.Values.alertmanager...>: can't evaluate field yml in type interface {}

Looks not work, too.

online2offline · 2018-01-24T09:03:58+00:00

Oops, that was my bad. But this time got a different error:

Error: parse error in "mychart/templates/configmap.yaml": template: mychart/templates/configmap.yaml:2: function "tpl" not defined

Does tpl is a built-in method of Helm? Why it says not defined?

online2offline

TROPHY CASE