You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently SNO vDU pre-install and certain post install configs (such as performance profile and tunedpatch application) are supported by Jetlag. For complete DU configuration, we require the installation of the following additional operators and their config CRs to be applied thereafter (based on certain input vars):
PTP Operator (with ptpConfigSlave and ptpOperatorConfigForEvent configs)
Additional enhancements to consider:
No need to set separate vars setup_bastion_registry, use_bastion_registry (disconnected ipv6 setup) and sno_localstorage_configuration when du_profile is enabled. They should be all be enabled in this case.
Currently SNO vDU pre-install and certain post install configs (such as performance profile and tunedpatch application) are supported by Jetlag. For complete DU configuration, we require the installation of the following additional operators and their config CRs to be applied thereafter (based on certain input vars):
The operator install procedure is fairly consistent across releases however, the config afterwards may vary between releases.
Details can be found here:
https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-sno-post-install-time-cluster-config
Source of truth for all DU config CRs:
https://github.com/openshift-kni/cnf-features-deploy/tree/release-4.15/ztp/source-crs
The text was updated successfully, but these errors were encountered: