apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "23394"
    uid: 2bb0f924-0eb8-40e1-8f32-cf7aa4702ed5
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:35:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:35:24Z"
    - latency: 1.619024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:34:24Z"
    - latency: 1.710546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:33:24Z"
    - latency: 1.02951ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:32:24Z"
    - latency: 844.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:24Z"
    - latency: 1.359018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:24Z"
    - latency: 1.555701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "27503"
    uid: 05fec742-8253-4601-a238-796fe582a116
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:34:24Z"
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071072ms
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 14.257649ms
      message: 'load-balancer-api-external: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 5.017611ms
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 12.904389ms
      message: 'load-balancer-api-external: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 2.976799ms
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 9.499367ms
      message: 'load-balancer-api-external: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 5.780851ms
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 8.184231ms
      message: 'load-balancer-api-external: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 5.568994ms
      message: 'load-balancer-api-external: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:36:24Z"
    - latency: 9.977373ms
      message: 'load-balancer-api-external: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:36:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "27502"
    uid: f5806315-4721-4b6c-a72d-d5a116829d2e
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:34:24Z"
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.270709ms
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 14.350581ms
      message: 'load-balancer-api-internal: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 5.031297ms
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 12.862841ms
      message: 'load-balancer-api-internal: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 3.965607ms
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 9.461241ms
      message: 'load-balancer-api-internal: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 5.789719ms
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 8.107153ms
      message: 'load-balancer-api-internal: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 5.55594ms
      message: 'load-balancer-api-internal: tcp connection to acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:36:24Z"
    - latency: 9.998209ms
      message: 'load-balancer-api-internal: resolved host name acf6672bd50b4403897d1518dcff72ac-c6054b9cc0055df4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:36:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-network-check-target-ip-10-0-135-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "23391"
    uid: a3362f8e-426c-42e6-b26f-8ef817a3c466
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:35:24Z"
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.583µs
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:35:24Z"
    - latency: 916.912µs
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:34:24Z"
    - latency: 1.259376ms
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:33:24Z"
    - latency: 1.189752ms
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:32:24Z"
    - latency: 918.731µs
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:24Z"
    - latency: 934.016µs
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:24Z"
    - latency: 1.35417ms
      message: 'network-check-target-ip-10-0-135-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-network-check-target-ip-10-0-141-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "23393"
    uid: 33d65972-2591-4940-b3da-ba95806074c8
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:35:24Z"
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.517095ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:35:24Z"
    - latency: 2.044049ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:34:24Z"
    - latency: 2.077968ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:33:24Z"
    - latency: 2.162109ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:32:24Z"
    - latency: 2.058101ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:24Z"
    - latency: 2.147585ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:24Z"
    - latency: 2.356694ms
      message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-network-check-target-ip-10-0-142-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "23392"
    uid: 69a15fbd-e4d9-4ddf-8773-1e75476dbef6
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:35:24Z"
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.295658ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:35:24Z"
    - latency: 2.166481ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:34:24Z"
    - latency: 2.301479ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:33:24Z"
    - latency: 2.135967ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:32:24Z"
    - latency: 2.155932ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:24Z"
    - latency: 2.345449ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:24Z"
    - latency: 2.870136ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T20:28:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-189.ec2.internal
      uid: a5bcd2a3-20dd-4117-91ca-a9e22e567ea9
    resourceVersion: "27501"
    uid: 51b980d7-9c5e-4225-b431-eb09c45d3eed
  spec:
    sourcePod: network-check-source-869dcfcdcd-47dpz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T20:34:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 1.718583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:40:24Z"
    - latency: 858.517µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 1.865275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:39:24Z"
    - latency: 764.311µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 1.947245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:38:24Z"
    - latency: 1.001632ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 1.707779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:37:24Z"
    - latency: 867.971µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:36:24Z"
    - latency: 1.981985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:36:24Z"
kind: List
metadata:
  resourceVersion: ""