apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "21905"
    uid: 05db3cfe-4f0e-424e-83ed-9e5b7035149b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:54:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:54:54Z"
    - latency: 854.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 929.055µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 866.11µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 1.092788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 874.371µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 1.31361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "20749"
    uid: cbc1cb22-878c-4efd-8b29-e18ee5a646c2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:53:54Z"
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.928229ms
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 6.569523ms
      message: 'load-balancer-api-external: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 6.441046ms
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 9.001262ms
      message: 'load-balancer-api-external: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 6.286122ms
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 8.25303ms
      message: 'load-balancer-api-external: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 7.61421ms
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 6.963572ms
      message: 'load-balancer-api-external: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 6.057278ms
      message: 'load-balancer-api-external: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 9.431289ms
      message: 'load-balancer-api-external: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "20750"
    uid: e43e75e9-7f28-450c-8d82-12ff9cfed220
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:53:54Z"
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.381472ms
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 6.529118ms
      message: 'load-balancer-api-internal: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 4.817548ms
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 9.050297ms
      message: 'load-balancer-api-internal: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 5.875433ms
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 8.275006ms
      message: 'load-balancer-api-internal: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 5.662263ms
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 7.035723ms
      message: 'load-balancer-api-internal: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 6.066706ms
      message: 'load-balancer-api-internal: tcp connection to ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 9.474234ms
      message: 'load-balancer-api-internal: resolved host name ab7594123bc7d434f8db43ba1939302d-823d6af884539575.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-129-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "21903"
    uid: 22b0a3c1-b238-4fb3-8845-73a2a3787a1b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:54:54Z"
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.596565ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:54:54Z"
    - latency: 1.933141ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 1.965587ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 1.956662ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 2.053085ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 1.970682ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 2.106459ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-129-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "21904"
    uid: f769ac63-39f8-445a-963d-9c0d32f908d4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:54:54Z"
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.116µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:54:54Z"
    - latency: 977.346µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 1.090878ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 1.153517ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 888.465µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 951.504µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 1.233012ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-130-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "21902"
    uid: 55af1a58-f59e-47d5-915f-e7c405bfe39c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:54:54Z"
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.920836ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:54:54Z"
    - latency: 2.303263ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 2.216579ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 2.157574ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 2.396033ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 2.134996ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 2.112977ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3c40ea18-1516-4049-93f5-95821488d57d
    resourceVersion: "20747"
    uid: 6560451b-8004-457f-b19f-52438ed00470
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tmlcb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:53:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 1.993209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:53:54Z"
    - latency: 900.482µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 1.974424ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:52:54Z"
    - latency: 826.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 1.820746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:51:54Z"
    - latency: 847.266µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 1.850267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:50:54Z"
    - latency: 909.554µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:49:54Z"
    - latency: 2.547851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:49:54Z"
kind: List
metadata:
  resourceVersion: ""