apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14691"
    uid: 518fdaf1-37a9-4275-a34b-1ec7ded2ec53
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:43:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:43:07Z"
    - latency: 1.373511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 1.234448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 984.03µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 678.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 932.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 1.119211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:37:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14352"
    uid: e4e23745-1d25-45f3-88b6-72454f28481f
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:42:07Z"
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.933241ms
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 7.292526ms
      message: 'load-balancer-api-external: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 4.331625ms
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 6.456789ms
      message: 'load-balancer-api-external: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 5.561728ms
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 6.463476ms
      message: 'load-balancer-api-external: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 5.67993ms
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 10.202258ms
      message: 'load-balancer-api-external: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 5.862672ms
      message: 'load-balancer-api-external: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 6.586137ms
      message: 'load-balancer-api-external: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14351"
    uid: 924b5d42-5c8b-4579-8068-9d5852057ad6
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:42:07Z"
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.888967ms
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 7.214016ms
      message: 'load-balancer-api-internal: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 4.098498ms
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 6.455144ms
      message: 'load-balancer-api-internal: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 5.570908ms
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 6.416193ms
      message: 'load-balancer-api-internal: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 9.384814ms
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 10.153734ms
      message: 'load-balancer-api-internal: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 4.114324ms
      message: 'load-balancer-api-internal: tcp connection to aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 6.54824ms
      message: 'load-balancer-api-internal: resolved host name aa33ac37b298e476e9df53878a7cabb8-19a6353e675acab1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-134-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14688"
    uid: d5682fb5-9361-4d0b-805f-75aa0f038bd0
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:43:07Z"
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.608511ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:43:07Z"
    - latency: 1.020509ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 701.006µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 957.224µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 829.061µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 893.564µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 1.590086ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:37:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-139-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14689"
    uid: e7ccd246-f7ca-44ba-99f2-8e33726057f6
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:43:07Z"
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.79107ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:43:07Z"
    - latency: 2.193138ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 1.690584ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 1.797981ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 1.772529ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 1.751054ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 2.006385ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:37:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-143-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14690"
    uid: 95aa012d-fe12-41cd-9139-4796c00727cf
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:43:07Z"
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.281232ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:43:07Z"
    - latency: 3.405099ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 2.037406ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 2.503465ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 1.839796ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 2.269828ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 2.342448ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:37:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:36:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 26079c3c-7ae2-4402-85f6-b3e20540cdeb
    resourceVersion: "14350"
    uid: f51bbcb3-33b4-467b-894a-a573a94dec08
  spec:
    sourcePod: network-check-source-65bdbbff45-cxl4r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:42:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 2.641935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:42:07Z"
    - latency: 735.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 1.726696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:41:07Z"
    - latency: 907.921µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 1.748729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:40:07Z"
    - latency: 888.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 1.954027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:39:07Z"
    - latency: 897.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:38:07Z"
    - latency: 1.942893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:38:07Z"
kind: List
metadata:
  resourceVersion: ""