-
Notifications
You must be signed in to change notification settings - Fork 6
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #6 : Add Namespace and Probes Configuration to Kubernetes Manifests #7
base: main
Are you sure you want to change the base?
Conversation
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.
Thanks @RohanRusta21! Could you also add a description to the newly added fields
} | ||
} | ||
}, | ||
"readiness": { |
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.
Can you add order
: ["path", "initialDelaySeconds"...]
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.
Hey @petar-cvit , Yup its done now. Please Review it :)
- name: {{ $key }} | ||
value: {{ $value | quote }} | ||
{{- if .Values.general.environment }} | ||
{{- toYaml .Values.general.environment | indent 12 }} |
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.
} | ||
}, | ||
"order": [ | ||
"enabled", |
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.
can we add enabled
to each probe separately? Also can you make it disabled by default in values.yaml
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.
Hi @petar-cvit , actually initially I tried to have separate toggle for each probe. But it was not working fine. Maybe will try it again.
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.
Please do. You can paste the error here if you want and we can try to figure it out
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.
Hi @petar-cvit @KaradzaJuraj ,
This pull request focuses on the addition of new fields within various files, namely "deployment.yaml", "services.yaml", "values.schema.json", and "values.yaml". Here's a summary of the changes made:
In "demo-extended/templates/deployment.yaml", I have introduced YAML code for Namespace and Probes (specifically, readinessProbe, livenessProbe, and startupProbe). The default values for these fields are retrieved from "values.yaml".
Within "demo-extended/templates/services.yaml", I have incorporated YAML code for Namespace. Similar to the deployment template, the default values for these fields are sourced from "values.yaml".
In "demo-extended/values.schema.json", I have extended the JSON schema to include the Namespace field below Name, which falls under the metadata of deployment.yml. Additionally, I have structured a separate, expandable section for Probes, allowing users to conveniently review and customize each probe as needed.
Within "demo-extended/values.yaml", default values have been provided for the newly added fields in the branch, along with resources (CPU and memory), which were previously declared but lacked default values.
Please Review the PR and feel free to contact me if any improvement required from my end 馃憤 ,
Thanks & Regards,
Rohan Rustagi