apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "22891"
    uid: e5cded32-6d70-4949-a61a-6d3192744485
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:59:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.125117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:59:13Z"
    - latency: 1.328999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 1.012435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 933.509µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 960.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 1.757792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 924.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "21600"
    uid: 81e063fa-053d-42bc-82ec-4b7c6065bf5f
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:58:13Z"
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.114956ms
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 8.229313ms
      message: 'load-balancer-api-external: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 3.576593ms
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 6.745035ms
      message: 'load-balancer-api-external: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 3.60048ms
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 10.545237ms
      message: 'load-balancer-api-external: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 4.668477ms
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 9.411214ms
      message: 'load-balancer-api-external: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 5.371366ms
      message: 'load-balancer-api-external: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 6.344751ms
      message: 'load-balancer-api-external: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "21599"
    uid: 3b3fa758-f23a-4280-9f1e-7bd66670d069
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:58:13Z"
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.44045ms
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 8.304382ms
      message: 'load-balancer-api-internal: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 4.661553ms
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 6.593188ms
      message: 'load-balancer-api-internal: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 4.427283ms
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 10.60424ms
      message: 'load-balancer-api-internal: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 4.625904ms
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 9.419597ms
      message: 'load-balancer-api-internal: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 4.977842ms
      message: 'load-balancer-api-internal: tcp connection to ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 6.313878ms
      message: 'load-balancer-api-internal: resolved host name ac883a59cb68949feaa6aac0b618f43a-d7c27ccad0f036c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-network-check-target-ip-10-0-133-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "22888"
    uid: 5dddcb06-b142-4da4-8701-2139d43864c2
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:59:13Z"
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.761µs
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:59:13Z"
    - latency: 1.278369ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 1.216275ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 1.789315ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 921.594µs
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 1.023444ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 1.278294ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-network-check-target-ip-10-0-134-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "22890"
    uid: 80a01915-3a15-4ae1-957d-0b5dafa343ca
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:59:13Z"
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.3616ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:59:13Z"
    - latency: 2.34475ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 2.297662ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 2.335057ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 2.274494ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 1.773781ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 2.569175ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-network-check-target-ip-10-0-143-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "22889"
    uid: defaaaf9-f81f-40ff-98a3-310127c90a28
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:59:13Z"
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.342905ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:59:13Z"
    - latency: 2.282229ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 1.945627ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 2.437826ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 2.222403ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 2.441653ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 2.312212ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:52:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-37.ec2.internal
      uid: d0a32b3f-eddf-4afb-a902-1e2936260a50
    resourceVersion: "21598"
    uid: 0b4a70b2-9c0a-4886-b5ca-b39026293b7a
  spec:
    sourcePod: network-check-source-685456655f-l89pb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:58:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.111646ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 1.696305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:58:13Z"
    - latency: 918.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 1.807414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:57:13Z"
    - latency: 1.103108ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 1.664612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:56:13Z"
    - latency: 978.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 2.082315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:55:13Z"
    - latency: 785.529µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:54:13Z"
    - latency: 1.772045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:54:13Z"
kind: List
metadata:
  resourceVersion: ""