apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "24292"
    uid: 62360ed2-9f66-4916-b956-162a11b49b7c
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:28:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 768.013µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:28:36Z"
    - latency: 980.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:27:36Z"
    - latency: 975.08µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:26:36Z"
    - latency: 924.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:25:36Z"
    - latency: 1.126443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:24:36Z"
    - latency: 1.314513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:23:36Z"
    - latency: 1.083973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:22:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "28291"
    uid: e1c65ba3-0e10-461b-9da2-09c7392f3c09
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:27:36Z"
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.491546ms
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 9.332106ms
      message: 'load-balancer-api-external: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 4.048698ms
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 11.841331ms
      message: 'load-balancer-api-external: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 4.641321ms
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 10.506066ms
      message: 'load-balancer-api-external: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 4.431526ms
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 10.050406ms
      message: 'load-balancer-api-external: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 4.226564ms
      message: 'load-balancer-api-external: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:29:36Z"
    - latency: 10.605902ms
      message: 'load-balancer-api-external: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "28292"
    uid: e1d9ad54-b7ba-4f38-8f70-2af0c84b87ae
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:27:36Z"
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.498944ms
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 9.434643ms
      message: 'load-balancer-api-internal: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 4.107985ms
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 11.974672ms
      message: 'load-balancer-api-internal: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 4.650605ms
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 10.63565ms
      message: 'load-balancer-api-internal: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 4.438495ms
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 10.004676ms
      message: 'load-balancer-api-internal: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 5.226451ms
      message: 'load-balancer-api-internal: tcp connection to a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:29:36Z"
    - latency: 10.703311ms
      message: 'load-balancer-api-internal: resolved host name a8a44d191e092447bafcc94aa02e9d02-e49db7e690b579ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-129-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "24289"
    uid: 410353ea-a376-49c6-9e8d-7b9b2b9178a1
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:28:36Z"
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.748262ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:28:36Z"
    - latency: 1.623613ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:27:36Z"
    - latency: 1.770291ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:26:36Z"
    - latency: 1.92121ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:25:36Z"
    - latency: 1.852758ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:24:36Z"
    - latency: 1.695822ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:23:36Z"
    - latency: 2.039611ms
      message: 'network-check-target-ip-10-0-129-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:22:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-136-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "24288"
    uid: a59cf572-b1ab-4f6d-9141-dd0ef238e246
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:28:36Z"
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.574µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:28:36Z"
    - latency: 887.873µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:27:36Z"
    - latency: 1.693443ms
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:26:36Z"
    - latency: 1.285558ms
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:25:36Z"
    - latency: 816.05µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:24:36Z"
    - latency: 681.343µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:23:36Z"
    - latency: 1.045643ms
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:22:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-141-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "24290"
    uid: a24a87a5-ec4c-4c43-9975-6a29c080db3d
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:28:36Z"
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.19512ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:28:36Z"
    - latency: 1.734467ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:27:36Z"
    - latency: 2.334707ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:26:36Z"
    - latency: 2.096637ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:25:36Z"
    - latency: 2.250365ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:24:36Z"
    - latency: 2.16082ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:23:36Z"
    - latency: 2.941137ms
      message: 'network-check-target-ip-10-0-141-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:22:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T09:21:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 2543255a-ae24-45a4-806c-bacb00bd6d3a
    resourceVersion: "28290"
    uid: 5f481813-b938-40ef-87fb-3e77b88b77f7
  spec:
    sourcePod: network-check-source-6947749cfc-jqxp5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T09:27:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 1.686216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:33:36Z"
    - latency: 1.015366ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 1.733875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:32:36Z"
    - latency: 1.127935ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 1.945392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:31:36Z"
    - latency: 887.767µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 1.80197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:30:36Z"
    - latency: 1.100191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T09:29:36Z"
    - latency: 2.120215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T09:29:36Z"
kind: List
metadata:
  resourceVersion: ""