apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "19128"
    uid: 746844ce-38f1-49c7-b781-89d5757e142f
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:39:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.244724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:39:18Z"
    - latency: 1.430735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 1.530745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 1.408864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 1.265921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 927.576µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 1.169405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "18497"
    uid: bac095aa-8881-4689-bc3b-3e432fb3c0c1
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.792514ms
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 7.714167ms
      message: 'load-balancer-api-external: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 56.45464ms
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 13.462042ms
      message: 'load-balancer-api-external: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 50.7182ms
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 8.247717ms
      message: 'load-balancer-api-external: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 51.193663ms
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 9.812379ms
      message: 'load-balancer-api-external: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 52.304171ms
      message: 'load-balancer-api-external: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 8.708792ms
      message: 'load-balancer-api-external: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:34:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "18498"
    uid: 59d7de31-7ee5-4b93-ade4-7241ac2531ec
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 58.838045ms
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 7.770026ms
      message: 'load-balancer-api-internal: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 52.247548ms
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 13.526863ms
      message: 'load-balancer-api-internal: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 50.708585ms
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 8.284413ms
      message: 'load-balancer-api-internal: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 53.362222ms
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 9.91368ms
      message: 'load-balancer-api-internal: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 51.542313ms
      message: 'load-balancer-api-internal: tcp connection to a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 8.752674ms
      message: 'load-balancer-api-internal: resolved host name a9753cfd54fbc4413af5ddaaf6ce77e7-46c63ce3a09e5500.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:34:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-131-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "19125"
    uid: ce7224e5-c5ce-4b58-995c-390228b034a9
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:39:18Z"
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.12µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:39:18Z"
    - latency: 905.23µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 8.165041ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 973.466µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 1.476381ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 844.29µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 1.549127ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-132-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "19126"
    uid: 550fe751-dc92-4f3f-bc3e-2a351f0c0327
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:39:18Z"
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.137396ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:39:18Z"
    - latency: 2.339734ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 7.875097ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 2.475122ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 2.37264ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 1.954896ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 2.622317ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-135-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "19127"
    uid: 53d7e815-82f4-4e00-8c8b-4ce67815df80
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:39:18Z"
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.280158ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:39:18Z"
    - latency: 2.522536ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 2.508379ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 2.482438ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 2.418992ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 2.378668ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 2.177216ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:32:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.us-west-2.compute.internal
      uid: 772a55bf-5305-4f7a-ad88-361598548877
    resourceVersion: "18494"
    uid: 333351e4-77ab-45fa-8716-8e51b9ff9961
  spec:
    sourcePod: network-check-source-6f78d59f99-jjdnx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 2.051455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:38:18Z"
    - latency: 1.034719ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 2.139632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:37:18Z"
    - latency: 1.662019ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 1.773375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:36:18Z"
    - latency: 819.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 2.214542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:35:18Z"
    - latency: 862.317µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:34:18Z"
    - latency: 1.770782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:34:18Z"
kind: List
metadata:
  resourceVersion: ""