-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm chart #13
Comments
Hi ! |
Hi @TomChv, please fork the repo, push your changes there and open a PR so we can discuss the changes |
I was using @TomChv PR until the branch was deleted the other day. Since then, I migrated using stakater's applicationName: oom-event-generator
labels:
group: com.my-group
team: my-team
deployment:
replicas: 1
image:
repository: xingse/kubernetes-oom-event-generator
tag: v1.2.0
env:
- name: VERBOSE
value: "1"
ports:
- containerPort: 10254
name: metrics
protocol: TCP
probes:
readinessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 10
periodSeconds: 10
livenessProbe:
httpGet:
path: /metrics
port: metrics
initialDelaySeconds: 10
periodSeconds: 10
resources:
limits:
cpu: 200m
memory: 128Mi
requests:
cpu: 100m
memory: 64Mi
service:
ports:
- name: metrics
port: 10254
protocol: TCP
targetPort: metrics
serviceMonitor:
enabled: true
endpoints:
- port: metrics
interval: 30s
path: /metrics
rbac:
serviceAccount:
enabled: true
name: oom-event-generator
clusterroles:
- name: oom-event-generator
rules:
- apiGroups:
- ""
resources:
- pods
- pods/status
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- events
verbs:
- create
- patch
- list
- watch |
It would be nice to package this up as a Helm chart to make it really easy to deploy.
The text was updated successfully, but these errors were encountered: