apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14510"
    uid: 328e8360-65bd-474a-b4a4-4e00e40dd693
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:10:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:10:12Z"
    - latency: 1.515461ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 1.348047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 930.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 1.061091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 954.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 1.249526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:04:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14200"
    uid: 1a5faa05-386d-4824-90ce-32cb1ef0da13
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:09:12Z"
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.29254ms
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 7.219376ms
      message: 'load-balancer-api-external: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 3.742265ms
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 9.405239ms
      message: 'load-balancer-api-external: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 4.388438ms
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 7.314606ms
      message: 'load-balancer-api-external: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 4.944416ms
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 7.429292ms
      message: 'load-balancer-api-external: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 5.334578ms
      message: 'load-balancer-api-external: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 9.893322ms
      message: 'load-balancer-api-external: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14201"
    uid: 4d705966-694b-4a47-aaa3-9481f70353b6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:09:12Z"
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.438486ms
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 7.121033ms
      message: 'load-balancer-api-internal: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 5.14301ms
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 9.325968ms
      message: 'load-balancer-api-internal: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 4.340402ms
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 7.223915ms
      message: 'load-balancer-api-internal: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 5.119429ms
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 7.529276ms
      message: 'load-balancer-api-internal: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 5.249693ms
      message: 'load-balancer-api-internal: tcp connection to a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 9.96319ms
      message: 'load-balancer-api-internal: resolved host name a22dc865dee5e433294bcd69b4ac8238-cbd8b58353c20745.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-network-check-target-ip-10-0-133-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14511"
    uid: b227fae7-7478-44a3-91f9-51642bfee4ba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:10:12Z"
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.035825ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:10:12Z"
    - latency: 2.242892ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 2.088769ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 1.998815ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 1.933088ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 2.154176ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 2.65608ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:04:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-network-check-target-ip-10-0-136-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14508"
    uid: 18d4fcc0-12a9-427e-962d-298dbf25f655
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:10:12Z"
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.155µs
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:10:12Z"
    - latency: 1.460719ms
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 1.483005ms
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 1.29271ms
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 1.495645ms
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 940.333µs
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 1.875854ms
      message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:04:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-network-check-target-ip-10-0-141-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14509"
    uid: 8de5d8f7-2088-4dd6-9346-8148c734463f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:10:12Z"
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.844376ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:10:12Z"
    - latency: 1.715405ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 1.596503ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 1.352011ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 1.771216ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 1.251434ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 1.871615ms
      message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:04:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:03:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-214-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-214.ec2.internal
      uid: f82ecc7e-014b-490b-9c01-971bc1131a1c
    resourceVersion: "14199"
    uid: 95b6a357-2051-46df-9ad6-41496268d52c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h9f8m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:09:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 1.989109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:09:12Z"
    - latency: 804.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 2.111235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:08:12Z"
    - latency: 743.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 2.263177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:07:12Z"
    - latency: 690.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 1.810886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:06:12Z"
    - latency: 808.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:05:12Z"
    - latency: 2.264697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:05:12Z"
kind: List
metadata:
  resourceVersion: ""