| // Updated 2025-9-10 | |
| // | |
| // This proxy.pac configuration is a mirror of the other one, but sends these URLs to /dev/null | |
| // for use with a "Home" profile, as opposed to a "Work" profile, to ensure they're not ever accessed. | |
| // | |
| // IMPORTANT - the "RAW" url for Gists changes whenever they're edited, so you must copy the new | |
| // url to your Automatic Proxy Config field in Firefox. | |
| // The "Reload" button will just reload the previous version of the file | |
| function FindProxyForURL(url, host) { |
| { | |
| "severity": "Error", | |
| "service_name": "SREManualAction", | |
| "log_type": "cluster-configuration", | |
| "summary":"Action required: Network misconfiguration", | |
| "description": "Your cluster requires rou to take action. SRE has observed that there have been changes made to network configuration which impact normal working of the cluster: Default Ingress Controller allowedSourceRanges have been modified to exclude the IP(s) of the default router, ${IP}, causing the Console and OAuth routes to become inaccessible. Please allow the IP of service 'router-default' in namespace 'openshift-ingress' in the default Ingress Controller's allowedSourceRanges field.", | |
| "internal_only": false | |
| } |
| #!/usr/bin/env bash | |
| set -euxo pipefail | |
| set -o nounset | |
| NAMESPACE="${1}" | |
| OPERATOR="${2}" | |
| # Look for a CSV, then perform the reinstall if found. If you want to _always_ reinstall, remove this check and just keep the logic inside the "if" | |
| CSV_FOUND=$(oc -n "$NAMESPACE" get clusterserviceversions.operators.coreos.com -o name | grep "$OPERATOR") |
These conventions apply to this repository and can be adopted by any repository following the same standards.
CONTAINER_SUBSYS variable (defaulting
to podman) to allow overriding if desired
Document type: Project bootstrap / role instructions
Audience: Any Claude agent assuming the Architect role, or any Claude Code CLI session assuming the Master Control role
Scope: Project-agnostic. This document defines the framework. Project-specific context lives in a separate PROJECT.md (see §13).
Communication format: All inter-agent communication and all deliverables under this framework are markdown. Plans, dispatch envelopes, completion reports, state files, ADRs, in-repo plans, reviewer comments — every artifact is markdown. Live chat with the User happens in the chat interface; substantive outputs accompany that chat as markdown documents.