apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "18781"
    uid: 9c7fafe1-9aac-4688-8dfc-c1849cdcaa12
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:46:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.251356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:46:44Z"
    - latency: 1.23214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:45:44Z"
    - latency: 1.320339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:44:44Z"
    - latency: 5.264895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:43:44Z"
    - latency: 1.076472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:42:44Z"
    - latency: 1.081166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:41:44Z"
    - latency: 1.14852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:40:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "23254"
    uid: 50f4928c-082b-494c-873d-032ace0af0ec
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:45:44Z"
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.92125ms
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 8.451443ms
      message: 'load-balancer-api-external: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 22.160934ms
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 7.303675ms
      message: 'load-balancer-api-external: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 16.943355ms
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 11.695024ms
      message: 'load-balancer-api-external: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 33.025258ms
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 17.908902ms
      message: 'load-balancer-api-external: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 16.57556ms
      message: 'load-balancer-api-external: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:47:44Z"
    - latency: 6.993182ms
      message: 'load-balancer-api-external: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:47:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "23255"
    uid: cfd3ea22-cb57-4d4e-b5b0-a41684816402
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:45:44Z"
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.927398ms
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 8.535961ms
      message: 'load-balancer-api-internal: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 16.63614ms
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 7.364363ms
      message: 'load-balancer-api-internal: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 18.553228ms
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 11.651903ms
      message: 'load-balancer-api-internal: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 16.640541ms
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 18.666458ms
      message: 'load-balancer-api-internal: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 16.598129ms
      message: 'load-balancer-api-internal: tcp connection to a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:47:44Z"
    - latency: 7.040363ms
      message: 'load-balancer-api-internal: resolved host name a03a8617a291f4be8bd601cfbb3ed85d-d75737b9ad33549c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:47:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-139-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "18778"
    uid: e54eeedf-126d-4600-8a2a-d24c0898cd26
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:46:44Z"
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 842.365µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:46:44Z"
    - latency: 820.621µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:45:44Z"
    - latency: 826.345µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:44:44Z"
    - latency: 7.239282ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:43:44Z"
    - latency: 1.205508ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:42:44Z"
    - latency: 1.042021ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:41:44Z"
    - latency: 1.555488ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:40:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-139-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "18780"
    uid: c1d0e1e9-5d01-48f3-8fe8-ae05351e833a
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:46:44Z"
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296902ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:46:44Z"
    - latency: 2.088884ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:45:44Z"
    - latency: 2.101544ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:44:44Z"
    - latency: 3.311823ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:43:44Z"
    - latency: 1.977767ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:42:44Z"
    - latency: 2.371927ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:41:44Z"
    - latency: 2.217584ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:40:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-141-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "18779"
    uid: fdf33201-dcaf-4e46-8f5b-530a0fbd14dc
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:46:44Z"
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.033159ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:46:44Z"
    - latency: 1.958532ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:45:44Z"
    - latency: 2.107611ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:44:44Z"
    - latency: 3.915192ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:43:44Z"
    - latency: 1.65459ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:42:44Z"
    - latency: 2.0554ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:41:44Z"
    - latency: 2.129776ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:40:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: d19869c7-cca2-401e-b84b-dea44e43bc21
    resourceVersion: "23253"
    uid: 9f95345f-45d7-4435-8f5d-3bbd381bc380
  spec:
    sourcePod: network-check-source-6f78d59f99-wxrt9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:45:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.345µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 1.760276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:51:44Z"
    - latency: 841.246µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 2.051455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:50:44Z"
    - latency: 1.153424ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 1.928317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:49:44Z"
    - latency: 1.002022ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 13.837778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:48:44Z"
    - latency: 1.064447ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:47:44Z"
    - latency: 1.8187ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:47:44Z"
kind: List
metadata:
  resourceVersion: ""