apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "14464"
    uid: 37ded343-5482-4dd2-a16c-ea220bd052c6
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:50:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.359578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:50:36Z"
    - latency: 1.096926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 973.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 1.020197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 853.503µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 998.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 866.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:44:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "13970"
    uid: f4adae80-9681-4cad-a48f-ceafc5256563
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:49:36Z"
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.515887ms
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 9.717555ms
      message: 'load-balancer-api-external: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 4.326206ms
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 8.134461ms
      message: 'load-balancer-api-external: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 5.513086ms
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 7.239073ms
      message: 'load-balancer-api-external: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 5.556883ms
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 8.455662ms
      message: 'load-balancer-api-external: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 4.427478ms
      message: 'load-balancer-api-external: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 6.571352ms
      message: 'load-balancer-api-external: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:45:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "13971"
    uid: 670cf40a-8199-4848-9279-f809ef0c53da
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:49:36Z"
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.506877ms
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 9.767528ms
      message: 'load-balancer-api-internal: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 4.677187ms
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 8.102812ms
      message: 'load-balancer-api-internal: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 5.484403ms
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 7.347317ms
      message: 'load-balancer-api-internal: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 6.219101ms
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 8.415457ms
      message: 'load-balancer-api-internal: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 4.358839ms
      message: 'load-balancer-api-internal: tcp connection to a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 6.640946ms
      message: 'load-balancer-api-internal: resolved host name a91b0254eb2924c5098cb3662f7528a6-8c2053e4a78b0d47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:45:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-133-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "14462"
    uid: e3e1b069-3f04-4335-906e-d501e3965911
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:50:36Z"
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.645267ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:50:36Z"
    - latency: 2.007737ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 2.371467ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 2.561406ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 2.117001ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 2.728864ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 2.310129ms
      message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:44:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-140-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "14463"
    uid: 2302944d-a061-4699-93b9-0f22363d0090
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:50:36Z"
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.55641ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:50:36Z"
    - latency: 2.180998ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 2.065425ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 2.323866ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 2.10838ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 2.351007ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 2.317431ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:44:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-142-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "14461"
    uid: 2fe5d599-3372-4560-8e01-8aefbcc9bb8f
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:50:36Z"
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.658ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:50:36Z"
    - latency: 972.219µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 879.19µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 1.280611ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 849.545µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 1.494275ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 1.131893ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:44:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:43:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: b94ea309-8b00-4ec8-8e73-e8a83357cb63
    resourceVersion: "13969"
    uid: 2351c24c-fdd3-441a-8641-e5157d406846
  spec:
    sourcePod: network-check-source-65bdbbff45-7pqxg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:49:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.806µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 1.759432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:49:36Z"
    - latency: 792.503µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 1.712854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:48:36Z"
    - latency: 904.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 1.699964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:47:36Z"
    - latency: 1.017962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 2.110494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:46:36Z"
    - latency: 1.150073ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:45:36Z"
    - latency: 1.680568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:45:36Z"
kind: List
metadata:
  resourceVersion: ""