- It is currently not possible. As a possible workaround, you may run a new Build.
kaniko be implemented in the CodeNOW CI/CD pipeline?#
- Yes. CodeNOW uses
docker buildCI step.
- At the moment you cannot modify yourself a CodeNOW CI/CD pipeline. It will likely be possible in future CodeNOW releases.
- Both options are currently not available. If you are interested in that feature, please let us know! Our support pages give you the opportunity to send us new feature requests. We welcome your feedback!
- In the left menu click
Dashboardto open a
Grafanainstance. Refer to CodeNOW documentation about Live Monitoring with Grafana.
- Currently 7 days.
- Yes, but only by opening a support ticket. Additional charges may be incurred.
- See DORA metrics.
- The DORA metrics might not be displayed immediately after connecting the Production Environment with the Application (thus enabling the DORA metrics) because DORA metrics are computed once a day and the computation might not have been started for the day yet.
- Yes. Use the
Docker/GenericComponent scaffolder. Because the configuration and deployment is not managed by CodeNOW, it comes without any guarantees that the configuration will work.
Will my custom cluster configuration implemented by the
Helm2 Generic chart or the
Docker/Generic scaffolder be automatically upgraded with the release of new versions of either of the scaffolders?#
- No, as it is technologically difficult to cover all use cases of these scaffolders.
- Yes. Please open a support ticket. We will perform the requested operation.
- A Cluster is an instance of a CodeNOW-managed Kubernetes Cluster. It is deployed independently of the CodeNOW platform, but CodeNOW controls and manages the Cluster exclusively (so the user does not need to).
- No. The usage of a monorepo is against the first rule of The Twelve-Factor App philosophy.
- Yes, currently it is possible for PostgreSQL, for other deployed third-party services, please open a support ticket.
Changing the cluster hardware resources allocated to a PostgreSQL service can result in a downtime. Downtime duration depends, among other things, on the underlying hosting hardware, the number of database replicas, the size of the database, and the actual database utilization.
- Changing allocated cluster hardware resources for a deployed PostgreSQL service:
- Navigate to
- Select the PostgreSQL service you want to change the resources for.
- Change the configuration in the
- Check the status of the PostgreSQL service in the table at the top of the
Managed Service Detail>
Statusfield displays the status of the update process (
- Navigate to