apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "23659"
    uid: 2baf3a1a-9eee-452e-9065-a901f57c61f6
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:01:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:01:42Z"
    - latency: 1.049895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 945.042µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 1.233417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 1.154698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 1.319547ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 1.597012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "22412"
    uid: 188db973-b37f-4685-a964-a082b1662c0e
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:00:42Z"
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.32508ms
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 6.570668ms
      message: 'load-balancer-api-external: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 5.046223ms
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 6.550799ms
      message: 'load-balancer-api-external: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 5.03175ms
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 6.613677ms
      message: 'load-balancer-api-external: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 5.676508ms
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 7.703301ms
      message: 'load-balancer-api-external: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 5.781573ms
      message: 'load-balancer-api-external: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 6.876295ms
      message: 'load-balancer-api-external: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "22411"
    uid: 36638d64-38ee-4001-af57-110ca7422fd9
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:00:42Z"
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.191081ms
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 6.597872ms
      message: 'load-balancer-api-internal: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 5.057087ms
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 6.571072ms
      message: 'load-balancer-api-internal: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 5.059545ms
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 6.573986ms
      message: 'load-balancer-api-internal: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 5.688962ms
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 7.682427ms
      message: 'load-balancer-api-internal: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 4.63356ms
      message: 'load-balancer-api-internal: tcp connection to a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 6.896832ms
      message: 'load-balancer-api-internal: resolved host name a8e5c1861ae274fd68942e2e7a1e63dc-5b6c82e91ed161d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:56:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-130-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "23657"
    uid: 19994b3f-2385-4f73-a796-15d981cadcc9
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:01:42Z"
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.672052ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:01:42Z"
    - latency: 2.536697ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 2.467126ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 2.425904ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 2.492077ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 2.574748ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 3.267037ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-132-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "23656"
    uid: 43ad97a5-3689-400e-af5b-9f10f1c1e9b0
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:01:42Z"
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.093µs
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:01:42Z"
    - latency: 1.420538ms
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 1.14455ms
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 831.082µs
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 949.491µs
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 927.075µs
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 1.195769ms
      message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-142-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "23658"
    uid: 2707d76c-99e8-4f92-9edd-53dfb6320d86
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:01:42Z"
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.70921ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:01:42Z"
    - latency: 2.398676ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 2.365324ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 2.398189ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 2.326812ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 2.385573ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 2.415112ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T03:54:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: 2bbfb0cf-2c66-4eab-8c71-2b9dfcae6707
    resourceVersion: "22410"
    uid: 7fc19053-9f8a-4599-830b-cb2588430cd1
  spec:
    sourcePod: network-check-source-685456655f-dgzqq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:00:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.376059ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 2.019823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:00:42Z"
    - latency: 1.144279ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 1.696123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:59:42Z"
    - latency: 1.271135ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 1.754374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:58:42Z"
    - latency: 2.289055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 1.988423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:57:42Z"
    - latency: 1.247362ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:56:42Z"
    - latency: 1.876695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:56:42Z"
kind: List
metadata:
  resourceVersion: ""