apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "22263"
    uid: b6ae2afc-62aa-4eb2-b225-fb5f075f3769
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:07:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.354109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:07:01Z"
    - latency: 942.168µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 1.247882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 1.092274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 1.570577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 1.065245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 1.146267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "21163"
    uid: 3544c719-ea9a-4cc0-95c1-5cd9f2327c28
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:01Z"
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.375558ms
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 8.118587ms
      message: 'load-balancer-api-external: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 3.937767ms
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 8.522ms
      message: 'load-balancer-api-external: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 3.723014ms
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 9.185882ms
      message: 'load-balancer-api-external: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 6.203139ms
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 8.998828ms
      message: 'load-balancer-api-external: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 3.677148ms
      message: 'load-balancer-api-external: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 8.334687ms
      message: 'load-balancer-api-external: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "21162"
    uid: b1496a2e-b32d-4ce1-9a47-9a65c3f292c1
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:01Z"
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.172271ms
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 8.180927ms
      message: 'load-balancer-api-internal: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 4.303956ms
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 8.457543ms
      message: 'load-balancer-api-internal: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 4.511745ms
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 9.11609ms
      message: 'load-balancer-api-internal: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 6.166668ms
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 8.9705ms
      message: 'load-balancer-api-internal: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 3.666968ms
      message: 'load-balancer-api-internal: tcp connection to aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 8.252279ms
      message: 'load-balancer-api-internal: resolved host name aeacd80afb7634b46914d3c5ed956e50-01cfc9f30038d466.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-133-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "22262"
    uid: 60304bcb-050f-446d-bb3f-5bdb8ea8d54a
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:07:01Z"
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996461ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:07:01Z"
    - latency: 1.707514ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 1.743448ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 1.90332ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 1.966202ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 1.750613ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 1.985521ms
      message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-136-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "22260"
    uid: b738d889-1341-4218-9a42-85fa28cd9302
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:07:01Z"
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.820649ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:07:01Z"
    - latency: 898.309µs
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 1.138858ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 1.277754ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 1.009182ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 1.389568ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 1.251998ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-network-check-target-ip-10-0-143-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "22261"
    uid: e1d44848-bbb7-4445-914f-a0c575a4dcb8
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:07:01Z"
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.282141ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:07:01Z"
    - latency: 2.168401ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 2.31227ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 2.34274ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 2.295001ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 2.120603ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 2.35812ms
      message: 'network-check-target-ip-10-0-143-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:00:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-8.ec2.internal
      uid: 8b65f049-51e8-438f-9330-a287f5bed927
    resourceVersion: "21161"
    uid: 857fdf2d-22b8-4903-9f74-9551b69d4cf0
  spec:
    sourcePod: network-check-source-989f8b8dc-4zfzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.138µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 1.97403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:06:01Z"
    - latency: 846.022µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 1.960071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:01Z"
    - latency: 832.524µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 1.670095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:01Z"
    - latency: 806.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 2.27712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:01Z"
    - latency: 890.283µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:01Z"
    - latency: 1.987146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:01Z"
kind: List
metadata:
  resourceVersion: ""