apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14350"
    uid: 848fce42-de4c-4535-beed-540239736156
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:50:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:39Z"
    - latency: 1.209333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 860.019µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 1.13889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 956.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 1.04578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 1.873136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14045"
    uid: 1cf8f0a8-f285-4e5f-91b1-86dcada1c1e0
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:49:39Z"
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.724711ms
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 8.538477ms
      message: 'load-balancer-api-external: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 4.960806ms
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 8.664813ms
      message: 'load-balancer-api-external: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 4.45172ms
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 9.900363ms
      message: 'load-balancer-api-external: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 5.366776ms
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 11.832852ms
      message: 'load-balancer-api-external: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 4.564412ms
      message: 'load-balancer-api-external: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 6.66179ms
      message: 'load-balancer-api-external: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14044"
    uid: ed0fddf6-daae-4d5f-a31a-6d49af70548a
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:49:39Z"
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.228901ms
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 8.481501ms
      message: 'load-balancer-api-internal: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 4.81963ms
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 8.635773ms
      message: 'load-balancer-api-internal: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 5.619269ms
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 9.762885ms
      message: 'load-balancer-api-internal: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 5.441564ms
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 11.776378ms
      message: 'load-balancer-api-internal: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 4.44886ms
      message: 'load-balancer-api-internal: tcp connection to a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 6.551565ms
      message: 'load-balancer-api-internal: resolved host name a5be1152985f54faaa49ffcd32d476eb-b9de4635cfab31aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-network-check-target-ip-10-0-131-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14347"
    uid: b4d7de4d-b1a0-4780-8587-0beae84743e1
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:50:39Z"
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.379µs
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:39Z"
    - latency: 899.887µs
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 1.134632ms
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 987.276µs
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 1.13459ms
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 896.524µs
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 2.658275ms
      message: 'network-check-target-ip-10-0-131-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-network-check-target-ip-10-0-131-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14349"
    uid: cfd5845e-a380-4383-9c80-a120931567ba
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:50:39Z"
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.689458ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:39Z"
    - latency: 2.378816ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 2.460532ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 2.146345ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 2.267373ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 2.321489ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 2.724915ms
      message: 'network-check-target-ip-10-0-131-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-network-check-target-ip-10-0-139-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14348"
    uid: 8914b6b6-b8ec-40e2-ae8a-c1917c9bb091
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:50:39Z"
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.120021ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:39Z"
    - latency: 2.211308ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 1.893339ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 2.308999ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 2.019426ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 2.20726ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 3.026546ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:43:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-219-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-219.ec2.internal
      uid: 9859f8f4-1cc6-4625-bf5e-5b13f5e26546
    resourceVersion: "14043"
    uid: 32c8927a-93c2-4cdd-a72c-e3b653cafc46
  spec:
    sourcePod: network-check-source-685456655f-lqznt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:49:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.542µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 1.819439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:39Z"
    - latency: 781.195µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 1.960823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:39Z"
    - latency: 1.144913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 1.785351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:39Z"
    - latency: 1.127581ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 2.034965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:39Z"
    - latency: 961.358µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:39Z"
    - latency: 1.768878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:39Z"
kind: List
metadata:
  resourceVersion: ""