One container on the CSE egress path
nf-egress-cse-undervalue-watcher runs as a Docker container from the image foundry-egress-proxy:0.1. This page collects what is recorded about it: how it is packaged, how to run it, and the questions the record does not answer.
See the run stepsWhat the record states
Container-packaged
The component is delivered as a container. There is no host install step and no per-machine build; the unit of deployment is the image.
Pinned image tag
The image is foundry-egress-proxy:0.1. The tag is explicit, so a deployment can be reproduced from the tag alone.
Egress-path component
It is built from an egress proxy image, and the name marks it as an egress component. Its exact network position is set by your environment.
Undervalue watch
The name identifies the condition it watches for: undervalue on CSE. The detection rules and outputs are not described in this record.
Early version
The image carries a 0.1 tag. Treat interfaces and behaviour as early and expect them to change between versions.
Running it
Pull the image
Fetch foundry-egress-proxy:0.1 from the registry your environment uses. The tag is fixed; do not substitute a floating tag.
Start the container
Run it as an ordinary Docker container under your usual supervisor or orchestrator. No other install or build step is recorded.
Give it its egress position
The component is named for the egress path, so place it where that role requires and grant it the reachability that position needs.
Confirm the running build
Check that the image reference reported by the running container is 0.1, so you always know which build is live.
Questions this record can and cannot answer
What exactly does it watch for?
The name states the condition: undervalue on CSE, observed from the egress path. The specific rules, thresholds and outputs are not part of the record this page is built from, so confirm them with the owning team before depending on them.
Does it act on traffic, or only observe it?
Not recorded. It ships from an egress proxy image, which is the kind of image that sits in the traffic path, but nothing here states whether it takes action on what it sees. Confirm before placing it inline.
How is it deployed?
As a Docker container from foundry-egress-proxy:0.1. No other packaging or install method is recorded.
Is 0.1 ready for production use?
The tag is 0.1 and no support level is recorded. Treat it as early software: pin the tag, watch it closely after rollout, and expect behaviour to change between versions.
Where are configuration, ports and metrics documented?
Not here. This page holds only what the system record contains: name, kind and image. Configuration, network details, credentials and any metrics or alerts live with the owning team.
About this page
This page is built from the Norfield system record for nf-egress-cse-undervalue-watcher. That record is short: the component is a container, and it runs from the image foundry-egress-proxy:0.1. Its description field is empty. Everything above stays inside those facts, plus what the component name itself says about its role. Where something is unknown, the page says so rather than filling the gap. If you own this service, the fastest improvement is to fill in the description and publish its configuration and outputs; this page gets more useful the moment the record does.