Skip to content

OCPBUGS-77078: Add MTU override for OVN-Kubernetes on hosted clusters#7942

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
jparrill:OCPBUGS-77078
Mar 31, 2026
Merged

OCPBUGS-77078: Add MTU override for OVN-Kubernetes on hosted clusters#7942
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
jparrill:OCPBUGS-77078

Conversation

@jparrill
Copy link
Copy Markdown
Contributor

@jparrill jparrill commented Mar 12, 2026

What this PR does / why we need it:

Some non-commercial AWS regions (ISO/classified) do not support the full 9001 MTU that the cluster-network-operator assumes for AWS. This PR adds a way to override the OVN-Kubernetes tunnel interface MTU through the HostedCluster API and CLI.

Changes:

  1. API: Adds an optional, immutable mtu field to OVNKubernetesConfig in spec.operatorConfiguration.clusterNetworkOperator.ovnKubernetesConfig. When set, the value is propagated to the operator.openshift.io/v1 Network resource that the CNO reads. When unset, the CNO continues to auto-detect the MTU.

  2. Reconciliation: Propagates the MTU value from the HyperShift API to the CNO operator Network resource inside the hosted cluster via ReconcileNetworkOperator().

  3. CLI: Adds --ovn-kubernetes-mtu flag to hypershift create cluster and hcp create cluster commands. The flag is validated to only work with --network-type=OVNKubernetes.

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/OCPBUGS-77078

Related PR

Special notes for your reviewer:

  • The CNO already supports the MTU field on operator.openshift.io/v1 Network.spec.defaultNetwork.ovnKubernetesConfig.mtu — no CNO changes are needed.
  • The field is immutable (CEL validation self == oldSelf) because changing tunnel MTU on a running cluster is a destructive operation.
  • Validation bounds: minimum 576 (RFC 791 IPv4 minimum), maximum 9216 (standard jumbo frame upper limit).
  • ROSA/ARO teams should be notified about this new field in case managed service admission needs to be updated.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code via /jira:solve OCPBUGS-77078

Summary by CodeRabbit

  • New Features

    • Optional OVN Kubernetes MTU (576–9216) that cannot be removed or changed once set.
    • New CLI flag to set OVN Kubernetes MTU during cluster creation (only for OVNKubernetes networks).
    • MTU is propagated into cluster/network configuration so operators receive the value.
  • Tests

    • Added unit tests covering flag validation, propagation to config, and reconciliation scenarios.

