apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14806"
    uid: 248647ed-dbf0-44e0-88e5-c2008adbbb93
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:46:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.78037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:00Z"
    - latency: 811.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 1.191007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 1.19502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 997.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 1.159093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 757.557µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14283"
    uid: 2f95b89f-9ab0-433e-bcb9-12fc532d6837
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:45:00Z"
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.241125ms
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 10.728167ms
      message: 'load-balancer-api-external: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 5.659593ms
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 8.634254ms
      message: 'load-balancer-api-external: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 6.161689ms
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 8.350723ms
      message: 'load-balancer-api-external: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 5.83904ms
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 8.670034ms
      message: 'load-balancer-api-external: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 5.039239ms
      message: 'load-balancer-api-external: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 8.529346ms
      message: 'load-balancer-api-external: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14282"
    uid: ed28a3e3-1aab-46b8-b4e1-20325f7872b3
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:45:00Z"
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.242865ms
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 10.782447ms
      message: 'load-balancer-api-internal: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 5.648081ms
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 8.52451ms
      message: 'load-balancer-api-internal: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 5.308244ms
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 8.476139ms
      message: 'load-balancer-api-internal: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 4.368709ms
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 8.597048ms
      message: 'load-balancer-api-internal: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 5.058863ms
      message: 'load-balancer-api-internal: tcp connection to a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 8.558836ms
      message: 'load-balancer-api-internal: resolved host name a69d7ad6bb3bf430f90a893058ab4526-4fb273f74bff8518.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-137-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14804"
    uid: 809486eb-3ae4-47f3-a2f5-e7c18bd5290b
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:46:00Z"
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.069µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:00Z"
    - latency: 1.091593ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 927.649µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 1.567248ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 964.086µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 1.584344ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 1.164615ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-140-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14805"
    uid: f3bdbd2a-28a6-4846-aaae-ad346e3dd81f
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:46:00Z"
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.102547ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:00Z"
    - latency: 1.739528ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 1.865537ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 1.781881ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 1.982367ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 1.953081ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 2.132434ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-140-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14803"
    uid: 7f22e2f2-ccdc-4f3f-98b8-78c968838a8c
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:46:00Z"
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.895033ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:00Z"
    - latency: 2.152557ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 1.92645ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 2.029375ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 1.858859ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 2.182967ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 2.17827ms
      message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:38:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: b76e659c-3ce0-4a56-8003-2db9d000067a
    resourceVersion: "14281"
    uid: 28c1574e-948a-49ea-8ab8-be26e5bb3d6c
  spec:
    sourcePod: network-check-source-7d88cb55d8-5q95l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:45:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 1.533251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:00Z"
    - latency: 839.907µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 1.844962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:00Z"
    - latency: 935.67µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 1.997527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:00Z"
    - latency: 875.568µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 1.971962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:00Z"
    - latency: 910.863µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:00Z"
    - latency: 2.311577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:00Z"
kind: List
metadata:
  resourceVersion: ""