apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "9138"
    uid: 472cd4d7-3ff0-4ab2-a3e0-975ac69c1e89
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "10496"
    uid: e1c497df-5e2e-42e4-bdc6-67caa3fb55ea
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:30Z"
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.2044ms
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 6.582978ms
      message: 'load-balancer-api-external: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 3.338094967s
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 7.108177ms
      message: 'load-balancer-api-external: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 5.709618ms
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 6.151591ms
      message: 'load-balancer-api-external: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 5.044902ms
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 6.997826ms
      message: 'load-balancer-api-external: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 6.435738ms
      message: 'load-balancer-api-external: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:30Z"
    - latency: 7.977886ms
      message: 'load-balancer-api-external: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "10495"
    uid: b6137083-82c6-468b-a272-7c445ec8bddf
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:30Z"
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.215802ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 6.681693ms
      message: 'load-balancer-api-internal: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 19.786146ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 7.048575ms
      message: 'load-balancer-api-internal: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 5.70344ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 6.218927ms
      message: 'load-balancer-api-internal: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 5.58521ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 6.893872ms
      message: 'load-balancer-api-internal: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 6.923434ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:30Z"
    - latency: 8.033263ms
      message: 'load-balancer-api-internal: resolved host name ab0ff8b41a0cf4427b72bec3df8f0f7b-eb182fb212bdec7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-network-check-target-ip-10-0-128-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "9136"
    uid: a6d0c045-41ee-4e97-9652-261d74038093
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-network-check-target-ip-10-0-130-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "9137"
    uid: def0c7e6-42b6-431e-8a12-f86781a782e6
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-network-check-target-ip-10-0-140-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "9135"
    uid: bd482918-fb0a-43e1-9fc7-8c61ceac02b0
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-66.us-east-2.compute.internal
      uid: e7846268-6104-47f5-a309-85e70203c4c7
    resourceVersion: "10494"
    uid: 3599a8e6-df9b-4dc9-a58c-9249c2b2342e
  spec:
    sourcePod: network-check-source-6f78d59f99-26zn5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 1.839333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:35:30Z"
    - latency: 1.207665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 1.92049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:34:30Z"
    - latency: 830.152µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 1.818966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:30Z"
    - latency: 1.004114ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 1.676036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:30Z"
    - latency: 1.0216ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:30Z"
    - latency: 3.096548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:30Z"
kind: List
metadata:
  resourceVersion: ""