@openshift-ci-robot
Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 12, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Mar 12, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: This pull request references Jira Issue OCPBUGS-77078, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (yli2@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

What this PR does / why we need it:

Some non-commercial AWS regions (ISO/classified) do not support the full 9001 MTU that the cluster-network-operator assumes for AWS. This PR adds a way to override the OVN-Kubernetes tunnel interface MTU through the HostedCluster API and CLI.

Changes:

  1. API: Adds an optional, immutable mtu field to OVNKubernetesConfig in spec.operatorConfiguration.clusterNetworkOperator.ovnKubernetesConfig. When set, the value is propagated to the operator.openshift.io/v1 Network resource that the CNO reads. When unset, the CNO continues to auto-detect the MTU.

  2. Reconciliation: Propagates the MTU value from the HyperShift API to the CNO operator Network resource inside the hosted cluster via ReconcileNetworkOperator().

  3. CLI: Adds --ovn-kubernetes-mtu flag to hypershift create cluster and hcp create cluster commands. The flag is validated to only work with --network-type=OVNKubernetes.

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/OCPBUGS-77078

Special notes for your reviewer:

  • The CNO already supports the MTU field on operator.openshift.io/v1 Network.spec.defaultNetwork.ovnKubernetesConfig.mtu — no CNO changes are needed.
  • The field is immutable (CEL validation self == oldSelf) because changing tunnel MTU on a running cluster is a destructive operation.
  • Validation bounds: minimum 576 (RFC 791 IPv4 minimum), maximum 9216 (standard jumbo frame upper limit).
  • ROSA/ARO teams should be notified about this new field in case managed service admission needs to be updated.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code via /jira:solve OCPBUGS-77078

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 12, 2026
@openshift-ci openshift-ci Bot added do-not-merge/needs-area area/api Indicates the PR includes changes for the API area/cli Indicates the PR includes changes for CLI approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 12, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 12, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 3f0ebe1d-46e5-4149-9098-36a353cc1c76

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Adds a new public field MTU int32 to OVNKubernetesConfig with JSON tag mtu,omitempty, validations (minimum=576, maximum=9216) and XValidation immutability rules. Introduces CLI flag --ovn-kubernetes-mtu (RawCreateOptions.OVNKubernetesMTU) with validation tied to --network-type=OVNKubernetes and range checks. The flag value is propagated into HostedCluster.Spec.OperatorConfiguration.ClusterNetworkOperator.OVNKubernetesConfig.MTU on create, and the control-plane reconciler applies the MTU into the OVNKubernetes IPv4 configuration (converted to *uint32). Tests added/updated to cover validation and propagation.

Sequence Diagram

sequenceDiagram
    actor User
    participant CLI as Create CLI
    participant Validator as Create Validator
    participant API as HostedCluster API
    participant Reconciler as Network Reconciler
    participant OVN as OVN Network Operator

    User->>CLI: run create with --ovn-kubernetes-mtu=<value>
    CLI->>Validator: validate OVNKubernetesMTU with network-type and range
    Validator-->>CLI: valid / invalid
    alt valid (network-type == OVNKubernetes)
        CLI->>API: create HostedCluster with OVNKubernetesConfig.MTU (int32)
        API->>Reconciler: notify/reconcile HostedCluster
        Reconciler->>OVN: set OVNKubernetes IPv4 MTU (convert int32 to *uint32)
        OVN-->>Reconciler: confirm MTU applied
    else invalid
        Validator-->>CLI: return validation error
    end
Loading
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Structure And Quality ⚠️ Warning The PR's test code in TestOVNKubernetesMTUFlag lacks meaningful failure messages in assertions, violating the custom check requirement. Add descriptive failure messages to all assertions in TestOVNKubernetesMTUFlag to match quality standards demonstrated in other tests.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The pull request title clearly and specifically describes the main change: adding MTU override capability for OVN-Kubernetes on hosted clusters, matching the changeset content across API definitions, CLI options, validation, and reconciliation logic.
Stable And Deterministic Test Names ✅ Passed All test names are stable and deterministic using standard Go testing conventions with purely static, descriptive strings.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/documentation Indicates the PR includes changes for documentation and removed do-not-merge/needs-area labels Mar 12, 2026
@jparrill
Copy link
Copy Markdown
Contributor Author

/label tide/merge-method-squash

@openshift-ci openshift-ci Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Mar 12, 2026
@jparrill
Copy link
Copy Markdown
Contributor Author

/auto-cc

@jparrill
Copy link
Copy Markdown
Contributor Author

/test unit

@jparrill
Copy link
Copy Markdown
Contributor Author

/test verify

@openshift-ci openshift-ci Bot requested review from bryan-cox and enxebre March 12, 2026 11:44
@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: This pull request references Jira Issue OCPBUGS-77078, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (yli2@redhat.com), skipping review request.

Details

In response to this:

What this PR does / why we need it:

Some non-commercial AWS regions (ISO/classified) do not support the full 9001 MTU that the cluster-network-operator assumes for AWS. This PR adds a way to override the OVN-Kubernetes tunnel interface MTU through the HostedCluster API and CLI.

Changes:

  1. API: Adds an optional, immutable mtu field to OVNKubernetesConfig in spec.operatorConfiguration.clusterNetworkOperator.ovnKubernetesConfig. When set, the value is propagated to the operator.openshift.io/v1 Network resource that the CNO reads. When unset, the CNO continues to auto-detect the MTU.

  2. Reconciliation: Propagates the MTU value from the HyperShift API to the CNO operator Network resource inside the hosted cluster via ReconcileNetworkOperator().

  3. CLI: Adds --ovn-kubernetes-mtu flag to hypershift create cluster and hcp create cluster commands. The flag is validated to only work with --network-type=OVNKubernetes.

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/OCPBUGS-77078

Special notes for your reviewer:

  • The CNO already supports the MTU field on operator.openshift.io/v1 Network.spec.defaultNetwork.ovnKubernetesConfig.mtu — no CNO changes are needed.
  • The field is immutable (CEL validation self == oldSelf) because changing tunnel MTU on a running cluster is a destructive operation.
  • Validation bounds: minimum 576 (RFC 791 IPv4 minimum), maximum 9216 (standard jumbo frame upper limit).
  • ROSA/ARO teams should be notified about this new field in case managed service admission needs to be updated.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code via /jira:solve OCPBUGS-77078

Summary by CodeRabbit

Release Notes

  • New Features
  • Added support for configuring OVN Kubernetes network MTU via new --ovn-kubernetes-mtu CLI flag during cluster creation
  • MTU setting is immutable once configured, with supported range of 576-9216 bytes
  • MTU configuration is only valid when using OVNKubernetes as the network type

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Comment thread cmd/cluster/core/create_test.go
Comment thread api/hypershift/v1beta1/operator.go Outdated
@enxebre
Copy link
Copy Markdown
Member

enxebre commented Mar 12, 2026

Thanks! two small comments, lgtm otherwise

@openshift-ci openshift-ci Bot added the area/platform/aws PR/issue for AWS (AWSPlatform) platform label Mar 12, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
cmd/cluster/aws/create_test.go (1)

220-232: Consider adding explicit --network-type=OVNKubernetes for clarity.

The test relies on the default NetworkType being OVNKubernetes. While validation will pass, explicitly including the flag would:

  1. Match the pattern used in core validation tests
  2. Make the test intent clearer
  3. Protect against future changes to the default network type
💡 Suggested improvement
 		{
 			name: "minimal with OVNKubernetesMTU",
 			args: []string{
 				"--name=example",
 				"--sts-creds=" + credentialsFile,
 				"--infra-json=" + infraFile,
 				"--iam-json=" + iamFile,
 				"--role-arn=fakeRoleARN",
 				"--pull-secret=" + pullSecretFile,
 				"--render-sensitive",
+				"--network-type=OVNKubernetes",
 				"--ovn-kubernetes-mtu=1400",
 			},
 		},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/cluster/aws/create_test.go` around lines 220 - 232, The test case named
"minimal with OVNKubernetesMTU" relies on the default NetworkType; update its
args slice to include the explicit flag "--network-type=OVNKubernetes" so the
test intent is obvious and resilient to default changes — locate the test case
with name "minimal with OVNKubernetesMTU" in create_test.go and add the
"--network-type=OVNKubernetes" entry alongside the existing args (e.g., near
"--ovn-kubernetes-mtu=1400").
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@cmd/cluster/aws/create_test.go`:
- Around line 220-232: The test case named "minimal with OVNKubernetesMTU"
relies on the default NetworkType; update its args slice to include the explicit
flag "--network-type=OVNKubernetes" so the test intent is obvious and resilient
to default changes — locate the test case with name "minimal with
OVNKubernetesMTU" in create_test.go and add the "--network-type=OVNKubernetes"
entry alongside the existing args (e.g., near "--ovn-kubernetes-mtu=1400").

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 663e1202-9aae-4cba-b86b-eaa1a8a78fb6

📥 Commits

Reviewing files that changed from the base of the PR and between 16c5ff3 and 90c666f.

⛔ Files ignored due to path filters (1)
  • cmd/cluster/aws/testdata/zz_fixture_TestCreateCluster_minimal_with_OVNKubernetesMTU.yaml is excluded by !**/testdata/**
📒 Files selected for processing (3)
  • cmd/cluster/aws/create_test.go
  • cmd/cluster/core/create.go
  • cmd/cluster/core/create_test.go
🚧 Files skipped from review as they are similar to previous changes (2)
  • cmd/cluster/core/create.go
  • cmd/cluster/core/create_test.go

@enxebre
Copy link
Copy Markdown
Member

enxebre commented Mar 12, 2026

Let's hold on merging this until the CNO counterpart changes are in place if any is needed https://github.com/openshift/cluster-network-operator/blob/9d540eb7929f83879d3dafbcd1ae6cb1feca36b3/pkg/controller/operconfig/mtu_probe.go#L38-L42

@jparrill
Copy link
Copy Markdown
Contributor Author

Rebase due to conflicts

@enxebre
Copy link
Copy Markdown
Member

enxebre commented Mar 27, 2026

/approve
commits seems mixed up e.g. c17c1e8#diff-ceacf0d077810c445b92562a07c0f59a2cea9607f16354a3a469db6e586ea52a
let's squash
/label tide/merge-method-squash

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 27, 2026
Copy link
Copy Markdown
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

For API review

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre, JoelSpeed, jparrill

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jparrill
Copy link
Copy Markdown
Contributor Author

/test e2e-aks

@jparrill
Copy link
Copy Markdown
Contributor Author

/retest-required

Non related infra failure

@jparrill
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: This pull request references Jira Issue OCPBUGS-77078, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wewang58

Details

In response to this:

What this PR does / why we need it:

Some non-commercial AWS regions (ISO/classified) do not support the full 9001 MTU that the cluster-network-operator assumes for AWS. This PR adds a way to override the OVN-Kubernetes tunnel interface MTU through the HostedCluster API and CLI.

Changes:

  1. API: Adds an optional, immutable mtu field to OVNKubernetesConfig in spec.operatorConfiguration.clusterNetworkOperator.ovnKubernetesConfig. When set, the value is propagated to the operator.openshift.io/v1 Network resource that the CNO reads. When unset, the CNO continues to auto-detect the MTU.

  2. Reconciliation: Propagates the MTU value from the HyperShift API to the CNO operator Network resource inside the hosted cluster via ReconcileNetworkOperator().

  3. CLI: Adds --ovn-kubernetes-mtu flag to hypershift create cluster and hcp create cluster commands. The flag is validated to only work with --network-type=OVNKubernetes.

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/OCPBUGS-77078

Related PR

Special notes for your reviewer:

  • The CNO already supports the MTU field on operator.openshift.io/v1 Network.spec.defaultNetwork.ovnKubernetesConfig.mtu — no CNO changes are needed.
  • The field is immutable (CEL validation self == oldSelf) because changing tunnel MTU on a running cluster is a destructive operation.
  • Validation bounds: minimum 576 (RFC 791 IPv4 minimum), maximum 9216 (standard jumbo frame upper limit).
  • ROSA/ARO teams should be notified about this new field in case managed service admission needs to be updated.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code via /jira:solve OCPBUGS-77078

Summary by CodeRabbit

  • New Features

  • Optional OVN Kubernetes MTU (576–9216) that cannot be removed or changed once set.

  • New CLI flag to set OVN Kubernetes MTU during cluster creation (only for OVNKubernetes networks).

  • MTU is propagated into cluster/network configuration so operators receive the value.

  • Tests

  • Added unit tests covering flag validation, propagation to config, and reconciliation scenarios.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 30, 2026

Codecov Report

❌ Patch coverage is 84.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 26.57%. Comparing base (c503233) to head (c17c1e8).
⚠️ Report is 52 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7942      +/-   ##
==========================================
+ Coverage   26.56%   26.57%   +0.01%     
==========================================
  Files        1087     1087              
  Lines      105041   105066      +25     
==========================================
+ Hits        27901    27922      +21     
- Misses      74731    74735       +4     
  Partials     2409     2409              
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@wewang58
Copy link
Copy Markdown
Contributor

/verified by @wewang58

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@wewang58: This PR has been marked as verified by @wewang58.

Details

In response to this:

/verified by @wewang58

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 31, 2026

@jparrill: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot Bot merged commit 7ce6015 into openshift:main Mar 31, 2026
30 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: Jira Issue OCPBUGS-77078: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-77078 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

What this PR does / why we need it:

Some non-commercial AWS regions (ISO/classified) do not support the full 9001 MTU that the cluster-network-operator assumes for AWS. This PR adds a way to override the OVN-Kubernetes tunnel interface MTU through the HostedCluster API and CLI.

Changes:

  1. API: Adds an optional, immutable mtu field to OVNKubernetesConfig in spec.operatorConfiguration.clusterNetworkOperator.ovnKubernetesConfig. When set, the value is propagated to the operator.openshift.io/v1 Network resource that the CNO reads. When unset, the CNO continues to auto-detect the MTU.

  2. Reconciliation: Propagates the MTU value from the HyperShift API to the CNO operator Network resource inside the hosted cluster via ReconcileNetworkOperator().

  3. CLI: Adds --ovn-kubernetes-mtu flag to hypershift create cluster and hcp create cluster commands. The flag is validated to only work with --network-type=OVNKubernetes.

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/OCPBUGS-77078

Related PR

Special notes for your reviewer:

  • The CNO already supports the MTU field on operator.openshift.io/v1 Network.spec.defaultNetwork.ovnKubernetesConfig.mtu — no CNO changes are needed.
  • The field is immutable (CEL validation self == oldSelf) because changing tunnel MTU on a running cluster is a destructive operation.
  • Validation bounds: minimum 576 (RFC 791 IPv4 minimum), maximum 9216 (standard jumbo frame upper limit).
  • ROSA/ARO teams should be notified about this new field in case managed service admission needs to be updated.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code via /jira:solve OCPBUGS-77078

Summary by CodeRabbit

  • New Features

  • Optional OVN Kubernetes MTU (576–9216) that cannot be removed or changed once set.

  • New CLI flag to set OVN Kubernetes MTU during cluster creation (only for OVNKubernetes networks).

  • MTU is propagated into cluster/network configuration so operators receive the value.

  • Tests

  • Added unit tests covering flag validation, propagation to config, and reconciliation scenarios.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jparrill
Copy link
Copy Markdown
Contributor Author

/jira backport release-4.21

@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21

Details

In response to this:

/jira backport release-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-ci-robot: #7942 failed to apply on top of branch "release-4.21":

Applying: feat(api): add MTU field to OVNKubernetesConfig for hosted clusters
Applying: chore(generated): regenerate CRDs, clients, vendor, and docs
Using index info to reconstruct a base tree...
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/AAA_ungated.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/AutoNodeKarpenter.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ClusterVersionOperatorConfiguration.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDC.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDCWithUIDAndExtraClaimMappings.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/GCPPlatform.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/HCPEtcdBackup.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/HyperShiftOnlyDynamicResourceAllocation.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ImageStreamImportMode.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/KMSEncryptionProvider.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/OpenStack.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/AAA_ungated.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/AutoNodeKarpenter.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ClusterVersionOperatorConfiguration.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDC.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDCWithUIDAndExtraClaimMappings.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/GCPPlatform.yaml
A	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/HCPEtcdBackup.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/HyperShiftOnlyDynamicResourceAllocation.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ImageStreamImportMode.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/KMSEncryptionProvider.yaml
M	api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/OpenStack.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-CustomNoUpgrade.crd.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-Default.crd.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-TechPreviewNoUpgrade.crd.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-CustomNoUpgrade.crd.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-Default.crd.yaml
M	cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-TechPreviewNoUpgrade.crd.yaml
A	docs/content/reference/aggregated-docs.md
M	docs/content/reference/api.md
Falling back to patching base and 3-way merge...
Auto-merging docs/content/reference/api.md
CONFLICT (modify/delete): docs/content/reference/aggregated-docs.md deleted in HEAD and modified in chore(generated): regenerate CRDs, clients, vendor, and docs. Version chore(generated): regenerate CRDs, clients, vendor, and docs of docs/content/reference/aggregated-docs.md left in tree.
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-TechPreviewNoUpgrade.crd.yaml
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-Default.crd.yaml
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedcontrolplanes-Hypershift-CustomNoUpgrade.crd.yaml
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-TechPreviewNoUpgrade.crd.yaml
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-Default.crd.yaml
Auto-merging cmd/install/assets/hypershift-operator/zz_generated.crd-manifests/hostedclusters-Hypershift-CustomNoUpgrade.crd.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/OpenStack.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/NetworkDiagnosticsConfig.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/KMSEncryptionProvider.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ImageStreamImportMode.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/HyperShiftOnlyDynamicResourceAllocation.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/GCPPlatform.yaml
CONFLICT (modify/delete): api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml deleted in HEAD and modified in chore(generated): regenerate CRDs, clients, vendor, and docs. Version chore(generated): regenerate CRDs, clients, vendor, and docs of api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml left in tree.
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDCWithUIDAndExtraClaimMappings.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ExternalOIDC.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ClusterVersionOperatorConfiguration.yaml
CONFLICT (modify/delete): api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml deleted in HEAD and modified in chore(generated): regenerate CRDs, clients, vendor, and docs. Version chore(generated): regenerate CRDs, clients, vendor, and docs of api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml left in tree.
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/AutoNodeKarpenter.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedcontrolplanes.hypershift.openshift.io/AAA_ungated.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/OpenStack.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/NetworkDiagnosticsConfig.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/KMSEncryptionProvider.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ImageStreamImportMode.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/HyperShiftOnlyDynamicResourceAllocation.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/GCPPlatform.yaml
CONFLICT (modify/delete): api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml deleted in HEAD and modified in chore(generated): regenerate CRDs, clients, vendor, and docs. Version chore(generated): regenerate CRDs, clients, vendor, and docs of api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDCWithUpstreamParity.yaml left in tree.
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDCWithUIDAndExtraClaimMappings.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ExternalOIDC.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ClusterVersionOperatorConfiguration.yaml
CONFLICT (modify/delete): api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml deleted in HEAD and modified in chore(generated): regenerate CRDs, clients, vendor, and docs. Version chore(generated): regenerate CRDs, clients, vendor, and docs of api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/ClusterUpdateAcceptRisks.yaml left in tree.
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/AutoNodeKarpenter.yaml
Auto-merging api/hypershift/v1beta1/zz_generated.featuregated-crd-manifests/hostedclusters.hypershift.openshift.io/AAA_ungated.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 chore(generated): regenerate CRDs, clients, vendor, and docs

Details

In response to this:

@jparrill: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21

In response to this:

/jira backport release-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

jparrill added a commit to jparrill/hypershift that referenced this pull request Mar 31, 2026
Backport of PR openshift#7942 to release-4.21.

Some non-commercial AWS regions do not support the full 9001 MTU that
the cluster-network-operator assumes for AWS. This adds an optional,
immutable mtu field to the HyperShift OVNKubernetesConfig API type,
allowing users to override the tunnel interface MTU at cluster creation
time.

The field is propagated through ReconcileNetworkOperator to the
operator.openshift.io/v1 Network resource, which the CNO already
supports. When unset, the CNO continues to auto-detect the MTU.

Also adds --ovn-kubernetes-mtu CLI flag and regenerates CRDs/docs.

Squashed commits:
* feat(api): add MTU field to OVNKubernetesConfig for hosted clusters
* chore(generated): regenerate CRDs, clients, vendor, and docs
* feat(cli): add --ovn-kubernetes-mtu flag to hypershift create cluster
* chore(generated): add TestCreateCluster fixture for OVNKubernetesMTU

Ref: https://issues.redhat.com/browse/OCPBUGS-77078
Ref: https://issues.redhat.com/browse/OCPBUGS-81489

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>
jparrill added a commit to jparrill/hypershift that referenced this pull request Apr 6, 2026
Backport of PR openshift#7942 to release-4.21.

Some non-commercial AWS regions do not support the full 9001 MTU that
the cluster-network-operator assumes for AWS. This adds an optional,
immutable mtu field to the HyperShift OVNKubernetesConfig API type,
allowing users to override the tunnel interface MTU at cluster creation
time.

The field is propagated through ReconcileNetworkOperator to the
operator.openshift.io/v1 Network resource, which the CNO already
supports. When unset, the CNO continues to auto-detect the MTU.

Also adds --ovn-kubernetes-mtu CLI flag and regenerates CRDs/docs.

Squashed commits:
* feat(api): add MTU field to OVNKubernetesConfig for hosted clusters
* chore(generated): regenerate CRDs, clients, vendor, and docs
* feat(cli): add --ovn-kubernetes-mtu flag to hypershift create cluster
* chore(generated): add TestCreateCluster fixture for OVNKubernetesMTU

Ref: https://issues.redhat.com/browse/OCPBUGS-77078
Ref: https://issues.redhat.com/browse/OCPBUGS-81489

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>
jparrill added a commit to jparrill/hypershift that referenced this pull request Apr 6, 2026
Backport of PR openshift#7942 to release-4.21.

Some non-commercial AWS regions do not support the full 9001 MTU that
the cluster-network-operator assumes for AWS. This adds an optional,
immutable mtu field to the HyperShift OVNKubernetesConfig API type,
allowing users to override the tunnel interface MTU at cluster creation
time.

The field is propagated through ReconcileNetworkOperator to the
operator.openshift.io/v1 Network resource, which the CNO already
supports. When unset, the CNO continues to auto-detect the MTU.

Also adds --ovn-kubernetes-mtu CLI flag and regenerates CRDs/docs.

Squashed commits:
* feat(api): add MTU field to OVNKubernetesConfig for hosted clusters
* chore(generated): regenerate CRDs, clients, vendor, and docs
* feat(cli): add --ovn-kubernetes-mtu flag to hypershift create cluster
* chore(generated): add TestCreateCluster fixture for OVNKubernetesMTU

Ref: https://issues.redhat.com/browse/OCPBUGS-77078
Ref: https://issues.redhat.com/browse/OCPBUGS-81489

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>
@jparrill
Copy link
Copy Markdown
Contributor Author

jparrill commented Apr 7, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: Jira Issue Verification Checks: Jira Issue OCPBUGS-77078
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-77078 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

mehabhalodiya pushed a commit to mehabhalodiya/hypershift that referenced this pull request Apr 13, 2026
…openshift#7942)

* feat(api): add MTU field to OVNKubernetesConfig for hosted clusters

Some non-commercial AWS regions do not support the full 9001 MTU that
the cluster-network-operator assumes for AWS. This adds an optional,
immutable mtu field to the HyperShift OVNKubernetesConfig API type,
allowing users to override the tunnel interface MTU at cluster creation
time.

The field is propagated through ReconcileNetworkOperator to the
operator.openshift.io/v1 Network resource, which the CNO already
supports. When unset, the CNO continues to auto-detect the MTU.

Ref: https://issues.redhat.com/browse/OCPBUGS-77078

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

* chore(generated): regenerate CRDs, clients, vendor, and docs

Regenerate after adding the mtu field to OVNKubernetesConfig.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

* feat(cli): add --ovn-kubernetes-mtu flag to hypershift create cluster

Adds a new --ovn-kubernetes-mtu flag that allows users to specify the
OVN-Kubernetes tunnel interface MTU when creating a hosted cluster.
This is needed for non-commercial AWS regions that do not support
the full 9001 MTU that the cluster-network-operator assumes.

The flag is only valid when --network-type is OVNKubernetes and
validation enforces this constraint.

Ref: https://issues.redhat.com/browse/OCPBUGS-77078

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

* chore(generated): add TestCreateCluster fixture for OVNKubernetesMTU

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

---------

Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/api Indicates the PR includes changes for the API area/cli Indicates the PR includes changes for CLI area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/documentation Indicates the PR includes changes for documentation area/platform/aws PR/issue for AWS (AWSPlatform) platform jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants