apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "11159"
    uid: e8bb2a61-d398-4c67-8972-53350794d42e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "15031"
    uid: 2fe10c8e-452c-48d0-be5f-ea844c283f7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:10:44Z"
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.044767ms
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 8.675019ms
      message: 'load-balancer-api-external: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 5.827545ms
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 9.007737ms
      message: 'load-balancer-api-external: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 6.273696ms
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 8.300929ms
      message: 'load-balancer-api-external: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 5.005879ms
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 8.193747ms
      message: 'load-balancer-api-external: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 4.79546ms
      message: 'load-balancer-api-external: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:06:44Z"
    - latency: 11.882131ms
      message: 'load-balancer-api-external: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:06:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "15030"
    uid: 35f8f663-db7f-4fa4-81b2-70b4a0864141
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:10:44Z"
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.016379ms
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 8.925707ms
      message: 'load-balancer-api-internal: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 5.78159ms
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 9.337455ms
      message: 'load-balancer-api-internal: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 6.236949ms
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 8.401447ms
      message: 'load-balancer-api-internal: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 4.907712ms
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 8.246765ms
      message: 'load-balancer-api-internal: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 4.782069ms
      message: 'load-balancer-api-internal: tcp connection to afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:06:44Z"
    - latency: 11.963308ms
      message: 'load-balancer-api-internal: resolved host name afc05275df3774eb1bc76a3439c24ea7-8864504901a474f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:06:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-network-check-target-ip-10-0-134-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "11155"
    uid: ccd726b7-4259-44af-b380-7497a7231804
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-network-check-target-ip-10-0-135-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "11157"
    uid: e54eeac8-fdf8-4b07-944b-ab72184b1217
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-network-check-target-ip-10-0-136-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "11156"
    uid: 49535747-03dd-42bc-adba-df08fa0d20d2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:04:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-50-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-50.ec2.internal
      uid: f910c568-3d43-4a23-83a3-c9df2ad11ce1
    resourceVersion: "15029"
    uid: e58099e3-4af5-474c-ad47-2e4264591c26
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdlbf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:10:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.719µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 2.26508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:10:44Z"
    - latency: 891.215µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 2.269121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:09:44Z"
    - latency: 890.62µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 1.642196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:08:44Z"
    - latency: 1.039095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 1.801775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:07:44Z"
    - latency: 1.150731ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:06:44Z"
    - latency: 1.607871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:06:44Z"
kind: List
metadata:
  resourceVersion: ""