Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. Deploy OCP with 500 worker nodes

2. Create workload with 45,000 pods

3. Execute SDN to OVN live migration

Actual results:

• About workloads in OCP with OVN network when executing SDN to OVN live migration in OCP with 500 worker nodes
• Creating 4500 NS and 27,000 Pods, the migration is very smooth if less than 30,0000 Pods, it takes about 19 hours to complete. application is inaccessible time is 15 minutes(kube-apiserver can be accessible in the meantime)
• Creating 4500 NS and 36, 000 pods, The migration will take a very long time, but it's possible to successfully migrate, it  takes about 48 hours to complete(estimate), or more time. canceled the testing due to high cost. application is inaccessible time is 76 minutes(kube-apiserver can be accessible)
• Creating 4500 NS and 45,000 pods. after 45,000 pods created.  we couldn't create additional pods using kube-burner, it shows the cluster is unhealthy.
• The offline migration created 2004NS, 20,000 Pods Offline SDN migration: Scale Testing 
• The doc mentioned max is 150,000 pods planning-your-environment-according-to-object-maximums#cluster-maximums-major-releases_object-limits, the loaded upgrade or migration maybe have potential risk if create more than 45,000 pods
• Question - Do we need to test how many pods that OCP can support in OVN-Network? Any suggestions? 

Expected results:

                     Do we need to test how many pods that OCP can support in OVN-Network? Any suggestions? 

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms:

Is it an

1. internal CI failure
2. customer issue / SD
3. internal RedHat testing failure

If it is an internal RedHat testing failure:

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure:

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components