apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14996"
    uid: d8329d96-f2ca-4bc7-a486-04107c5258ff
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:57:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:57:34Z"
    - latency: 998.462µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 1.057157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 758.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 850.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 1.011729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 883.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14557"
    uid: 3a32095d-256d-4f7e-b7d6-828d12ec6607
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:56:34Z"
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.353921ms
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 7.600787ms
      message: 'load-balancer-api-external: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 5.414543ms
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 8.408091ms
      message: 'load-balancer-api-external: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 4.174896ms
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 8.933967ms
      message: 'load-balancer-api-external: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 4.053387ms
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 8.585412ms
      message: 'load-balancer-api-external: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 5.60806ms
      message: 'load-balancer-api-external: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 9.38762ms
      message: 'load-balancer-api-external: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:52:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14558"
    uid: d3a3712e-6740-441a-9ad6-1cfe425d0cf4
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:56:34Z"
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.134211ms
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 7.54235ms
      message: 'load-balancer-api-internal: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 6.279645ms
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 8.331537ms
      message: 'load-balancer-api-internal: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 6.093639ms
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 8.946342ms
      message: 'load-balancer-api-internal: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 4.367372ms
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 8.626353ms
      message: 'load-balancer-api-internal: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 5.583645ms
      message: 'load-balancer-api-internal: tcp connection to aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 9.363917ms
      message: 'load-balancer-api-internal: resolved host name aa25895405ce44f7abf9e41427d578cc-d595dccb80320bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:52:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-network-check-target-ip-10-0-134-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14995"
    uid: e09ec0e0-8eec-4c58-bb76-7207de05cf0f
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:57:34Z"
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.978797ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:57:34Z"
    - latency: 2.160904ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 2.21495ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 2.170704ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 2.272375ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 2.176283ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 2.099927ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-network-check-target-ip-10-0-134-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14993"
    uid: 14d236bb-51cf-4cff-85bd-f687224caad6
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:57:34Z"
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.499µs
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:57:34Z"
    - latency: 822.101µs
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 1.043064ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 829.476µs
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 879.616µs
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 1.573374ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 1.129933ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-network-check-target-ip-10-0-139-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14994"
    uid: a6d65dfa-5a14-4e9d-9f6b-499fc349aaef
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:57:34Z"
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.107427ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:57:34Z"
    - latency: 1.946321ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 2.113686ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 2.026715ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 1.993339ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 1.941983ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 2.11153ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:50:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-243-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-243.ec2.internal
      uid: 773e8315-6101-4b88-b4bb-f9aa06967482
    resourceVersion: "14556"
    uid: d62c171e-2df8-4971-b6c0-a406a8c4ab7f
  spec:
    sourcePod: network-check-source-685456655f-9hhrp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:56:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 1.650968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:56:34Z"
    - latency: 992.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 1.555395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:55:34Z"
    - latency: 907.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 2.262921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:54:34Z"
    - latency: 955.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 1.577104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:53:34Z"
    - latency: 831.559µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:52:34Z"
    - latency: 2.427855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:52:34Z"
kind: List
metadata:
  resourceVersion: ""