23 Nov
You are imprisoned in the deepest and darkest dungeon. It`s time to escape with your army of cute minions. Use them as shields, levers or to dominate the earth. Find out why you are locked up and beat everyone who stands in your way. To view versions, dependencies, defaults for the number of runner modules with each minion, how to access the persistent volume, and more, see the help and display examples below. After August 2022, we will end support for several features, including the URL of our original private Minion headset board. For more information, including how to easily prepare for this transition, check out our Explorers Hub article. Get the MINION_POD_INSTALLATION_NAME of the Minion pod you want to delete: Root volume: At least 50 GiB (node + PV) Persistent volume (PV): At least 20 GiB You can use New Relic`s containerized private minions (CPMs). These are private minions based on Docker containers that accept and run synthetic monitors for your private locations. To track Docker logs and verify the health of your monitors, see Containerized Private Minion (CPM) Maintenance and Monitoring. The Minion container must be configured to communicate with the Docker engine to create additional rider containers.
Each container created is then dedicated to performing a control associated with the synthetic monitor running in the private location to which the Minion container is linked. A CPM can be used without Internet access, but with a few exceptions. Public Internet integrity checking can be disabled by using the environment variable named MINION_NETWORK_HEALTHCHECK_DISABLED for a Docker container system environment or by using synthetics.minionNetworkHealthCheckDisabled for a Kubernetes container orchestration system environment. The CPM must be able to contact the domain synthetics-horde.nr-data.net. This is necessary so that the data can be reported to New Relic and the monitors can be received for execution. Ask your network administrator if this is a problem and how to configure exceptions. Unless the images are hosted in a local image repository, connections to quay.io or docker.io must be allowed through your firewall so that Docker can retrieve Synthetics Minion and Synthetics Minion Runner images. The “Runner” image is automatically dragged when the synthetic minion container is started. For more information about setting up a local repository and Runner registry endpoint, see Configuring the Docker Environment and Configuring the Kubernetes Environment. A single Docker CPM image serves both the Docker container system environment and the Kubernetes container orchestration system environment. The Docker image is hosted on quay.io.
To make sure your Docker image is up to date, check the newrelic/synthetics-minion repository quay.io. CPM images are also hosted on Docker Hub. See hub.docker.com/r/newrelic/synthetics-minion/tags for a list of all publications. In terms of game file size, you need at least 350 MB of free space. The system requirements for Millions of Minions: An Underground Adventure say you need at least 2GB of RAM. To play Millions of Minions: An Underground Adventure, you need at least one processor equivalent to an Intel Core i5-3317U processor. The cheapest graphics card you can play on is an ATI FireGL T2-128. The number of cores on the host determines the number of runner containers that the CPM can run simultaneously on the host. Because storage requirements adapt to the expected number of executor containers, it is recommended that you do not run multiple CPMs on the same host to avoid resource conflicts.
Installing and updating the CPM uses the same command to retrieve the latest Docker image from the repository Quay.io hosting the Docker CPM image. See quay.io/repository/newrelic/synthetics-minion for a list of all publications. To host CPMs, your system must meet the minimum requirements for the selected system environment. You can configure the private containerized minion with custom npm modules, retain data between boots, use environment variables, and more. For more information, see CPM Configuration. Docker CPM is not designed for use with container orchestrators such as AWS ECS, Docker Swarm, Apache Mesos, Azure Container Instances, etc. Running Docker CPM in a container orchestrator causes unexpected problems because it is itself a container orchestrator. If you use container orchestration, review our Kubernetes CPM requirements.
When a ReadWriteOnce (RWO) PV is provided to the minion, an implicit node affinity is established to ensure that the minion and runner containers are scheduled on the same node.