1.  It must be a bug/performance issue or a feature request or a build issue or
    a documentation issue (for small doc fixes please send a PR instead).
1.  Make sure the Issue Template is filled out.
1.  The issue should be related to the repo it is created in.

**Here's why we have this policy:** We want to focus on the work that benefits
the whole community, e.g., fixing bugs and adding features. Individual support

    List<Feature<?>> features = new ArrayList<>(parentBuilder.getFeatures());
    Set<Method> suppressing = new HashSet<>(parentBuilder.getSuppressedTests());
    features.add(CollectionFeature.SUBSET_VIEW);
    if (features.remove(CollectionFeature.ALLOWS_NULL_VALUES)) {
      // the null value might be out of bounds, so we can't always construct a subset with nulls
      features.add(CollectionFeature.ALLOWS_NULL_QUERIES);

    List<Feature<?>> features = new ArrayList<>(parentBuilder.getFeatures());
    Set<Method> suppressing = new HashSet<>(parentBuilder.getSuppressedTests());
    features.add(CollectionFeature.SUBSET_VIEW);
    if (features.remove(CollectionFeature.ALLOWS_NULL_VALUES)) {
      // the null value might be out of bounds, so we can't always construct a subset with nulls
      features.add(CollectionFeature.ALLOWS_NULL_QUERIES);

import org.graalvm.nativeimage.hosted.Feature
import org.graalvm.nativeimage.hosted.RuntimeResourceAccess

/**
 * Automatic configuration of OkHttp for native images.
 *
 * Currently, includes all necessary resources.
 */
class OkHttpFeature : Feature {
  @IgnoreJRERequirement
  override fun beforeAnalysis(access: Feature.BeforeAnalysisAccess?) {
    RuntimeResourceAccess.addResource(

- The `CSIMigrationAzureFile` feature gate (for the feature which graduated to GA in v1.26) is now unconditionally enabled and will be removed in v1.28. ([#114953](https://github.com/kubernetes/kubernetes/pull/114953), [@enj](https://github.com/enj))

$ cd minio
$ git remote add upstream https://github.com/minio/minio
$ git fetch upstream
$ git merge upstream/master
...
```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

import static com.google.common.collect.testing.features.FeatureUtil.getTesterAnnotations;
import static com.google.common.collect.testing.features.FeatureUtil.impliedFeatures;
import static com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.BAR;
import static com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.FOO;

import static com.google.common.collect.testing.features.FeatureUtil.getTesterAnnotations;
import static com.google.common.collect.testing.features.FeatureUtil.impliedFeatures;
import static com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.BAR;
import static com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.FOO;

- RemoteCommand feature gates for kubectl exec, cp, and attach over WebSockets are now enabled by default (Beta):
  - Server-side feature gate: `TranslateStreamCloseWebsocketRequests`
  - Client-side (kubectl) feature gate: `KUBECTL_REMOTE_COMMAND_WEBSOCKETS`

## How to test this PR?


## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Optimization (provides speedup with no functional changes)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

## Checklist:
- [ ] Fixes a regression (If yes, please add `commit-id` or `PR #` here)