apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "10998"
    uid: 74f22943-36ff-4cb8-ba8d-dcb0ce6f0d4c
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "14794"
    uid: 250b48ed-d6e0-45ca-beb1-961b4110f025
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:55:33Z"
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.044248ms
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 9.827679ms
      message: 'load-balancer-api-external: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 4.830768ms
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 9.597225ms
      message: 'load-balancer-api-external: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 6.43956ms
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 12.704168ms
      message: 'load-balancer-api-external: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 6.33928ms
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 8.104344ms
      message: 'load-balancer-api-external: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 5.003401ms
      message: 'load-balancer-api-external: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:51:33Z"
    - latency: 8.086281ms
      message: 'load-balancer-api-external: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:51:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "14795"
    uid: 06a0cc60-9b84-41ac-aab4-2068b66d5605
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:55:33Z"
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.655647ms
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 9.933212ms
      message: 'load-balancer-api-internal: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 5.464149ms
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 9.531242ms
      message: 'load-balancer-api-internal: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 6.428387ms
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 12.882172ms
      message: 'load-balancer-api-internal: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 6.358536ms
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 8.30483ms
      message: 'load-balancer-api-internal: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 4.977033ms
      message: 'load-balancer-api-internal: tcp connection to a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:51:33Z"
    - latency: 8.183369ms
      message: 'load-balancer-api-internal: resolved host name a6e0978ed93a64b48a098b19bd11a00b-c8e5f266a50443d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:51:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-128-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "11003"
    uid: c85e144b-4e6d-4ec9-a633-c7d98994b4a0
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-133-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "11004"
    uid: e3860b8e-a474-4169-bc81-5e460788d9b7
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-133-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "11005"
    uid: 76a17635-3370-4c20-bfc8-f6ca69072228
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 30707df0-624b-4f60-84ce-56475600f728
    resourceVersion: "14793"
    uid: 3204f2ad-2add-424d-9f2d-0888c7661cdf
  spec:
    sourcePod: network-check-source-7d88cb55d8-fgnhm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:55:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 1.801824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:55:33Z"
    - latency: 866.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 1.693151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:54:33Z"
    - latency: 851.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 1.68251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:53:33Z"
    - latency: 1.083762ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 1.871578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:52:33Z"
    - latency: 1.117602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:51:33Z"
    - latency: 1.866907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:51:33Z"
kind: List
metadata:
  resourceVersion: ""