apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "15247"
    uid: 92963f35-65e2-4a90-a313-ab9cfad46c94
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.134425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:33:56Z"
    - latency: 1.39407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 883.785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 1.08375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 967.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 908.202µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 931.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:27:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "14838"
    uid: 89a16bbb-5e76-4ef8-b0c8-9e59bbfc57c8
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:56Z"
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.283057ms
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 9.107439ms
      message: 'load-balancer-api-external: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 4.368579ms
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 8.580179ms
      message: 'load-balancer-api-external: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 4.623951ms
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 8.331992ms
      message: 'load-balancer-api-external: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 4.20098ms
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 9.181073ms
      message: 'load-balancer-api-external: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 5.182469ms
      message: 'load-balancer-api-external: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 8.105249ms
      message: 'load-balancer-api-external: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "14839"
    uid: 4f08762a-6ef3-41bb-a19f-7a57df14e325
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:56Z"
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.127722ms
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 9.058793ms
      message: 'load-balancer-api-internal: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 4.551053ms
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 8.686919ms
      message: 'load-balancer-api-internal: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 4.306209ms
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 8.283222ms
      message: 'load-balancer-api-internal: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 4.249712ms
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 9.016273ms
      message: 'load-balancer-api-internal: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 5.112729ms
      message: 'load-balancer-api-internal: tcp connection to a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 8.150892ms
      message: 'load-balancer-api-internal: resolved host name a4a9610ea1cfc4c8c8997b77ed047324-1f94e0a4db84e71f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-network-check-target-ip-10-0-129-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "15245"
    uid: 461fdd1d-83d3-468c-9a79-52a2f5916993
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:56Z"
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.013286ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:33:56Z"
    - latency: 2.05534ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 1.506758ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 1.986153ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 1.92421ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 2.015083ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 1.873882ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:27:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-network-check-target-ip-10-0-131-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "15244"
    uid: e7fb0730-a6e9-485a-8804-eb7033eb1214
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:56Z"
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.295024ms
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:33:56Z"
    - latency: 1.43123ms
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 820.698µs
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 834.436µs
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 865.216µs
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 945.801µs
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 1.088455ms
      message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:27:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-network-check-target-ip-10-0-141-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "15246"
    uid: bf8712d9-cf8e-4c75-9b37-82902861a731
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:56Z"
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.628431ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:33:56Z"
    - latency: 2.370045ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 2.093884ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 2.426058ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 2.481626ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 2.561549ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 2.274651ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:27:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-103-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-103.ec2.internal
      uid: 47ab94c9-a401-442c-866d-c883e50c4f92
    resourceVersion: "14837"
    uid: 5a1fadb8-9770-42c6-8475-935c8d5b4abf
  spec:
    sourcePod: network-check-source-7d88cb55d8-q9qpn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 1.895391ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:32:56Z"
    - latency: 878.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 1.701913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:31:56Z"
    - latency: 1.258659ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 1.866279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:30:56Z"
    - latency: 1.175562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 2.124919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:29:56Z"
    - latency: 1.316585ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:28:56Z"
    - latency: 1.941589ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:28:56Z"
kind: List
metadata:
  resourceVersion: ""