apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "15050"
    uid: a2562dda-bd17-45a5-bdb1-6922e4fe485e
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:43:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:43:53Z"
    - latency: 883.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 1.152297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 1.038997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 971.792µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 929.294µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 1.031121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "14543"
    uid: 0e5ad1bc-365e-4dfb-beea-d2539fe1e2f1
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:42:53Z"
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.465121ms
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 9.748234ms
      message: 'load-balancer-api-external: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 6.079569ms
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 14.019773ms
      message: 'load-balancer-api-external: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 4.727396ms
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 8.309145ms
      message: 'load-balancer-api-external: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 9.572966ms
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 11.554548ms
      message: 'load-balancer-api-external: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 4.66403ms
      message: 'load-balancer-api-external: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 10.299752ms
      message: 'load-balancer-api-external: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "14542"
    uid: 79b3d34e-565c-4a57-a4e3-cadc117b0a7a
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:42:53Z"
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.494735ms
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 9.731497ms
      message: 'load-balancer-api-internal: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 4.141776ms
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 14.118758ms
      message: 'load-balancer-api-internal: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 4.781796ms
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 8.285542ms
      message: 'load-balancer-api-internal: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 5.007236ms
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 11.522912ms
      message: 'load-balancer-api-internal: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 4.625127ms
      message: 'load-balancer-api-internal: tcp connection to ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 10.329483ms
      message: 'load-balancer-api-internal: resolved host name ae5b8de2f4f984fbc8ee3645b61d5945-e310b168313ffb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-network-check-target-ip-10-0-133-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "15049"
    uid: b5962b7a-810e-4a5d-a29d-d78704dcaa67
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:43:53Z"
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.624986ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:43:53Z"
    - latency: 2.0517ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 2.153171ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 2.158688ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 2.364655ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 2.285235ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 2.402985ms
      message: 'network-check-target-ip-10-0-133-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-network-check-target-ip-10-0-139-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "15048"
    uid: b3632cb4-2b26-494a-bf51-fbb1fa4e77b9
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:43:53Z"
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.225304ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:43:53Z"
    - latency: 2.073955ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 2.318183ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 2.13512ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 2.379515ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 2.22714ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 2.134909ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-network-check-target-ip-10-0-143-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "15047"
    uid: 51780de9-0723-411e-ac0e-9ed7993b2cca
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:43:53Z"
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.267717ms
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:43:53Z"
    - latency: 740.183µs
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 1.286629ms
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 824.232µs
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 766.581µs
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 866.12µs
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 1.685988ms
      message: 'network-check-target-ip-10-0-143-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:36:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-180-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-180.ec2.internal
      uid: 7ac008f1-83cb-4f73-a3df-3d6a48d3b26c
    resourceVersion: "14541"
    uid: b3c76efb-6b94-42f4-8805-d0809ebfb2ce
  spec:
    sourcePod: network-check-source-6f8b768455-7vmjw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:42:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 1.643155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:42:53Z"
    - latency: 895.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 1.451451ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:41:53Z"
    - latency: 919.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 1.89094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:53Z"
    - latency: 1.1234ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 1.853416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:53Z"
    - latency: 935.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:53Z"
    - latency: 1.502894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:53Z"
kind: List
metadata:
  resourceVersion: ""