apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "23121"
    uid: c65bab97-5c13-46c6-83c8-dc89ff2dc4cc
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:38:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.372996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:38:33Z"
    - latency: 1.12286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 916.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 1.271445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 1.060971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 2.127884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 969.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "21580"
    uid: ac9adfbb-af12-4b24-b4c5-da8d45e9bad8
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:37:33Z"
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.95425ms
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 10.716578ms
      message: 'load-balancer-api-external: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 6.335167ms
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 8.911919ms
      message: 'load-balancer-api-external: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 5.518612ms
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 6.489643ms
      message: 'load-balancer-api-external: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 4.500079ms
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 8.686153ms
      message: 'load-balancer-api-external: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 6.70392ms
      message: 'load-balancer-api-external: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 9.146089ms
      message: 'load-balancer-api-external: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "21579"
    uid: 6b2175d3-ad32-4d90-b484-ac56e8f1097c
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:37:33Z"
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.435012ms
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 10.855257ms
      message: 'load-balancer-api-internal: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 5.568231ms
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 8.879908ms
      message: 'load-balancer-api-internal: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 9.207011ms
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 6.584233ms
      message: 'load-balancer-api-internal: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 4.498531ms
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 8.751249ms
      message: 'load-balancer-api-internal: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 4.151728ms
      message: 'load-balancer-api-internal: tcp connection to af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 8.852397ms
      message: 'load-balancer-api-internal: resolved host name af0dc1271ebda49d09c685ad39ea6cfa-5e5dfb0a9a9b06dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-130-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "23118"
    uid: 4800328e-1bb7-4839-b629-9386d05a2b9a
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:38:33Z"
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 789.854µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:38:33Z"
    - latency: 2.031168ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 950.888µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 886.172µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 1.150988ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 1.360144ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 1.307937ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-137-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "23119"
    uid: 9ffbb249-c4c4-4ce6-89ec-bc8607bd95fb
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:38:33Z"
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.789788ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:38:33Z"
    - latency: 2.756367ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 2.481032ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 2.270565ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 1.797966ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 2.177641ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 1.963765ms
      message: 'network-check-target-ip-10-0-137-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-143-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "23120"
    uid: 1ccb2288-d332-427c-9cde-82b2bfbef719
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:38:33Z"
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.317486ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:38:33Z"
    - latency: 2.398269ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 2.543375ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 2.13954ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 2.168732ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 2.495788ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 2.205292ms
      message: 'network-check-target-ip-10-0-143-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:31:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: d31cad12-1a45-45d8-835d-f285f664b79b
    resourceVersion: "21578"
    uid: c8454885-169f-432b-8b82-f6a222587f72
  spec:
    sourcePod: network-check-source-65bdbbff45-rp5gb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:37:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.543025ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 2.180497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:37:33Z"
    - latency: 1.205064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 1.66096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:36:33Z"
    - latency: 1.103409ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 1.946886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:35:33Z"
    - latency: 942.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 1.825924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:33Z"
    - latency: 989.297µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:33Z"
    - latency: 3.040555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:33Z"
kind: List
metadata:
  resourceVersion: ""