apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "10887"
    uid: 470e8061-7803-4e50-950e-e8cf52e7a571
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "14581"
    uid: f6accd4b-6720-4530-bf4b-9528e5db56a9
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:28:53Z"
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.073012ms
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 8.271135ms
      message: 'load-balancer-api-external: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 4.536869ms
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 7.823661ms
      message: 'load-balancer-api-external: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 4.888519ms
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 7.013262ms
      message: 'load-balancer-api-external: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 5.759388ms
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 8.117134ms
      message: 'load-balancer-api-external: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 5.349756ms
      message: 'load-balancer-api-external: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:24:53Z"
    - latency: 12.509346ms
      message: 'load-balancer-api-external: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:24:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "14582"
    uid: c52c9289-d787-46b2-b898-f8a5fdfefa19
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:28:53Z"
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.119214ms
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 8.209173ms
      message: 'load-balancer-api-internal: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 3.660485ms
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 7.906005ms
      message: 'load-balancer-api-internal: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 4.509441ms
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 7.041798ms
      message: 'load-balancer-api-internal: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 7.589564ms
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 8.187649ms
      message: 'load-balancer-api-internal: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 5.105202ms
      message: 'load-balancer-api-internal: tcp connection to ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:24:53Z"
    - latency: 12.539551ms
      message: 'load-balancer-api-internal: resolved host name ab218e34681704c2abe3f4f42c623641-93c682a077a2bf55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:24:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-128-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "10893"
    uid: 52c2bd14-c211-4a37-afbb-ba12205de103
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-132-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "10892"
    uid: fa0bc57c-ec9d-4d56-9f4f-05aab794d286
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-136-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "10894"
    uid: 5a66285f-6f2a-4a49-a4a0-b4c9db6905ae
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-150-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-150.ec2.internal
      uid: 55725861-c7af-4558-9f94-c50c8eee0fa5
    resourceVersion: "14580"
    uid: cf98c42c-ef9b-4cc2-98dd-ade4cd5f595f
  spec:
    sourcePod: network-check-source-65bdbbff45-xwqwb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:28:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.547µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 1.722091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:28:53Z"
    - latency: 1.16902ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 1.908744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:27:53Z"
    - latency: 1.135918ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 1.729208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:26:53Z"
    - latency: 1.032452ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 1.787075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:25:53Z"
    - latency: 1.023553ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:24:53Z"
    - latency: 5.440034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:24:53Z"
kind: List
metadata:
  resourceVersion: ""