apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14520"
    uid: ef6ece96-e132-492a-bada-06fee2c13018
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:06:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.01321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:06:57Z"
    - latency: 884.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 1.092584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 1.269125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 775.4µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 1.123729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 2.187711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:00:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14071"
    uid: 736594fc-9b00-4912-ad07-0c51597dc610
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:05:57Z"
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.923731ms
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 8.507444ms
      message: 'load-balancer-api-external: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 5.268672ms
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 10.938615ms
      message: 'load-balancer-api-external: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 4.942197ms
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 7.965542ms
      message: 'load-balancer-api-external: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 5.333897ms
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 9.241406ms
      message: 'load-balancer-api-external: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 5.743553ms
      message: 'load-balancer-api-external: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 7.228684ms
      message: 'load-balancer-api-external: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14070"
    uid: 21376d31-7e7f-49c2-a084-56fdc2c84ce6
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:05:57Z"
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.798873ms
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 8.544734ms
      message: 'load-balancer-api-internal: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 5.236157ms
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 10.825277ms
      message: 'load-balancer-api-internal: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 4.911353ms
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 7.942138ms
      message: 'load-balancer-api-internal: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 5.366712ms
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 9.204483ms
      message: 'load-balancer-api-internal: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 5.758363ms
      message: 'load-balancer-api-internal: tcp connection to a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 7.257895ms
      message: 'load-balancer-api-internal: resolved host name a3f406ddb1ab74bdeb78ed9acad5f55c-f3ddd87cb2f8f652.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-136-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14518"
    uid: 2ed3c608-3a33-4ce8-9e1e-a1eaaebc67b5
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:06:57Z"
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133596ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:06:57Z"
    - latency: 1.802685ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 2.15331ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 2.258678ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 1.874359ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 2.431226ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 2.415788ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:00:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-136-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14517"
    uid: 85111953-ecc2-4001-9b04-8798983628f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:06:57Z"
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.962µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:06:57Z"
    - latency: 1.079826ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 938.756µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 1.476599ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 772.094µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 1.367467ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 1.101074ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:00:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-143-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14519"
    uid: 8d6029e5-eeaf-44c0-aed8-2c693c3ba48a
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:06:57Z"
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.415074ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:06:57Z"
    - latency: 2.369622ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 2.50322ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 2.179401ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 2.147197ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 2.054291ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 2.607806ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:00:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T02:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: d6f10d3f-6a08-4b97-8205-a5b075b3681c
    resourceVersion: "14069"
    uid: e94d026d-f3e2-4978-ac6e-6b20652116d6
  spec:
    sourcePod: network-check-source-7cbc45fddc-8qqft
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:05:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 822.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 1.743127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:05:57Z"
    - latency: 866.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 1.767019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:04:57Z"
    - latency: 914.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 1.559592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:03:57Z"
    - latency: 905.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 1.84915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:02:57Z"
    - latency: 896.003µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:01:57Z"
    - latency: 1.544866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:01:57Z"
kind: List
metadata:
  resourceVersion: ""