apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "21411"
    uid: 01506a2b-6e9c-4c89-aefc-2aca7451ca69
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:40:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:20Z"
    - latency: 1.511143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 1.444612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 879.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 1.444464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 825.821µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 1.018805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "20171"
    uid: d6e74a5b-24f8-4342-a561-f7522cb91ab8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:39:20Z"
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.207434ms
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 7.260964ms
      message: 'load-balancer-api-external: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 10.214953ms
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 10.988748ms
      message: 'load-balancer-api-external: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 3.937634ms
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 7.297234ms
      message: 'load-balancer-api-external: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 4.949605ms
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 8.421056ms
      message: 'load-balancer-api-external: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 3.504578ms
      message: 'load-balancer-api-external: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 8.061617ms
      message: 'load-balancer-api-external: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "20170"
    uid: 1691c781-df66-45b3-9a85-20c952495156
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:39:20Z"
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.233228ms
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 7.315214ms
      message: 'load-balancer-api-internal: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 4.520815ms
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 11.015503ms
      message: 'load-balancer-api-internal: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 3.886779ms
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 7.327375ms
      message: 'load-balancer-api-internal: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 4.897157ms
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 8.46651ms
      message: 'load-balancer-api-internal: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 3.474691ms
      message: 'load-balancer-api-internal: tcp connection to a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 8.134179ms
      message: 'load-balancer-api-internal: resolved host name a9a49d119ce714db6ad595f2cf0b539f-3b74081fc6206e3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-network-check-target-ip-10-0-134-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "21409"
    uid: bf5d7a54-d880-4835-9353-fd0b0f655c93
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:40:20Z"
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.604331ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:20Z"
    - latency: 2.961278ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 2.598317ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 2.399626ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 2.222148ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 2.10714ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 2.505663ms
      message: 'network-check-target-ip-10-0-134-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-network-check-target-ip-10-0-142-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "21408"
    uid: c1f04530-6a16-4510-b101-911d03c484c9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:40:20Z"
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.164747ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:20Z"
    - latency: 859.286µs
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 888.956µs
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 878.742µs
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 1.581865ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 749.445µs
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 1.290962ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-network-check-target-ip-10-0-142-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "21410"
    uid: 710f21ca-56aa-44b7-86b6-2ed6631ac8bf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:40:20Z"
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.718401ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:20Z"
    - latency: 2.445357ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 3.41246ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 2.483728ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 2.590893ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 2.65467ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 2.508456ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-38-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-38.ec2.internal
      uid: 5bf67bd2-83d1-444e-ad44-c597e9140cbf
    resourceVersion: "20169"
    uid: 744aa5d0-546a-444b-9ff4-73f3380e42df
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2r9qh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:39:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 807.273µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 1.861971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:39:20Z"
    - latency: 821.728µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 1.878212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:38:20Z"
    - latency: 1.174034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 1.628399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:37:20Z"
    - latency: 937.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 2.137258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:36:20Z"
    - latency: 767.033µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:35:20Z"
    - latency: 1.6839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:35:20Z"
kind: List
metadata:
  resourceVersion: ""