apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12287"
    uid: 1f436797-d145-4d58-aadc-5cfad41451bf
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:10:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.108µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:55Z"
    - latency: 1.416965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 1.481047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 1.068998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 1.161364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 1.545982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 1.422946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12003"
    uid: 284a9660-285e-45a2-90df-112cd5d397ed
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:55Z"
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.589192ms
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 7.949332ms
      message: 'load-balancer-api-external: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 54.043178ms
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 8.457651ms
      message: 'load-balancer-api-external: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 53.574077ms
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 7.559625ms
      message: 'load-balancer-api-external: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 53.492781ms
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 8.278383ms
      message: 'load-balancer-api-external: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 54.272202ms
      message: 'load-balancer-api-external: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 7.28538ms
      message: 'load-balancer-api-external: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12002"
    uid: 5714e402-cce7-49fc-ac1d-e48273c5180f
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:55Z"
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.86985ms
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 7.987773ms
      message: 'load-balancer-api-internal: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 53.379885ms
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 8.434141ms
      message: 'load-balancer-api-internal: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 53.384769ms
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 7.648342ms
      message: 'load-balancer-api-internal: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 53.475537ms
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 8.364734ms
      message: 'load-balancer-api-internal: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 54.635217ms
      message: 'load-balancer-api-internal: tcp connection to a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 7.868691ms
      message: 'load-balancer-api-internal: resolved host name a335051bfa5d644229f7333f1adf0bf7-866b660e603ffe48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-network-check-target-ip-10-0-130-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12284"
    uid: 9e97afc7-02aa-4c8b-803d-e18bfc2da605
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:10:55Z"
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996844ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:55Z"
    - latency: 2.009681ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 1.923886ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 1.871277ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 1.926929ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 2.111973ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 1.988232ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-network-check-target-ip-10-0-131-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12285"
    uid: 3d07d0a7-4ef2-4be2-bad9-6b380b83a604
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:10:55Z"
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.31967ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:55Z"
    - latency: 2.155158ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 2.040847ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 2.134288ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 2.122894ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 2.237379ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 2.33507ms
      message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-network-check-target-ip-10-0-137-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12283"
    uid: 7c99a68d-25b9-4eb6-9558-04af587117a5
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:10:55Z"
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.388567ms
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:55Z"
    - latency: 892.527µs
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 858.202µs
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 920.934µs
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 927.008µs
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 716.285µs
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 2.047463ms
      message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-71-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-71.us-west-1.compute.internal
      uid: 081cfae3-9c0e-4511-b48b-a32326b3187e
    resourceVersion: "12001"
    uid: 72652b17-aa05-470c-aaca-927b239366b7
  spec:
    sourcePod: network-check-source-6f78d59f99-8cj9n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 787.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 2.140155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:55Z"
    - latency: 983.897µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 1.701356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:55Z"
    - latency: 1.203427ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 1.870906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:55Z"
    - latency: 779.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 1.868108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:55Z"
    - latency: 910.195µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:55Z"
    - latency: 2.063429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:55Z"
kind: List
metadata:
  resourceVersion: ""