-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(k8s): Update pods with correct probes and remove unnecessary dependencies #2362
feat(k8s): Update pods with correct probes and remove unnecessary dependencies #2362
Conversation
Tagging folks who actively use helm charts to make sure the change looks good on your sides. @pedro93 @bernardino @frsann @shakti-garg-saxo |
We're rolling our own kustomize-targeted manifests, only loosely based on these charts, so no need to take us into consideration 😅 Thanks for the ping, though! |
@@ -46,26 +46,38 @@ spec: | |||
imagePullPolicy: {{ .Values.image.pullPolicy }} | |||
ports: | |||
- name: http | |||
containerPort: 9001 | |||
containerPort: 9002 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
containerPort: 9002 | |
containerPort: {{ .Values.service.port }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an internal port. I think it should be hardcoded. service.port field is used in the service.yml to define external port. WDYT?
initialDelaySeconds: 60 | ||
periodSeconds: 30 | ||
failureThreshold: 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would probably make these come from values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I make the whole readiness and liveness probe come from values?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have a suggestion here to only move below properties to values.yaml. The httpGet path can stay hardcoded as this the behavior of app which is not going to change on user wish.
initialDelaySeconds: 60
periodSeconds: 30
failureThreshold: 8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
# This is the version number of the application being deployed. This version number should be | ||
# incremented each time you make changes to the application. | ||
appVersion: latest #0.3.1 | ||
dependencies: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though these sub-chart dependencies are local, I still believe listing dependencies is good for two reasons:
- Good for documentation and chart navigation
- one of sub-chart(component) can be toggled off in special deployment scenarios. It is enabled by "condition" property like
datahub-mae-consumer.enabled
. In our case, we don't need to deploy datahub-ingestion-cron(as we have our own ingestion service), so we just provide parameter "datahub-ingestion.cron.enabled=false"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right. I initially removed this because helm dep update
doesn't work for datahub since all the subcharts are in the charts directory. Reverting. Going to keep the version update since multiple setup jobs were added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated version to 1.1.2 since the change is minor
contrib/kubernetes/datahub/README.md
Outdated
@@ -4,16 +4,6 @@ A Helm chart for LinkedIn DataHub | |||
|
|||
Current chart version is `0.1.1` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Version needs to be upgraded as per chart.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
List of changes:
Checklist