Managed Container
Managed Container Apps
Container App is designed to publish or migrate a single HTTP/API container without exposing Kubernetes internals to the customer.
Back to Platform HelpWhat you configure
Define image tag, registry credential, container port, health check, environment variables, secrets, domain, persistent files, imports, scheduled jobs, and resource plan.
- The panel provides application-level actions such as create, deploy, status, logs, restart, and scale.
- Customers do not need kubectl, SSH, artisan import commands, or direct database access.
- Secrets are entered through masked fields and are not returned later in GET responses.
Deployment flow
- Create creates the app record and first revision.
- Deploy publishes a new image or configuration revision.
- DB dump and file archive imports must finish before deployment opens public routing.
- Scheduled jobs can be saved disabled, run manually, and enabled after verification.
- Public traffic is not opened before readiness succeeds.
- Logs and Status screens show deployment issues at customer level.
Domain and CDN
- If DNS does not yet point to CDN.com.tr, the domain remains in waiting DNS state.
- If no serviceable SSL certificate exists, the public HTTPS route is not opened.
- The app is served from edge locations through the CDN reverse proxy.
- WAF, cache preset, and origin host header settings are managed per app.