apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "24817"
    uid: 409d97ee-fb81-4834-a59b-9180efe8dcab
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:01:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:01:20Z"
    - latency: 945.176µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 1.052481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 1.181899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 792.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 1.699466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 1.289367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "23568"
    uid: 18bb9460-fc64-45f9-be8b-f27a336561f9
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:00:20Z"
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.465579ms
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 9.138671ms
      message: 'load-balancer-api-external: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 4.51769ms
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 10.129382ms
      message: 'load-balancer-api-external: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 4.84014ms
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 9.6725ms
      message: 'load-balancer-api-external: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 4.568135ms
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 13.340323ms
      message: 'load-balancer-api-external: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 5.271046ms
      message: 'load-balancer-api-external: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 13.123898ms
      message: 'load-balancer-api-external: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:56:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "23567"
    uid: dc04629c-a094-46c8-af04-dbbb86a2adfd
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:00:20Z"
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.446311ms
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 9.074596ms
      message: 'load-balancer-api-internal: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 4.488411ms
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 10.163471ms
      message: 'load-balancer-api-internal: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 4.285098ms
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 9.602684ms
      message: 'load-balancer-api-internal: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 4.659549ms
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 13.260956ms
      message: 'load-balancer-api-internal: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 4.94421ms
      message: 'load-balancer-api-internal: tcp connection to a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 13.422099ms
      message: 'load-balancer-api-internal: resolved host name a5ed7a6a350994a56935b2ae52b28f7f-bc40f67fc815772f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:56:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-network-check-target-ip-10-0-135-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "24813"
    uid: 356575af-97c8-4698-835f-9131df6355f1
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:01:20Z"
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 715.326µs
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:01:20Z"
    - latency: 879.253µs
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 1.08756ms
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 1.674099ms
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 799.595µs
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 1.143847ms
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 1.616777ms
      message: 'network-check-target-ip-10-0-135-49: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-network-check-target-ip-10-0-137-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "24814"
    uid: d7260745-ca4c-4f82-bdce-7428da3e33c2
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:01:20Z"
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.704287ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:01:20Z"
    - latency: 1.901771ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 1.884867ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 1.880488ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 1.694333ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 2.053115ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 1.936958ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-network-check-target-ip-10-0-138-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "24815"
    uid: c9aff36f-380e-4b0f-bd2b-560c7cd45987
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:01:20Z"
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.23505ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:01:20Z"
    - latency: 2.104889ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 2.070578ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 2.370991ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 2.011151ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 2.268104ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 2.153955ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T17:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-49.ec2.internal
      uid: c0d6be4b-25c0-49ac-9dff-24e85cc864eb
    resourceVersion: "23566"
    uid: 5930b382-e9df-4f3c-9862-84b6e9b1bc36
  spec:
    sourcePod: network-check-source-8894fc9bd-92b5k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T18:00:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.168756ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 1.648161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T18:00:20Z"
    - latency: 1.089256ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 1.854066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:59:20Z"
    - latency: 942.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 2.114374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:58:20Z"
    - latency: 984.966µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 1.704555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:57:20Z"
    - latency: 1.007932ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T17:56:20Z"
    - latency: 4.75937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T17:56:20Z"
kind: List
metadata:
  resourceVersion: ""