cloudworkz / kube-eagle-helm-chart Goto Github PK

Helm chart for deployment of kube-eagle

Mustache 100.00%

kube-eagle-helm-chart's Introduction

Kube Eagle Helm Chart

Helm chart for deployment of kube-eagle in Kubernetes.

Installing helm chart

helm repo add kube-eagle https://raw.githubusercontent.com/cloudworkz/kube-eagle-helm-chart/master
helm repo update
helm install kube-eagle kube-eagle/kube-eagle

If using helm version 2 :

helm install --name=kube-eagle kube-eagle/kube-eagle

Chart configuration

Parameter	Description	Default
`rbac.create`	Create and use role based access resources	`true`
`telemetry.host`	Host for prometheus server to to listen on	`0.0.0.0`
`telemetry.port`	Port for prometheus server to listen on	`8080`
`serviceMonitor.create`	Whether or not to create a service monitor for prometheus operator	`false`
`serviceMonitor.interval`	Scrape interval for prometheus operator	`10s`
`serviceMonitor.scrapeTimeout`	Scrape timeout for prometheus operator	`10s`
`serviceMonitor.releaseLabel`	Release label being used for prometheus operator selector	`prometheus-operator`
`serviceMonitor.additionalLabels`	Additional labels to add to the ServiceMonitor
`metricsNamespace`	Prefix of exposed prometheus metrics	`eagle`
`logLevel`	Logger's log granularity (debug, info, warn, error, fatal, panic)	`info`
`podSecurityContext.runAsUser`	UserID to use for the pod	`99`
`podSecurityContext.runAsUser`	User group to use for the pod	`99`
`containerSecurityContext`	Security Context for the kube eagle container	`{}`
`podAnnotations`	Pod annotations	`{}`
`priorityClassName`	Priority Class to be used by the pod	`""`
`env`	Additional environment variables	`{}`

kube-eagle-helm-chart's People

Contributors

Stargazers

Watchers

kube-eagle-helm-chart's Issues

Support for k8s 1.16

K8s 1.16 has removed deprecated versions of api's.
Do you have any plan to make it work for 1.16 too ?

https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

helm install --name=kube-eagle kube-eagle/kube-eagle

Error: validation failed: unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta2"

Add support to set strategyType for Deployment

I guess will be nice to have an option where we can set strageryType.

Thx.

Add chart to artifacthub.io

Please add the chart to https://artifacthub.io/

How to pass ENV to helm chart

Seems that I can't pass ENV to helm chart ?

Thx, testing this now. Seems great!

`readinessProbe` and `livenessProbe` timeout too short

time curl 172.31.0.85:8080/health
Ok
real    0m1,429s
user    0m0,008s
sys     0m0,011s

It's taking longer than the default 1s to return the /health endpoint.

Support for ingressClassName in > Kubernetes 1.18

The annotation kubernetes.io/ingress.class will be depreacated.

See https://kubernetes.io/docs/concepts/services-networking/ingress/#deprecated-annotation

So users have to use the new ingressClassName field.

See https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#ingress-v1-networking-k8s-io

Add grafana dashboards for prometheus operator

It would be nice if grafana dasboards could be added though ConfigMap as it is done in https://github.com/helm/charts/tree/master/stable/prometheus-operator

Options to pass pod annotations

Would be great to have as well option to pass pod annotations.

Thx.

add securityContext to helm chart

Can you add a securityContext for the container (and possibly also the pod) with minimal access - so that it can be deployed with a strict PSP.

Without it I get:

state:
        waiting:
          message: container has runAsNonRoot and image will run as root
          reason: CreateContainerConfigError

Doesn't work outside of default namespace?

As far as I can tell, this works fine if you install the helm chart into the default namespace. As soon as you pass a --namespace something-else into the command, it is unable to authenticate.

I've pinned this down to the ServiceAccount resource, which has namespace: default specified in there.

Cannot install Helm chart

Since the removal of the tgz file in the repository, the installation instructions aren't correct anymore. Output:

helm install kube-eagle/kube-eagle --debug
[debug] Created tunnel using local port: '61514'

[debug] SERVER: "127.0.0.1:61514"

[debug] Original chart version: ""
Error: Failed to fetch https://raw.githubusercontent.com/google-cloud-tools/kube-eagle-helm-chart/master/kube-eagle-1.0.4.tgz : 404 Not Found

Support for custom podAnnotations, no hardcoded defaults

Sorry, my english is poor.

Current hardcoded Annotations

prometheus.io/scrape: "true"
prometheus.io/port: {{ .Values.service.port | quote }}
prometheus.io/path: "/metrics"

Annotations I need

prometheus.io/scrape: "false"
prometheus.io/scrape_every_5s: "true"
prometheus.io/port: {{ .Values.service.port | quote }}
prometheus.io/path: "/metrics"

I need a way to override the default like this.

kube-eagle pod is restarting frequently

the kube-eagle pod is restarting frequently.
This is the error I got.

panic: the server is currently unable to handle the request (get pods.metrics.k8s.io)

goroutine 38 [running]:
github.com/google-cloud-tools/kube-eagle/vendor/github.com/weeco/kube-eagle/pkg/metrics_store.Collect()
	/go/src/github.com/google-cloud-tools/kube-eagle/vendor/github.com/weeco/kube-eagle/pkg/metrics_store/metrics_store.go:59 +0x386
main.main.func1()
	/go/src/github.com/google-cloud-tools/kube-eagle/main.go:56 +0x32
created by main.main
	/go/src/github.com/google-cloud-tools/kube-eagle/main.go:52 +0x47

Is it possible to keep old versions of helm charts packages? I am relying on a specific version for the installation, but it breaks once you override it with a new version. Any plans to move to charts/stable?