apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "13002"
    uid: 4079bb60-cd94-4ab2-9a32-f4f93412d0e9
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:37:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.542µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:37:45Z"
    - latency: 1.26194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:36:45Z"
    - latency: 1.369338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:35:45Z"
    - latency: 987.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:34:45Z"
    - latency: 1.063745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:33:45Z"
    - latency: 873.567µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:32:45Z"
    - latency: 887.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:31:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "15055"
    uid: d21ba318-c551-49e4-b97e-1d38daaa3aba
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:36:45Z"
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.555943ms
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 8.843831ms
      message: 'load-balancer-api-external: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 55.530323ms
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 7.018448ms
      message: 'load-balancer-api-external: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 55.234229ms
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 7.856676ms
      message: 'load-balancer-api-external: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 54.750481ms
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 7.414072ms
      message: 'load-balancer-api-external: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 55.364032ms
      message: 'load-balancer-api-external: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:38:45Z"
    - latency: 7.648498ms
      message: 'load-balancer-api-external: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:38:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "15054"
    uid: 0c8620bc-d5f8-4a18-9d9e-0086513f3e44
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:36:45Z"
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.541735ms
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 8.95144ms
      message: 'load-balancer-api-internal: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 55.475065ms
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 7.133811ms
      message: 'load-balancer-api-internal: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 54.973378ms
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 7.908377ms
      message: 'load-balancer-api-internal: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 54.824355ms
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 7.335552ms
      message: 'load-balancer-api-internal: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 55.376671ms
      message: 'load-balancer-api-internal: tcp connection to aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:38:45Z"
    - latency: 7.605748ms
      message: 'load-balancer-api-internal: resolved host name aba120f1cba2042cbad52a420222b164-0610ce61f886076c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:38:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-130-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "12995"
    uid: a68cb4f9-0214-49e1-9ff7-fd90e67ae2ea
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:37:45Z"
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.778µs
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:37:45Z"
    - latency: 831.899µs
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:36:45Z"
    - latency: 1.293043ms
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:35:45Z"
    - latency: 937.513µs
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:34:45Z"
    - latency: 1.813014ms
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:33:45Z"
    - latency: 879.173µs
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:32:45Z"
    - latency: 1.200781ms
      message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:31:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-133-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "12997"
    uid: 3cc3ec85-e947-45f8-a54d-d433c7d8123b
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:37:45Z"
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.966269ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:37:45Z"
    - latency: 2.255191ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:36:45Z"
    - latency: 1.873451ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:35:45Z"
    - latency: 2.290914ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:34:45Z"
    - latency: 2.522782ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:33:45Z"
    - latency: 2.136746ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:32:45Z"
    - latency: 2.245448ms
      message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:31:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-135-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "12996"
    uid: c5d19e40-0220-4b0f-855c-4885d1cab0db
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:37:45Z"
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.149541ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:37:45Z"
    - latency: 2.029999ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:36:45Z"
    - latency: 2.22192ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:35:45Z"
    - latency: 2.064306ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:34:45Z"
    - latency: 2.944162ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:33:45Z"
    - latency: 2.248648ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:32:45Z"
    - latency: 2.15416ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:31:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-12T18:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-210.us-west-1.compute.internal
      uid: 4338303b-cf77-41dd-9803-0d725b4d302d
    resourceVersion: "15053"
    uid: d20f7005-cc69-4a65-8782-cdf36ced25ba
  spec:
    sourcePod: network-check-source-7c57c6dd5d-sgwrn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-12T18:36:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 1.646471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:42:45Z"
    - latency: 825.04µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 1.586096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:41:45Z"
    - latency: 822.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 1.865832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:40:45Z"
    - latency: 1.06308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 1.668518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:39:45Z"
    - latency: 1.077377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-12T18:38:45Z"
    - latency: 1.681749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-12T18:38:45Z"
kind: List
metadata:
  resourceVersion: ""