apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "24236"
    uid: fe8b2a2c-755a-4d33-b442-07ac996c2d07
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:45:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.14067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:45:41Z"
    - latency: 1.463661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:44:41Z"
    - latency: 982.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:43:41Z"
    - latency: 1.040128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:42:41Z"
    - latency: 1.017811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:41:41Z"
    - latency: 929.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:40:41Z"
    - latency: 968.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:39:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "28299"
    uid: 8a8594b7-ab82-4ace-af4b-fabd7a0c14b4
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:44:41Z"
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.657526ms
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 7.274463ms
      message: 'load-balancer-api-external: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 4.987817ms
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 6.99799ms
      message: 'load-balancer-api-external: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 4.238367ms
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 6.750327ms
      message: 'load-balancer-api-external: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 6.049954ms
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 7.368645ms
      message: 'load-balancer-api-external: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 6.454475ms
      message: 'load-balancer-api-external: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:46:41Z"
    - latency: 6.83761ms
      message: 'load-balancer-api-external: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "28300"
    uid: 87db3730-ca5f-4428-86a5-4984a681b86e
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:44:41Z"
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.555667ms
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 7.338576ms
      message: 'load-balancer-api-internal: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 4.978943ms
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 7.060991ms
      message: 'load-balancer-api-internal: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 4.76268ms
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 6.845898ms
      message: 'load-balancer-api-internal: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 13.474745ms
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 7.42353ms
      message: 'load-balancer-api-internal: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 12.532071ms
      message: 'load-balancer-api-internal: tcp connection to ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:46:41Z"
    - latency: 6.89198ms
      message: 'load-balancer-api-internal: resolved host name ae61f9ffe8aed42228e733a744e94be8-31b70a3a8a8c0fd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-network-check-target-ip-10-0-133-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "24234"
    uid: 6d981908-d402-4531-a1ac-b4852710b5c8
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:45:41Z"
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.366374ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:45:41Z"
    - latency: 2.538755ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:44:41Z"
    - latency: 2.590964ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:43:41Z"
    - latency: 2.286849ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:42:41Z"
    - latency: 5.885646ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:41:41Z"
    - latency: 2.339286ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:40:41Z"
    - latency: 2.674643ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:39:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-network-check-target-ip-10-0-135-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "24233"
    uid: 934827db-3f61-4a91-949f-b922489a6ae2
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:45:41Z"
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.723µs
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:45:41Z"
    - latency: 1.920225ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:44:41Z"
    - latency: 946.212µs
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:43:41Z"
    - latency: 1.32466ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:42:41Z"
    - latency: 953.242µs
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:41:41Z"
    - latency: 881.317µs
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:40:41Z"
    - latency: 1.621228ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:39:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-network-check-target-ip-10-0-141-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "24235"
    uid: cac08bc3-9987-4645-b5be-8830333c0cbe
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:45:41Z"
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.565064ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:45:41Z"
    - latency: 2.41246ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:44:41Z"
    - latency: 2.589076ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:43:41Z"
    - latency: 2.428412ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:42:41Z"
    - latency: 6.007463ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:41:41Z"
    - latency: 2.175961ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:40:41Z"
    - latency: 2.5651ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:39:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:38:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-164-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-164.ec2.internal
      uid: a45a4294-e502-41d2-aed6-a959b38e2fe5
    resourceVersion: "28298"
    uid: 563dd50e-905c-427a-b210-847b1c22f932
  spec:
    sourcePod: network-check-source-dbd9cf844-chsm8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:44:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 1.600138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:50:41Z"
    - latency: 1.100181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 1.760944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:49:41Z"
    - latency: 846.948µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 1.642262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:48:41Z"
    - latency: 990.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 1.882335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:47:41Z"
    - latency: 888.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:46:41Z"
    - latency: 1.79891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:46:41Z"
kind: List
metadata:
  resourceVersion: ""