apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "10651"
    uid: 0d54eb94-ed11-4219-8a04-911873f25bdc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "14142"
    uid: f255a6b0-4134-4281-9fa9-b439cdfca6e2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T10:52:00Z"
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.009113ms
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 8.501204ms
      message: 'load-balancer-api-external: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 2.928234ms
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 9.824373ms
      message: 'load-balancer-api-external: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 4.056698ms
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 8.460318ms
      message: 'load-balancer-api-external: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 3.502302ms
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 8.405522ms
      message: 'load-balancer-api-external: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 4.480505ms
      message: 'load-balancer-api-external: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:48:00Z"
    - latency: 10.774624ms
      message: 'load-balancer-api-external: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:48:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "14141"
    uid: dd39126f-e774-468c-8f9f-1e34d85ae29a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T10:52:00Z"
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.960331ms
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 8.561347ms
      message: 'load-balancer-api-internal: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 2.998877ms
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 9.8ms
      message: 'load-balancer-api-internal: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 4.031717ms
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 8.396207ms
      message: 'load-balancer-api-internal: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 3.527893ms
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 8.465665ms
      message: 'load-balancer-api-internal: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 4.496087ms
      message: 'load-balancer-api-internal: tcp connection to a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:48:00Z"
    - latency: 10.753268ms
      message: 'load-balancer-api-internal: resolved host name a220bc713d4ba40fe8f619918fa79c1b-6a7ba71a81ce9396.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:48:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-135-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "10647"
    uid: 3a97b16e-fcc2-4c51-b9a0-987141bb1494
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-139-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "10650"
    uid: ad1e78d8-b0b0-4bc6-89ac-c194ea75a96e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-140-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "10648"
    uid: 1c02ed8f-0fd2-4888-a3c0-15f2a37c103b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T10:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: cdc2deb2-2854-46c2-82fc-b5912b043a2c
    resourceVersion: "14140"
    uid: 8981cce5-f8c5-40a9-ba0b-fa98e661d785
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gqq7k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T10:52:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.334396ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 1.758089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:52:00Z"
    - latency: 821.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 2.016503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:51:00Z"
    - latency: 909.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 1.761671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:50:00Z"
    - latency: 1.065976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 1.762278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:49:00Z"
    - latency: 732.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T10:48:00Z"
    - latency: 1.408562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T10:48:00Z"
kind: List
metadata:
  resourceVersion: ""