apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15575"
    uid: 752320c2-6450-478d-ac62-a04c4d26a297
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:02:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.311456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:17Z"
    - latency: 907.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 1.250644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 1.167048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 1.110958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 1.112654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 919.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15103"
    uid: fbcadb50-607b-46f0-b6f3-ac8d26aeb830
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:01:17Z"
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.29053ms
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 9.225743ms
      message: 'load-balancer-api-external: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 5.193657ms
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 9.1654ms
      message: 'load-balancer-api-external: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 5.937869ms
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 7.505886ms
      message: 'load-balancer-api-external: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 6.139094ms
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 8.828104ms
      message: 'load-balancer-api-external: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 3.928512ms
      message: 'load-balancer-api-external: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 8.028155ms
      message: 'load-balancer-api-external: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:57:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15102"
    uid: 51614258-79ae-45ac-a97f-86bd5203ed40
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:01:17Z"
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.285025ms
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 9.292137ms
      message: 'load-balancer-api-internal: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 5.203982ms
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 9.099779ms
      message: 'load-balancer-api-internal: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 5.98233ms
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 8.061373ms
      message: 'load-balancer-api-internal: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 6.140471ms
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 8.814416ms
      message: 'load-balancer-api-internal: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 3.945593ms
      message: 'load-balancer-api-internal: tcp connection to a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 8.181272ms
      message: 'load-balancer-api-internal: resolved host name a64987f1786ff4685bbfc4d721622094-54708ad257d5ecaa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:57:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-131-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15572"
    uid: f3a894b7-da0a-4ee3-8b02-94c09157967f
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:02:17Z"
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.237128ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:17Z"
    - latency: 1.84937ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 2.249975ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 2.181692ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 1.899667ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 2.263012ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 2.252417ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-136-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15574"
    uid: 8e0019a5-3ac1-4bbc-93dc-5f91f415c32e
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:02:17Z"
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.167027ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:17Z"
    - latency: 1.95841ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 2.157325ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 2.487136ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 2.162449ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 2.077575ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 2.266172ms
      message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-141-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15573"
    uid: 7ce6f87e-550e-4452-9c83-7d2c1ca9bb2f
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:02:17Z"
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.251459ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:17Z"
    - latency: 940.656µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 994.884µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 1.037703ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 1.006083ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 1.070388ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 1.221768ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:55:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 92fb4f84-556c-4dfd-bbf4-9b07f7f7f7ac
    resourceVersion: "15101"
    uid: 24307768-8bee-40ce-b026-dcca07b5f913
  spec:
    sourcePod: network-check-source-7d88cb55d8-pk2x7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:01:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.962µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 1.814381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:01:17Z"
    - latency: 941.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 2.211534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:00:17Z"
    - latency: 900.215µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 1.837351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:59:17Z"
    - latency: 1.014147ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 1.829324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:58:17Z"
    - latency: 1.11895ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:57:17Z"
    - latency: 1.623584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:57:17Z"
kind: List
metadata:
  resourceVersion: ""