apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15607"
    uid: e8bd14db-76e9-47f7-89c2-feb617213df1
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:10:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:10:20Z"
    - latency: 986.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 926.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 1.495652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 1.051978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 1.467568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 2.331224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15187"
    uid: f27d4364-8345-4852-b651-fcfac338d4f8
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:09:20Z"
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.192793ms
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 8.893679ms
      message: 'load-balancer-api-external: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 5.134463ms
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 8.600843ms
      message: 'load-balancer-api-external: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 4.810787ms
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 9.125995ms
      message: 'load-balancer-api-external: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 5.198041ms
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 8.301978ms
      message: 'load-balancer-api-external: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 4.167984ms
      message: 'load-balancer-api-external: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 8.005102ms
      message: 'load-balancer-api-external: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15186"
    uid: 18a80913-4e7d-4a7b-9b27-4f757a4060bc
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:09:20Z"
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.137378ms
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 9.015662ms
      message: 'load-balancer-api-internal: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 5.099085ms
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 8.731073ms
      message: 'load-balancer-api-internal: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 4.859561ms
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 9.231943ms
      message: 'load-balancer-api-internal: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 5.174843ms
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 8.383423ms
      message: 'load-balancer-api-internal: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 4.287036ms
      message: 'load-balancer-api-internal: tcp connection to ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 8.051794ms
      message: 'load-balancer-api-internal: resolved host name ac63d00db7c484c978ca625163afebbb-ca23c3c8365d2c1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-129-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15606"
    uid: 9e36befd-d2e3-4546-9fc5-5bdc946ccd19
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:10:20Z"
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.276963ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:10:20Z"
    - latency: 1.934557ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 1.776833ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 1.780238ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 1.883065ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 1.7936ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 2.237164ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-141-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15605"
    uid: be8e0649-7394-43c1-9605-66044c9d24c7
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:10:20Z"
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.587268ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:10:20Z"
    - latency: 1.785419ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 1.943491ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 2.524157ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 2.144318ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 2.162098ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 3.012777ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-142-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15604"
    uid: ce8c89fa-7170-481a-86b4-8ed06e64de80
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:10:20Z"
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097312ms
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:10:20Z"
    - latency: 836.511µs
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 1.11763ms
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 781.493µs
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 1.008033ms
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 1.000296ms
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 1.265352ms
      message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:03:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-45.ec2.internal
      uid: 0a35d7e6-a3aa-4b89-b5a2-0fd1ca6c3e55
    resourceVersion: "15184"
    uid: ab7815d5-726e-4645-b118-d37579b9777c
  spec:
    sourcePod: network-check-source-dbd9cf844-mwbx5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:09:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.672µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 2.298164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:09:20Z"
    - latency: 870.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 1.749401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:08:20Z"
    - latency: 930.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 1.702609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:07:20Z"
    - latency: 855.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 1.861277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:20Z"
    - latency: 884.96µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:20Z"
    - latency: 1.978334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:20Z"
kind: List
metadata:
  resourceVersion: ""