apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "14153"
    uid: 971e5413-92f6-4091-943b-636c1da7e226
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:40:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.851µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:40:58Z"
    - latency: 1.010744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 869.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 877.505µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 931.593µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 945.811µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 4.624247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:34:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "13738"
    uid: 9bdae841-f2aa-4c57-aa32-a489de2cfa4d
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:39:58Z"
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.773385ms
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 7.903274ms
      message: 'load-balancer-api-external: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 4.09797ms
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 8.481851ms
      message: 'load-balancer-api-external: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 4.863204ms
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 7.596871ms
      message: 'load-balancer-api-external: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 4.824735ms
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 10.616095ms
      message: 'load-balancer-api-external: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 4.806425ms
      message: 'load-balancer-api-external: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 7.181244ms
      message: 'load-balancer-api-external: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:35:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "13740"
    uid: b2abcca6-1998-40b3-9534-14aca2662835
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:39:58Z"
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.121092ms
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 7.984233ms
      message: 'load-balancer-api-internal: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 4.097828ms
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 8.373675ms
      message: 'load-balancer-api-internal: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 4.945123ms
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 7.671622ms
      message: 'load-balancer-api-internal: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 4.862264ms
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 10.533149ms
      message: 'load-balancer-api-internal: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 4.863484ms
      message: 'load-balancer-api-internal: tcp connection to a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 7.067344ms
      message: 'load-balancer-api-internal: resolved host name a2518ddef223a4ada9f22aa2713a1eb5-7cbd19aba992afd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:35:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-129-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "14151"
    uid: e490125e-915a-4507-bbfd-783aebe685f2
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:40:58Z"
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251615ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:40:58Z"
    - latency: 2.190278ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 1.982546ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 2.251229ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 1.955821ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 1.894227ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 4.260734ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:34:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-136-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "14150"
    uid: 9c3d1a95-8642-45f6-87ec-bc66e8111fbd
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:40:58Z"
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.939µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:40:58Z"
    - latency: 891.574µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 1.219794ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 832.844µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 787.268µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 731.769µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 4.830844ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:34:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-140-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "14152"
    uid: edbeb229-2172-4862-a0a8-37e11604f7c3
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:40:58Z"
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303956ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:40:58Z"
    - latency: 2.167607ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 2.254503ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 2.099352ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 2.075538ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 2.097636ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 4.978ms
      message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:34:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T09:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 38b7d213-9dc5-459a-b293-16667fb8953e
    resourceVersion: "13737"
    uid: fe94722f-b6cc-4a56-8fb6-36f0890e2418
  spec:
    sourcePod: network-check-source-8894fc9bd-zvsn4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:39:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.826µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 1.891423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:39:58Z"
    - latency: 1.050039ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 1.786247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:38:58Z"
    - latency: 644.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 1.602947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:37:58Z"
    - latency: 862.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 1.616494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:36:58Z"
    - latency: 976.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:35:58Z"
    - latency: 1.642624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:35:58Z"
kind: List
metadata:
  resourceVersion: ""