apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "14314"
    uid: 46fe7683-26cd-4696-b603-3aeb4bb5cf89
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 1.029288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 1.016107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.111692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.029741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 941.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 918.759µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "13960"
    uid: 94ec24eb-8ea4-4d78-b19c-b7c8fb92e17b
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.343949ms
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 8.213144ms
      message: 'load-balancer-api-external: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 5.105148ms
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 13.918127ms
      message: 'load-balancer-api-external: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 5.815498ms
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 8.15184ms
      message: 'load-balancer-api-external: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 4.658716ms
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 8.868794ms
      message: 'load-balancer-api-external: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 3.753377ms
      message: 'load-balancer-api-external: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 7.589163ms
      message: 'load-balancer-api-external: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "13959"
    uid: e0efd022-5658-40f2-b53f-fefec76590d0
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.420681ms
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 8.236843ms
      message: 'load-balancer-api-internal: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 5.042204ms
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 13.892426ms
      message: 'load-balancer-api-internal: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 4.271275ms
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 8.124667ms
      message: 'load-balancer-api-internal: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 4.671002ms
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 8.839609ms
      message: 'load-balancer-api-internal: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 3.742513ms
      message: 'load-balancer-api-internal: tcp connection to ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 7.53849ms
      message: 'load-balancer-api-internal: resolved host name ac6bf468fd44c44cf9685d92f8ca7bfb-6f2ce6f60606e2fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-network-check-target-ip-10-0-128-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "14312"
    uid: 56aeda23-6de4-4935-9b30-fb0c2e47c295
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249255ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 1.999174ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 2.176528ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 2.117667ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 2.111266ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 2.294269ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 2.400305ms
      message: 'network-check-target-ip-10-0-128-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-network-check-target-ip-10-0-132-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "14310"
    uid: 1801961d-601a-4dc7-96b0-11ad25d90766
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 766.634µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 840.078µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 946.306µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 774.22µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 861.454µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 786.73µs
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.079443ms
      message: 'network-check-target-ip-10-0-132-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-network-check-target-ip-10-0-133-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "14311"
    uid: 310cf0ea-bb25-4d83-a3c6-5bd320be495d
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.877573ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 2.055515ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 1.741753ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.777929ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.827627ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 1.619497ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.678048ms
      message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-209-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-209.ec2.internal
      uid: 51a5206a-6262-4cbe-84db-4e1b7d324eb0
    resourceVersion: "13957"
    uid: 8d938c15-04ed-4c3c-bc7c-2245d4ed0b1f
  spec:
    sourcePod: network-check-source-685456655f-k72vs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.985µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 1.725655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 943.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.811673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 952.648µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.711963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.015404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 1.780906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 767.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.704826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
kind: List
metadata:
  resourceVersion: ""