이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동