For whom: Panel Administrator, SRE. Required rights: Flow management and CDN.
Preliminary requirements
- Connected account provider in the status of
valid– see Providers and accounts . - An input node with a configured domain and HTTPS working: the panel checks the origin-TLS before the first contact with the provider.
- The provider account must have access to the DNS zone covering the node domain.
Operational life cycle
Side states:NEEDS_QUALIFICATION (checks are not passed or the provider is not qualified), NEEDS_ATTENTION (operator intervention is required), FAILED, ROLLING_BACK, ROLLED_BACK. Transitions between states are validated - the operation cannot “jump” the step.
Operations are idempotent: re-use of the same Flow reuses the existing binding, and the finished resource is returned immediately, without re-provisioning.
Delivery Domain and Domain Pools
The delivery domain is generated automatically from the input node domain: thenode.example.com node receives cdn.node.example.com. You do not need to invent and register it manually.
Domains are issued from domain pools under the lease model:
reserved– the domain is reserved for the CDN-block for the duration of provisioning;active- resource is ready, domain is fixed;released– The domain is returned to the pool after a rollback or uninstallation.
Terms of READY (fail-closed)
ISP status is deliberately considered insufficient, and the operation reachesREADY only when everything is done at once:
- the provider’s resource is active and the provider has issued a canonical CNAME;
- DNS recording is visible on authoritative servers and Confirmed by at least two independent public resolvers;
- TLS is valid on both the delivery domain and the origin node.
- Functional tests passed: HTTP-methods are processed correctly, disabling caching proved empirically, transport sample is successful.
needs_qualification, and the application of Flow informs about this, and the re-use cross-checks the resource and transfers it to ready when all the evidence is collected.
Monitoring of the operation
The status of the CDN block is visible directly in the Flow column:applying / verifying / ready / blocked / failed / draft, together with the transaction ID, delivery domain and error code. Observability.
Pushback of the operation
Rollback is a controlled operation that returns everything to its original state:- Restores each modified DNS record from the “before” image.
- removes artifacts created by a provider-side operation: CDN resource, origin group, certificate;
- releases the delivery domain lease (the domain returns to the pool);
- Returns the CDN block to the draft state.
ROLLBACK_PARTIAL with a list of unfinished items and marked as requiring attention — it will not be quietly marked “clean.” What to finish with your hands — see Troubleshooting.
Verification
- Check the status of the provider account -
valid. - Make sure that the input node has a domain and responds via HTTPS with a valid certificate.
Rollback
- Remove the CDN block from Flow and apply the configuration again (see Warning above).
- After a rollback, the delivery domain returns to the pool and can be issued again.
Limitations and risks
- One CDN block on Flow; the block must lead to exactly one input node with the domain.
- Tests become obsolete after 12 hours: “ready” always relies on fresh checks.
- Flow will fail until the CDN is ready (fail-closed) – consider this when planning routing changes, see Routing .
Typical errors
Application drops with NEEDS_QUALIFICATION
Application drops with NEEDS_QUALIFICATION
Either the provider does not have a qualified adapter (VK Cloud, Selectel, Beget, Timeweb), or the functional tests did not pass. In the first case, use Yandex Cloud or manual mode; in the second, eliminate the cause (see the operation error code) and apply the configuration again.
Pushback returns 409
Pushback returns 409
Operation in
READY - Direct rollback is prohibited. Remove the CDN block from Flow and apply the configuration.ORIGIN_TLS_FAILED before the start of maintenance
ORIGIN_TLS_FAILED before the start of maintenance
The original test didn’t go through: there’s no valid HTTPS certificate on the node. First, clean up the node’s domain and certificate, then repeat the application.
