ArgoCon North America
argocd admin settings resource-overrides health degraded.yaml --argocd-cm-path argocd-cm.yaml
STATUS: Degraded
MESSAGE: DEMO_STATE is broken
degraded.yaml is the resource to evaluate, saved as a plain YAML file.--argocd-cm-path argocd-cm.yaml reads the Lua health checks from a local file instead of the cluster's argocd-cm.Audit your instruction files
To have Claude check your instruction files for outdated or conflicting content, run /doctor prompt-audit in a session. Claude looks for problems such as instructions written for older models, references to files or commands that don’t exist, and files that contradict each other. You get a report of findings with proposed edits, and nothing in your files changes until you ask Claude to apply them.
a repo with few mods that work together
claude mods
Leopold Aschenbrenner
Situational Awareness
modules installed from a module registry, such as the Public OpenTofu Registry or any TACOS (TF Automation and Collaboration Software) private modules registry. Other module sources can provide their own versioning mechanisms within the source string itself, or might not support versions at all. In particular, modules sourced from local file paths do not support version; since they're loaded from the same source repository, they always share the same version as their caller.
| Component | Current tag | Age | Latest tag | Latest age | Gap |
|---|---|---|---|---|---|
| ComponentA | 2.3.1 | 140 d | 3.0.2 | 12 d | 128 d |
| ComponentB | 1.8.4 | 45 d | 1.9.0 | 6 d | 39 d |
| ComponentC | 5.2.0 | 30 d | 5.2.3 | 3 d | 27 d |
| ComponentD | 4.1.0 | 20 d | 4.1.1 | 8 d | 12 d |
| ComponentE | 0.9.7 | 95 d | 0.9.7 | 95 d | 0 d |
Using this one for quite some time now and it's rly cool
[Summary, full note in Shaarli]
Approach: a startup taint plus the Node Readiness Controller (https://github.com/kubernetes-sigs/node-readiness-controller). No fixed sleep; keep NodeReady separate from workload initialization.
Limits: NoSchedule doesn't evict running workloads (needs a separate policy). Docs: https://node-readiness-controller.sigs.k8s.io/user-guide/getting-started.html , https://karpenter.sh/docs/concepts/nodepools/
aws ecr get-account-setting --name REGISTRY_POLICY_SCOPE
aws ecr put-account-setting --name REGISTRY_POLICY_SCOPE --value V2
Depending on your level of expertise in this area, you may wonder why Istio’s support for canary deployment is even needed, given that platforms like Kubernetes already provide a way to do version rollout and canary deployment. Problem solved, right? Well, not exactly. Although doing a rollout this way works in simple cases, it’s very limited, especially in large scale cloud environments receiving lots of (and especially varying amounts of) traffic, where autoscaling is needed.
apiVersion: v1
kind: ConfigMap
metadata:
name: gw-options
data:
horizontalPodAutoscaler: |
spec:
minReplicas: 2
maxReplicas: 2
deployment: |
metadata:
annotations:
additional-annotation: some-value
spec:
replicas: 4
template:
spec:
containers:
- name: istio-proxy
resources:
requests:
cpu: 1234m
service: |
spec:
ports:
- "\$patch": delete
port: 15021