apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "21933"
    uid: abb4978e-a004-412f-98aa-b3f553a2e46f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:37:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:37:08Z"
    - latency: 1.242608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 976.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 1.445528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 1.222913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 1.729301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 996.407µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "20623"
    uid: e2b40ad8-4bbb-46cc-8e5b-c38d0f704e7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:36:08Z"
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.078584ms
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 7.13359ms
      message: 'load-balancer-api-external: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 5.155755ms
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 7.493802ms
      message: 'load-balancer-api-external: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 8.685025ms
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 10.535366ms
      message: 'load-balancer-api-external: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 4.958449ms
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 9.255496ms
      message: 'load-balancer-api-external: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 4.145014ms
      message: 'load-balancer-api-external: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 13.57289ms
      message: 'load-balancer-api-external: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "20624"
    uid: 4d4d6c67-58d5-48a0-ba46-7af41f403def
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:36:08Z"
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.023378ms
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 7.149556ms
      message: 'load-balancer-api-internal: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 5.144014ms
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 7.440469ms
      message: 'load-balancer-api-internal: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 3.996362ms
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 10.317815ms
      message: 'load-balancer-api-internal: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 4.981265ms
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 9.349959ms
      message: 'load-balancer-api-internal: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 4.943953ms
      message: 'load-balancer-api-internal: tcp connection to a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 13.525946ms
      message: 'load-balancer-api-internal: resolved host name a790ac6a5a8174191adca88201463631-8332c12d6ae82c9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-network-check-target-ip-10-0-137-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "21932"
    uid: 7fcd17ef-5ef4-4b17-97a6-bf2865b67174
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:37:08Z"
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.189257ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:37:08Z"
    - latency: 2.226542ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 2.012367ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 2.887087ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 1.946688ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 3.181451ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 2.231913ms
      message: 'network-check-target-ip-10-0-137-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-network-check-target-ip-10-0-139-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "21931"
    uid: 1940d3a3-57f7-46a0-ad56-097bcc80f9f1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:37:08Z"
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.614µs
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:37:08Z"
    - latency: 950.677µs
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 856.475µs
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 2.454949ms
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 897.632µs
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 1.051747ms
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 1.324917ms
      message: 'network-check-target-ip-10-0-139-203: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-network-check-target-ip-10-0-139-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "21934"
    uid: 50a17ef7-498e-49ff-ba97-ec1a766d8e30
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:37:08Z"
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 20.216088ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:37:08Z"
    - latency: 2.545296ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 2.02671ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 2.787095ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 2.093317ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 2.468505ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 2.453988ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:30:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-203-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-203.ec2.internal
      uid: 08a08f57-25ed-4019-8524-ad609577b9ac
    resourceVersion: "20622"
    uid: 6d267971-eba5-49a2-9b48-ec0afc16c004
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9pdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:36:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 914.479µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 1.841671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:36:08Z"
    - latency: 897.339µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 2.011254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:35:08Z"
    - latency: 1.29664ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 2.503813ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:34:08Z"
    - latency: 1.01177ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 1.883905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:33:08Z"
    - latency: 1.005205ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:32:08Z"
    - latency: 2.394862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:32:08Z"
kind: List
metadata:
  resourceVersion: ""