Limitations

Out-of-band configuration

Out-of-band configuration modifications are not supported. The service’s core responsibility is to deploy and maintain the service with a specified configuration. In order to do this, the service assumes that it has ownership of task configuration. If an end-user makes modifications to individual tasks through out-of-band configuration operations, the service will override those modifications at a later time. For example:

If a task crashes, it will be restarted with the configuration known to the scheduler, not one modified out-of-band.
If a configuration update is initiated, all out-of-band modifications will be overwritten during the rolling update.

Prometheus also does not offer durable long-term storage, anomaly detection, automatic horizontal scaling and user management. Prometheus is not a dashboarding solution; it features a simple UI for experimentation with PromQL queries but relies on Grafana for dashboarding.

Scaling in

To prevent accidental data loss, the service does not support reducing the number of pods.

Disk changes

To prevent accidental data loss from reallocation, the service does not support changing volume requirements after initial deployment.

Best-effort installation

If your cluster does not have enough resources to deploy the service as requested, the initial deployment will not complete until either those resources are available or until you reinstall the service with corrected resource requirements. Similarly, scale-outs following initial deployment will not complete if the cluster does not have the needed available resources to complete the scale-out.

Virtual networks

When the service is deployed on a virtual network, the service may not be switched to host networking without a full re-installation. The same is true for attempting to switch from host to virtual networking.

Task Environment Variables