apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "12886"
    uid: c9d41b0b-aa1c-4f04-8cfb-d63d5a5642a3
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 1.500852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.240753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 1.250478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 1.250429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 1.115963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
    - latency: 1.343026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "11280"
    uid: 589d51d5-78bb-417f-b0f0-728dcbf3b285
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:01Z"
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.308323ms
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 6.455465ms
      message: 'load-balancer-api-external: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 53.295826ms
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 7.006895ms
      message: 'load-balancer-api-external: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 52.134882ms
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 6.455273ms
      message: 'load-balancer-api-external: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 53.394127ms
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 7.100226ms
      message: 'load-balancer-api-external: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 55.778388ms
      message: 'load-balancer-api-external: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
    - latency: 6.229175ms
      message: 'load-balancer-api-external: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "11279"
    uid: 590051f1-c1c2-42d7-a7ba-ada1d40dbf0b
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:01Z"
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.314639ms
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 6.633553ms
      message: 'load-balancer-api-internal: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 53.251106ms
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 7.078007ms
      message: 'load-balancer-api-internal: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 53.181979ms
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 6.421666ms
      message: 'load-balancer-api-internal: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 53.39088ms
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 7.135307ms
      message: 'load-balancer-api-internal: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 55.249763ms
      message: 'load-balancer-api-internal: tcp connection to a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
    - latency: 6.243302ms
      message: 'load-balancer-api-internal: resolved host name a9dffb5858787452c8e0af2fe0486c32-aec373f6a2f23785.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-network-check-target-ip-10-0-132-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "12885"
    uid: 936b127e-cfd3-4f3a-9569-e22a0020c926
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:01Z"
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.387642ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 1.208464ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.342348ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 1.109972ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 1.432251ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 1.075311ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
    - latency: 1.346324ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-network-check-target-ip-10-0-132-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "13017"
    uid: 8cb96f5e-0ea2-4b53-8e2e-c2ff382a3270
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:09Z"
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.631µs
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:09Z"
    - latency: 2.15109ms
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:09Z"
    - latency: 2.19786ms
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:09Z"
    - latency: 976.275µs
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:09Z"
    - latency: 2.412424ms
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:09Z"
    - latency: 2.192522ms
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:09Z"
    - latency: 2.602921ms
      message: 'network-check-target-ip-10-0-132-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-network-check-target-ip-10-0-137-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "12961"
    uid: ad4faa4d-9644-4f68-97bf-2e1e069402ba
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:06Z"
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.933423ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:06Z"
    - latency: 1.787142ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:06Z"
    - latency: 854.287µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:06Z"
    - latency: 1.907505ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:06Z"
    - latency: 806.613µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:06Z"
    - latency: 1.885798ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:06Z"
    - latency: 783.896µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:09:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-171.us-west-1.compute.internal
      uid: e00be89f-38ef-412e-8972-1674d96bbeb5
    resourceVersion: "11274"
    uid: d8c2123f-6cf8-48fe-9e33-e31eabc740b0
  spec:
    sourcePod: network-check-source-6f78d59f99-n9p5b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:15:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.976461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 2.057766ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 1.783898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 2.116083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 1.887147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 2.299562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 2.023491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 1.000235ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
    - latency: 1.886169ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:01Z"
kind: List
metadata:
  resourceVersion: ""