apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14797"
    uid: 842b35ab-460b-4f07-8ad0-5476ac355c40
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:57:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:57:43Z"
    - latency: 1.327548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 934.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 911.05µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 1.009465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 1.583841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 1.853491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14302"
    uid: 4f2d7ad9-a2d2-4c3f-961e-c0f4c8c23548
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:56:43Z"
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.029671ms
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 13.717338ms
      message: 'load-balancer-api-external: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 10.324234ms
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 8.305936ms
      message: 'load-balancer-api-external: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 4.84447ms
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 8.687572ms
      message: 'load-balancer-api-external: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 6.269016ms
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 10.033253ms
      message: 'load-balancer-api-external: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 5.392492ms
      message: 'load-balancer-api-external: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 8.222144ms
      message: 'load-balancer-api-external: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14303"
    uid: d9091601-02b2-4f93-a9f7-a69c7ff8dc0e
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:56:43Z"
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.245258ms
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 13.824329ms
      message: 'load-balancer-api-internal: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 5.002388ms
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 8.237756ms
      message: 'load-balancer-api-internal: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 4.878634ms
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 8.626406ms
      message: 'load-balancer-api-internal: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 6.305025ms
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 10.175047ms
      message: 'load-balancer-api-internal: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 4.259188ms
      message: 'load-balancer-api-internal: tcp connection to a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 8.138889ms
      message: 'load-balancer-api-internal: resolved host name a02877256ad974683887497562516ac3-162e0da28b6bfa91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-128-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14794"
    uid: 9af76c5a-3b9a-40dd-8c00-f2114af6ecc6
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:57:43Z"
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330575ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:57:43Z"
    - latency: 2.0701ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 1.997515ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 2.153629ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 2.136285ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 1.836162ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 2.384065ms
      message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-136-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14796"
    uid: 5a012880-b6e4-4ec3-b9c3-53a69f28aad5
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:57:43Z"
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.478762ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:57:43Z"
    - latency: 2.403289ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 2.296475ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 2.186331ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 2.603731ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 1.755958ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 2.492451ms
      message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-143-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14795"
    uid: b2614338-0813-4250-a0f3-f2b6cd7007cb
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:57:43Z"
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.12281ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:57:43Z"
    - latency: 1.461219ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 982.621µs
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 1.516207ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 1.851682ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 880.11µs
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 1.484574ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:50:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-10-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-10.ec2.internal
      uid: 89c2c08e-1c6f-4a57-8990-12f2f8250347
    resourceVersion: "14301"
    uid: 58b9aa7f-a8a6-4c32-aacf-130812e107ca
  spec:
    sourcePod: network-check-source-7d88cb55d8-fdzbr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:56:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.671µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 2.276108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:56:43Z"
    - latency: 1.002104ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 2.091586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:55:43Z"
    - latency: 978.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 2.01915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:54:43Z"
    - latency: 1.156247ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 2.319406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:53:43Z"
    - latency: 745.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:43Z"
    - latency: 1.933604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:52:43Z"
kind: List
metadata:
  resourceVersion: ""