apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "23620"
    uid: 072ac760-9deb-40ab-bce0-569e8b3de5b3
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:51:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:51:18Z"
    - latency: 1.085084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:50:18Z"
    - latency: 939.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:49:18Z"
    - latency: 964.359µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:48:18Z"
    - latency: 1.073127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:47:18Z"
    - latency: 1.089669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:46:18Z"
    - latency: 952.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "28309"
    uid: d054577f-7383-4128-a0fe-7e392aad0e88
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:50:18Z"
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.298793ms
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 8.068817ms
      message: 'load-balancer-api-external: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 4.276589ms
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 11.049639ms
      message: 'load-balancer-api-external: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 4.224685ms
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 5.887069ms
      message: 'load-balancer-api-external: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 4.360407ms
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 8.650026ms
      message: 'load-balancer-api-external: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 6.560965ms
      message: 'load-balancer-api-external: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:52:18Z"
    - latency: 11.244743ms
      message: 'load-balancer-api-external: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:52:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "28310"
    uid: 0e21413f-7a86-454e-a0e3-ae3dcfe110aa
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:50:18Z"
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.263211ms
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 8.108258ms
      message: 'load-balancer-api-internal: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 4.308111ms
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 10.995492ms
      message: 'load-balancer-api-internal: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 4.209014ms
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 5.793403ms
      message: 'load-balancer-api-internal: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 4.385445ms
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 8.545145ms
      message: 'load-balancer-api-internal: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 6.553958ms
      message: 'load-balancer-api-internal: tcp connection to a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:52:18Z"
    - latency: 11.282497ms
      message: 'load-balancer-api-internal: resolved host name a2867679863cc49908156db57059eb72-88890bf770399de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:52:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-134-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "23619"
    uid: 38568f5e-13fd-43b7-8f8d-0160747270af
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:51:18Z"
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329448ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:51:18Z"
    - latency: 2.322751ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:50:18Z"
    - latency: 2.390526ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:49:18Z"
    - latency: 2.419176ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:48:18Z"
    - latency: 2.484913ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:47:18Z"
    - latency: 2.800474ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:46:18Z"
    - latency: 2.527401ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-136-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "23617"
    uid: 26b834ee-0d2b-4195-bad3-5e6dd59a6dc0
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:51:18Z"
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.987µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:51:18Z"
    - latency: 952.696µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:50:18Z"
    - latency: 875.323µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:49:18Z"
    - latency: 914.573µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:48:18Z"
    - latency: 840.264µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:47:18Z"
    - latency: 886.907µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:46:18Z"
    - latency: 1.198366ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-138-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "23618"
    uid: 4b5c7c36-3ee7-48fe-b41a-3ca2a5bc44e3
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:51:18Z"
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.217566ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:51:18Z"
    - latency: 2.17254ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:50:18Z"
    - latency: 2.408359ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:49:18Z"
    - latency: 2.151828ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:48:18Z"
    - latency: 2.125344ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:47:18Z"
    - latency: 2.598599ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:46:18Z"
    - latency: 2.435705ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T16:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 25812faa-2383-4a45-9795-4a6ef992860b
    resourceVersion: "28308"
    uid: 473d6061-fa2e-40d7-99ff-295506089d70
  spec:
    sourcePod: network-check-source-56499946bc-dp9nw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:50:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 698.124µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 1.562338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:56:18Z"
    - latency: 1.00062ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 1.788165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:55:18Z"
    - latency: 924.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 1.713948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:54:18Z"
    - latency: 1.104544ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 2.039911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:53:18Z"
    - latency: 735.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:52:18Z"
    - latency: 1.7605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:52:18Z"
kind: List
metadata:
  resourceVersion: ""