apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "23201"
    uid: 56619e90-9d7b-424d-ae17-fa18549c7620
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:07:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.240517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:57Z"
    - latency: 991.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 1.163963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 1.323025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 865.146µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 1.316563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 844.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "22178"
    uid: 89ffc5a8-5638-4b64-8471-965c3707a001
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:06:57Z"
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.228455ms
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 8.671882ms
      message: 'load-balancer-api-external: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 4.804034ms
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 8.414022ms
      message: 'load-balancer-api-external: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 5.342892ms
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 9.714ms
      message: 'load-balancer-api-external: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 4.71123ms
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 8.494254ms
      message: 'load-balancer-api-external: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 6.097745ms
      message: 'load-balancer-api-external: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 13.367692ms
      message: 'load-balancer-api-external: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "22177"
    uid: 866b9aae-e097-425d-adcf-5fc211a06c50
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:06:57Z"
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.258957ms
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 8.653618ms
      message: 'load-balancer-api-internal: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 4.817044ms
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 8.33153ms
      message: 'load-balancer-api-internal: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 5.354667ms
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 9.641169ms
      message: 'load-balancer-api-internal: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 3.923033ms
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 8.45552ms
      message: 'load-balancer-api-internal: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 4.070179ms
      message: 'load-balancer-api-internal: tcp connection to acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 13.313786ms
      message: 'load-balancer-api-internal: resolved host name acaa16a491341493ba9caa42e225bcd9-90c52a182870e9d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-129-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "23198"
    uid: 8173c356-d625-427b-880d-fde827924523
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:07:57Z"
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.686µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:57Z"
    - latency: 988.737µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 1.009027ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 1.058549ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 1.028849ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 964.651µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 1.359503ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-140-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "23199"
    uid: d5771657-611f-4b7d-94b3-e3b2187f5b2b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:07:57Z"
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.828319ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:57Z"
    - latency: 1.939432ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 1.985241ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 2.55999ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 2.65162ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 2.783146ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 2.216145ms
      message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-141-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "23200"
    uid: efdf1bc2-241c-4141-9ef1-7eab3ab38f03
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:07:57Z"
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.386259ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:57Z"
    - latency: 2.421345ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 2.468762ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 2.95155ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 2.60667ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 2.50383ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 2.338739ms
      message: 'network-check-target-ip-10-0-141-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: e3c07446-2050-4660-ab8d-087ba84546ce
    resourceVersion: "22175"
    uid: bd41a075-2c8f-421b-ba44-f8b003864962
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nxcbz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:06:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.109µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 1.832373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:06:57Z"
    - latency: 825.198µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 1.684616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:05:57Z"
    - latency: 1.018244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 2.933814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:04:57Z"
    - latency: 830.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 1.868865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:03:57Z"
    - latency: 1.042308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:02:57Z"
    - latency: 1.793568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:02:57Z"
kind: List
metadata:
  resourceVersion: ""