apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "21745"
    uid: 974eb96e-4a3a-4d2a-a48e-8041f112cd04
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:19:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.334782ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:56Z"
    - latency: 1.453425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:56Z"
    - latency: 988.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:56Z"
    - latency: 1.121811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:16:56Z"
    - latency: 917.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:15:56Z"
    - latency: 1.08125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:56Z"
    - latency: 985.461µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "26679"
    uid: 0ed69824-2c5a-4d73-88cf-dc40817ac074
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:18:56Z"
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071599ms
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 8.209791ms
      message: 'load-balancer-api-external: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 5.430146ms
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 6.845274ms
      message: 'load-balancer-api-external: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 5.59047ms
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 7.205223ms
      message: 'load-balancer-api-external: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 4.053721ms
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 7.013594ms
      message: 'load-balancer-api-external: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 5.597167ms
      message: 'load-balancer-api-external: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:56Z"
    - latency: 8.145771ms
      message: 'load-balancer-api-external: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:20:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "26680"
    uid: b6f4fc6c-c8e7-4039-b55f-d8c6661f05c0
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:18:56Z"
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.040361ms
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 8.320511ms
      message: 'load-balancer-api-internal: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 5.008532ms
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 6.882691ms
      message: 'load-balancer-api-internal: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 5.594675ms
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 7.250989ms
      message: 'load-balancer-api-internal: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 4.172447ms
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 6.895955ms
      message: 'load-balancer-api-internal: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 5.651131ms
      message: 'load-balancer-api-internal: tcp connection to aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:56Z"
    - latency: 7.959027ms
      message: 'load-balancer-api-internal: resolved host name aaa6cff52afa240eb91a52cb1eef7cdc-f69bec8361fec6fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:20:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-network-check-target-ip-10-0-136-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "21743"
    uid: 1b3e2ada-0ce0-454d-9979-98f1ba3bf064
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:19:56Z"
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249903ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:56Z"
    - latency: 2.380834ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:56Z"
    - latency: 2.098183ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:56Z"
    - latency: 2.050966ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:16:56Z"
    - latency: 2.425008ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:15:56Z"
    - latency: 2.30985ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:56Z"
    - latency: 2.268026ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-network-check-target-ip-10-0-137-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "21744"
    uid: 55fc809a-23f0-4548-8ecb-7875c2e87ed7
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:19:56Z"
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.337275ms
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:56Z"
    - latency: 966.283µs
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:56Z"
    - latency: 1.066257ms
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:56Z"
    - latency: 891.088µs
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:16:56Z"
    - latency: 794.15µs
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:15:56Z"
    - latency: 891.37µs
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:56Z"
    - latency: 1.549723ms
      message: 'network-check-target-ip-10-0-137-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-network-check-target-ip-10-0-138-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "21741"
    uid: a1622ae7-45d0-4e5c-8400-dea59858c2a5
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:19:56Z"
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.673962ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:56Z"
    - latency: 1.919756ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:56Z"
    - latency: 1.840266ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:56Z"
    - latency: 1.900041ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:16:56Z"
    - latency: 1.719711ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:15:56Z"
    - latency: 1.673664ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:56Z"
    - latency: 1.949769ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-178.ec2.internal
      uid: d310240f-ddc2-4a0e-a1b1-00b72856402d
    resourceVersion: "26678"
    uid: 72c8840f-50d2-4b9b-9b45-3a4f3f6b40b5
  spec:
    sourcePod: network-check-source-989f8b8dc-q49qj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:18:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 926.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 2.559545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:56Z"
    - latency: 973.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 1.843382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:56Z"
    - latency: 960.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 2.084167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:22:56Z"
    - latency: 1.040217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 1.906315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:21:56Z"
    - latency: 1.436381ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:56Z"
    - latency: 2.181757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:20:56Z"
kind: List
metadata:
  resourceVersion: ""