apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "21784"
    uid: 4dd094f4-d4f4-4c20-a132-0a6f611a0e1e
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.311737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:08Z"
    - latency: 1.310125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:08Z"
    - latency: 1.216148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:08Z"
    - latency: 940.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:08Z"
    - latency: 1.082308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:08Z"
    - latency: 1.271626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:08Z"
    - latency: 1.133232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:30:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "26321"
    uid: a21410cc-c3cf-4cf3-9340-6d4e5184789a
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:35:08Z"
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.872694ms
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 7.308658ms
      message: 'load-balancer-api-external: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 6.208247ms
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 8.884305ms
      message: 'load-balancer-api-external: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 4.71891ms
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 8.953559ms
      message: 'load-balancer-api-external: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 5.321143ms
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 8.051575ms
      message: 'load-balancer-api-external: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 4.570535ms
      message: 'load-balancer-api-external: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:08Z"
    - latency: 7.292695ms
      message: 'load-balancer-api-external: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:37:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "26322"
    uid: 660e2432-b372-4635-ad5f-29dde15f60e8
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:35:08Z"
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.834149ms
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 7.351437ms
      message: 'load-balancer-api-internal: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 5.395594ms
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 8.924063ms
      message: 'load-balancer-api-internal: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 4.696435ms
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 9.010027ms
      message: 'load-balancer-api-internal: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 3.675657ms
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 8.13583ms
      message: 'load-balancer-api-internal: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 4.599602ms
      message: 'load-balancer-api-internal: tcp connection to a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:08Z"
    - latency: 7.342922ms
      message: 'load-balancer-api-internal: resolved host name a9a85a129eddf4be987ad1c790521a81-eadbaa668c59ead0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:37:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-134-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "21782"
    uid: 10bbde6c-3d4a-46d2-b8f0-2edb4a57b8b3
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:08Z"
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.383467ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:08Z"
    - latency: 2.443987ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:08Z"
    - latency: 2.336764ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:08Z"
    - latency: 2.529335ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:08Z"
    - latency: 2.5523ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:08Z"
    - latency: 2.626792ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:08Z"
    - latency: 2.485493ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:30:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-135-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "21781"
    uid: 8442efdf-b4ec-4303-a2af-2d4019a69ff0
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:08Z"
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.362198ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:08Z"
    - latency: 2.28086ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:08Z"
    - latency: 2.0076ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:08Z"
    - latency: 2.093566ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:08Z"
    - latency: 2.464637ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:08Z"
    - latency: 2.274513ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:08Z"
    - latency: 2.222404ms
      message: 'network-check-target-ip-10-0-135-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:30:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-138-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "21780"
    uid: 8ac57cc8-9a58-45c1-a189-93c5a904995f
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:08Z"
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.913µs
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:08Z"
    - latency: 1.516752ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:08Z"
    - latency: 888.027µs
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:08Z"
    - latency: 895.812µs
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:08Z"
    - latency: 1.460535ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:08Z"
    - latency: 819.269µs
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:08Z"
    - latency: 1.13675ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:30:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:29:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-41.ec2.internal
      uid: 5cbd6634-0c35-4ce0-a892-0aee4149e9f9
    resourceVersion: "26320"
    uid: 7649b67b-9846-40cc-bef4-79d1df689848
  spec:
    sourcePod: network-check-source-56499946bc-x8l44
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:35:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 1.86434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:41:08Z"
    - latency: 875.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 1.700399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:40:08Z"
    - latency: 1.018547ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 1.679383ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:39:08Z"
    - latency: 813.921µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 1.988042ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:38:08Z"
    - latency: 897.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:08Z"
    - latency: 1.882932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:37:08Z"
kind: List
metadata:
  resourceVersion: ""