apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "22197"
    uid: b6b5705d-64d7-4984-8e9e-3a3574938b1d
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:52:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.832069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:52:33Z"
    - latency: 946.952µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 676.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 980.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 863.819µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 1.221895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 977.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "21089"
    uid: c9c80eeb-75a7-4586-a67c-bf10858ad41c
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:51:33Z"
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.143033ms
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 10.520718ms
      message: 'load-balancer-api-external: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 5.32917ms
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 7.993071ms
      message: 'load-balancer-api-external: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 5.633762ms
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 8.309862ms
      message: 'load-balancer-api-external: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 4.545798ms
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 7.398398ms
      message: 'load-balancer-api-external: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 4.129923ms
      message: 'load-balancer-api-external: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 7.956823ms
      message: 'load-balancer-api-external: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:47:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "21090"
    uid: cab72bca-c2dd-4fc3-bf39-b2ee8c2ed117
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:51:33Z"
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.646367ms
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 10.595735ms
      message: 'load-balancer-api-internal: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 5.274318ms
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 8.085052ms
      message: 'load-balancer-api-internal: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 3.598455ms
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 8.266103ms
      message: 'load-balancer-api-internal: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 3.883339ms
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 7.482301ms
      message: 'load-balancer-api-internal: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 4.416766ms
      message: 'load-balancer-api-internal: tcp connection to a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 8.069576ms
      message: 'load-balancer-api-internal: resolved host name a3819224514a74eef83d107c3cc66e2d-55d8287ab616aab0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:47:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-131-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "22194"
    uid: 34fd1952-421f-43d5-bf53-77cd569625c9
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:52:33Z"
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.765725ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:52:33Z"
    - latency: 2.21899ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 2.053903ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 2.024974ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 2.003637ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 2.061214ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 2.28889ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-141-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "22195"
    uid: 99089903-0609-4b29-bdf6-173c884e4fe6
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:52:33Z"
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.788049ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:52:33Z"
    - latency: 2.053976ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 1.647755ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 1.614674ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 1.636724ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 1.878815ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 1.79035ms
      message: 'network-check-target-ip-10-0-141-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-143-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "22196"
    uid: 61b9bfff-a769-4885-8332-e03baa0de8b5
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:52:33Z"
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.781789ms
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:52:33Z"
    - latency: 1.461689ms
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 738.464µs
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 1.202121ms
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 829.582µs
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 1.281608ms
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 1.134543ms
      message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-242-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-242.ec2.internal
      uid: cd8fe37a-9702-429a-93cb-3e29fd900349
    resourceVersion: "21088"
    uid: 89cadac2-7705-406f-96cb-982712103f4d
  spec:
    sourcePod: network-check-source-56499946bc-mtggq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:51:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 2.773488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:51:33Z"
    - latency: 683.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 1.602963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:50:33Z"
    - latency: 914.528µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 1.953616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:49:33Z"
    - latency: 994.851µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 1.830023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:48:33Z"
    - latency: 848.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:47:33Z"
    - latency: 1.514352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:47:33Z"
kind: List
metadata:
  resourceVersion: ""