Red Hat Summitこのコンテンツは選択した言語では利用できません。
Chapter 21. Managing technology preview features
You can enable or disable features that are Technology Preview by using feature flags.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
21.1. Managing feature flags
21.1.1. Prerequisites
- You have access to the environment where the RHACS component is deployed.
- You have permission to modify environment variables.
- You understand that the Technology Preview features might be incomplete and are provided with limited support.
- You know if the flag for the Technology Preview feature needs to be configured before the deployment. Check the installation manifests to see if they use the required flag.
Procedure
-
Identify the environment variable name associated with the feature flag. Consult the release notes or the
/v1/featureflagsAPI endpoint to identify the flag for the feature you want to enable or disable. Modify the feature flag by completing one of the following actions:
-
To enable a feature, configure the environment variable associated with the flag by setting its value to
true. Configure this directly on the Kubernetes deployment or during installation by using the Helm chart or the Operator custom resource (CR). -
To disable a feature, set the environment variable associated with the flag to
false.
-
To enable a feature, configure the environment variable associated with the flag by setting its value to
After the application is restarted or redeployed, verify that the feature has been enabled or disabled by completing the following steps:
-
Check the output of the
/v1/featureflagsAPI endpoint. - Check the application functionality related to the feature.
- Review logs or monitoring tools for any errors or confirmation messages.
-
Check the output of the
21.1.2. Best practices
Follow these best practices for using the feature flag:
- Always test feature changes in a staging environment before applying them to production.
- Keep a record of all feature flags and their current status.
- Be prepared to revert the changes if the feature causes issues.
21.1.3. Troubleshooting
Follow these troubleshooting guidelines:
- If the feature does not appear, ensure that the environment variable is correctly named and set. Check application logs for any errors related to feature flag parsing.
- If enabling a feature causes application errors, disable the feature and contact Red Hat Support.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}