[feature] Add troubleshooting dump script #106
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release 1.3.0
Release 1.3.1
Release 1.4.0
* [feature]: Added support for external DNS using dns endpoint * [feature]: waiting on balancer recognition for route * [chore]: rename dns type to 'external_dns' in mninus * [chore]: revert values.yaml * [chore]: get information from providers for gateways * [chore]: rework, we now apply the dns ednpoint only on scope creation * [chore]: rework, we now apply the dns ednpoint only on scope creation * [chore]: pr review * [feature] define a component name with maximum 63 characters based on namespace and application slug * feat: log improvements (#58) * [fixes][route53]: we create the record on both hosted zones * [feature] ignore not found errors when deleting k8s objects * [feature] set default memory to 128 MB * [feature] Add missing labels to k8s objects + Allow to delete extra gPRC ports (#68) * [feature] Add missing labels to k8s objects * [feature] add script to delete all objects related to a deployment_id * feat: add Pod Disruption Budget (PDB) support (#64) * feat: add Pod Disruption Budget (PDB) support - Add POD_DISRUPTION_BUDGET configuration to values.yaml - Integrate PDB settings into deployment build_context using jq - Create pdb.yaml.tpl template with standard annotations and labels - Support for configurable maxUnavailable (percentage or number) * [feature]: pod disruption budget build tpl * [feature]: private and public domains (#65) * [feature] add support for web sockets inbound traffic (#69) --------- Co-authored-by: Sebastian Nallar <sebastiansaidnallar@gmail.com> Co-authored-by: Sebastian Nallar <95891104+sebasnallar@users.noreply.github.com> Co-authored-by: Javi <javier.solis@nullplatform.io>
Release 1.5.0
Release 1.5.1
This reverts commit dde9e65.
geisbruch
changed the title
fedemaleh
reviewed
Dec 16, 2025
Comment on lines
+238
to
+242
| # Object naming patterns based on analysis | ||
| DEPLOYMENT_NAME="d-${SCOPE_ID}-${DEPLOYMENT_ID}" | ||
| SECRET_NAME="s-${SCOPE_ID}-d-${DEPLOYMENT_ID}" | ||
| HPA_NAME="hpa-d-${SCOPE_ID}-${DEPLOYMENT_ID}" | ||
| PDB_NAME="pdb-d-${SCOPE_ID}-${DEPLOYMENT_ID}" |
Collaborator
There was a problem hiding this comment.
No conviene buscar por label? Se que al menos Itti metio un override para cambiar el nombre de los objetos.
fedemaleh
reviewed
Dec 16, 2025
| if kubectl get events -n "${NAMESPACE}" \ | ||
| --field-selector involvedObject.name="${resource_name}" \ | ||
| --sort-by='.lastTimestamp' 2>/dev/null | grep -v "^No resources found"; then | ||
| : |
fedemaleh
reviewed
Dec 16, 2025
| if kubectl get events -n "${NAMESPACE}" \ | ||
| --field-selector involvedObject.name="${resource_name}" \ | ||
| --sort-by='.lastTimestamp' 2>/dev/null | grep -v "^No resources found"; then | ||
| : |
Collaborator
There was a problem hiding this comment.
No tendría sentido invertir la condición? Entiendo que estamos metiendo un noop acá.
fedemaleh
reviewed
Dec 16, 2025
| if kubectl get events -n "${NAMESPACE}" \ | ||
| --field-selector involvedObject.name="${resource_name}" \ | ||
| --sort-by='.lastTimestamp' 2>/dev/null | grep -v "^No resources found"; then | ||
| : |
Collaborator
There was a problem hiding this comment.
No tendría sentido invertir la condición? Entiendo que estamos metiendo un noop acá.
fedemaleh
reviewed
Dec 16, 2025
| if kubectl get events -n "${NAMESPACE}" \ | ||
| --field-selector involvedObject.name="${pod_name}",involvedObject.kind=Pod \ | ||
| --sort-by='.lastTimestamp' 2>/dev/null | grep -v "^No resources found"; then | ||
| : |
Collaborator
There was a problem hiding this comment.
No tendría sentido invertir la condición? Entiendo que estamos metiendo un noop acá.
fedemaleh
reviewed
Dec 16, 2025
| if get_and_print_resources_by_label "pod"; then | ||
| # Get detailed pod status | ||
| print_section "Pod Status (detailed)" | ||
| kubectl get pods -n "${NAMESPACE}" -l "${LABEL_SELECTOR}" -o wide |
Collaborator
There was a problem hiding this comment.
Estamos haciendo el kubectl get pods un montón de veces.
No tiene sentido hacer el get y dejarlo en una variable archivo y que el resto lo lea? @ignacioboud ya hizo esta lógica para el diagnose podríamos copiarla.
Contributor
There was a problem hiding this comment.
mi duda es como queremos utilizar esto por que veo un upload, podemos agregarle de ultima un parametro al diagnose par que haga el upload de la data cruda. me resulta raro que este en dos lugares diferentes.
…dd_dump_status_troubleshooting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.