apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "10892"
    uid: 90107742-a6fb-4d5c-a83c-540e7a286bd5
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "14423"
    uid: 116dd7bc-223e-4e4e-9bdf-04593b16f8b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:46:27Z"
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.806641ms
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 9.248993ms
      message: 'load-balancer-api-external: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 5.564515ms
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 12.548487ms
      message: 'load-balancer-api-external: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 4.930157ms
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 9.380847ms
      message: 'load-balancer-api-external: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 5.145939ms
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 9.919697ms
      message: 'load-balancer-api-external: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 4.739062ms
      message: 'load-balancer-api-external: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:42:27Z"
    - latency: 9.689004ms
      message: 'load-balancer-api-external: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "14422"
    uid: 70d65e0d-8a06-4e06-b4af-83df6cfb0505
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:46:27Z"
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.259985ms
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 9.167576ms
      message: 'load-balancer-api-internal: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 5.585061ms
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 12.57385ms
      message: 'load-balancer-api-internal: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 5.423847ms
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 9.403143ms
      message: 'load-balancer-api-internal: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 4.628717ms
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 9.834232ms
      message: 'load-balancer-api-internal: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 4.854578ms
      message: 'load-balancer-api-internal: tcp connection to ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:42:27Z"
    - latency: 9.67262ms
      message: 'load-balancer-api-internal: resolved host name ae799c85035b940038cd3fc5575a2520-5f6ea00cebe62a2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-134-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "10890"
    uid: a480f0eb-f5a1-4fb0-aabe-5848e1d01e5b
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: 10.135.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-136-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "10887"
    uid: 027f6250-0b0a-4eaa-ba8d-6cd45093cdb2
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-142-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "10889"
    uid: 02830db2-d56c-42cb-a7a3-55ae9afe205e
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 31bf4c5c-17bd-475b-a576-402eb388a51a
    resourceVersion: "14421"
    uid: 48bf8743-3c9a-4a21-a5be-fb076d2c19e1
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qwg4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:46:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.105988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 1.918455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:46:27Z"
    - latency: 1.027145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 2.173875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:45:27Z"
    - latency: 830.796µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 2.165348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:44:27Z"
    - latency: 947.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 1.655777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:43:27Z"
    - latency: 1.132144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:42:27Z"
    - latency: 1.618486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:42:27Z"
kind: List
metadata:
  resourceVersion: ""