apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "9623"
    uid: 9b93074d-849b-4f5d-9630-4b48101580e9
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "18063"
    uid: 96184c59-977a-47b9-ab6e-83d615e5ee3f
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:24Z"
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.230791ms
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 18.377563ms
      message: 'load-balancer-api-external: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 52.428356ms
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 9.757673ms
      message: 'load-balancer-api-external: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 3.383711819s
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 8.238757ms
      message: 'load-balancer-api-external: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 53.977699ms
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 10.068541ms
      message: 'load-balancer-api-external: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 51.906813ms
      message: 'load-balancer-api-external: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:24Z"
    - latency: 10.043803ms
      message: 'load-balancer-api-external: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "18064"
    uid: ee23bd62-dd70-4eeb-a2f1-2340336818ee
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:24Z"
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.272057ms
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 15.446235ms
      message: 'load-balancer-api-internal: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 52.447455ms
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 6.789643ms
      message: 'load-balancer-api-internal: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 53.881563ms
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 5.194761ms
      message: 'load-balancer-api-internal: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 56.686774ms
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 7.338901ms
      message: 'load-balancer-api-internal: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 51.964094ms
      message: 'load-balancer-api-internal: tcp connection to af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:24Z"
    - latency: 7.404138ms
      message: 'load-balancer-api-internal: resolved host name af0c3e1109d574ab68fbc2bb82460a9c-8b4500ed082056de.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-128-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "9619"
    uid: 6f5b5c23-6376-4abc-bf9d-8975449b8094
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-129-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "9621"
    uid: 08b5fca8-d245-4c1d-a089-b00974d879cb
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-138-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "9622"
    uid: 3fbb5115-2282-40ae-b348-b20fe6108880
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:37:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-1.compute.internal
      uid: 85e3530d-22c3-4912-93a7-bb3c5deb036b
    resourceVersion: "18062"
    uid: 314296e7-a4e1-4191-b42c-26913e71df71
  spec:
    sourcePod: network-check-source-6f78d59f99-pgc5d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:43:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 3.884719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:24Z"
    - latency: 1.381369ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 1.739402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:24Z"
    - latency: 741.283µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 2.417499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:24Z"
    - latency: 1.144136ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 1.629614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:40:24Z"
    - latency: 1.045999ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:39:24Z"
    - latency: 1.915087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:39:24Z"
kind: List
metadata:
  resourceVersion: ""