此内容没有您所选择的语言版本。

Chapter 10. Using feature gates to develop solutions for your applications


Use feature gates to test new Kubernetes features for potential use in your MicroShift deployments.

10.1. Understanding feature gates for MicroShift

As an application developer for edge computing environments, you can now experiment with upcoming Kubernetes features to evaluate their potential benefits for specific use cases.

By using feature gates, you can test various enhancements that might improve performance in your resource-constrained edge environments. For example, you can try advanced CPU management, enhanced scheduling features, or experimental storage options.

Warning

When you trial new features using feature gates, your MicroShift can become unstable or lose data. Enable feature gates only in non-production environments.

When planning to use feature gates for development, consider the following details:

  • After you specify feature gates, you cannot update MicroShift.
  • If your configuration is not valid, MicroShift can fail to start.
  • The Kubernetes components you enable handle feature gate validation.
  • Feature gates are disabled by default in MicroShift. After you enable feature gates, you cannot disable them.

10.2. Using feature gates for MicroShift

To use feature gates in your development environment, you must specify them in the config.yaml file or create a configuration snippet file. You must also configure the feature set you want to work with.

Important
  • A config.yaml configuration file takes precedence over built-in settings. The config.yaml file is read every time the MicroShift service starts.
  • Configuration snippet YAMLs take precedence over both built-in settings and the config.yaml configuration file.
  • After you enable feature gates, you cannot disable them.

Prerequisites

  • You installed MicroShift.
  • You installed the OpenShift CLI (oc).
  • You have sudo privileges on the MicroShift host.

Procedure

  1. Apply features gates in one of the two following ways:

    1. Update the MicroShift config.yaml configuration file by making a copy of the provided config.yaml.default file in the /etc/microshift/ directory. Name it config.yaml and keep it in the source directory.
    2. Use a configuration snippet to apply the ingress control settings you want. To do this, create a configuration snippet YAML file and put it in the /etc/microshift/config.d/ configuration directory. For example, /etc/microshift/config.d/10-feature-gate.yaml.
  2. Replace the default values in the xyz section of the MicroShift YAML with your valid values, or create a configuration snippet file with the sections you need.

    Feature gates configuration with example values

    # ...
    apiServer:
      featureGates:
        featureSet: TechPreviewNoUpgrade
    # ...
    apiServer:
      featureGates:
        featureSet: CustomNoUpgrade
        customNoUpgrade:
          enabled:
          - "CPUManagerPolicyAlphaOptions"
          - "MemoryQoS"
          disabled:
          - "SomeDefaultEnabledFeature"
    # ...
    Copy to Clipboard Toggle word wrap

  3. Use the following configuration rules:

    1. You must set the featureSet field when configuring feature gates.
    2. When you use customNoUpgrade feature, you must set the featureSet to CustomNoUpgrade. The customNoUpgrade field is only valid when featureSet: CustomNoUpgrade.
  4. Configure any settings required for the feature set you want to work with.
  5. Restart MicroShift to apply the configuration changes by running the following command:

    $ sudo systemctl restart microshift
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部