apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20918"
    uid: 817a683a-5832-470f-988c-df008ba3581a
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:09:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.165678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:09:28Z"
    - latency: 1.227285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 1.277403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 1.271265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 881.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 989.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 1.095079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20277"
    uid: 92dc0bd5-b854-45cd-ab49-bdd64444b7f4
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:08:28Z"
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.031475ms
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 11.627633ms
      message: 'load-balancer-api-external: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 5.952773ms
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 12.495312ms
      message: 'load-balancer-api-external: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 6.175397ms
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 15.386143ms
      message: 'load-balancer-api-external: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 5.665055ms
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 12.075959ms
      message: 'load-balancer-api-external: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 4.493275ms
      message: 'load-balancer-api-external: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 12.202444ms
      message: 'load-balancer-api-external: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20278"
    uid: 660617c9-3a4f-4e27-abd1-0db3c2726383
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:08:28Z"
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.195138ms
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 11.600593ms
      message: 'load-balancer-api-internal: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 3.615067ms
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 12.510383ms
      message: 'load-balancer-api-internal: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 6.189755ms
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 15.344346ms
      message: 'load-balancer-api-internal: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 5.667551ms
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 12.053069ms
      message: 'load-balancer-api-internal: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 3.034406ms
      message: 'load-balancer-api-internal: tcp connection to ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 12.215888ms
      message: 'load-balancer-api-internal: resolved host name ab1955fc7369f40d3985f3f20395ecda-56ac2b4a5ace587c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-network-check-target-ip-10-0-130-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20917"
    uid: c09dcdc2-7448-4b8b-b3ad-d4abe3f0f8ec
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:09:28Z"
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.612938ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:09:28Z"
    - latency: 2.549651ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 2.514351ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 2.641098ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 2.363688ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 2.111379ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 2.485719ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-network-check-target-ip-10-0-135-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20915"
    uid: 70f5741a-d1a7-4d60-b557-111441c9817d
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:09:28Z"
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.159048ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:09:28Z"
    - latency: 2.250328ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 2.167473ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 2.027486ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 2.943943ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 2.123359ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 2.392763ms
      message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-network-check-target-ip-10-0-141-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20916"
    uid: 6925b492-7a6a-4b8b-aa4a-98b187423df0
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:09:28Z"
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.393724ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:09:28Z"
    - latency: 889.591µs
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 854.758µs
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 933.188µs
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 969.674µs
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 897.796µs
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 1.192332ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-33.ec2.internal
      uid: d0d85e1c-69e0-4717-8b31-0a4e05363feb
    resourceVersion: "20276"
    uid: 06df8bf3-30f4-4f13-8839-afca679fbd2c
  spec:
    sourcePod: network-check-source-6f8b768455-z7xvw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:08:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.487661ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 1.944452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:08:28Z"
    - latency: 928.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 2.087598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:07:28Z"
    - latency: 1.15677ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 1.884028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:06:28Z"
    - latency: 821.203µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 1.643826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:28Z"
    - latency: 762.204µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:28Z"
    - latency: 1.85614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:28Z"
kind: List
metadata:
  resourceVersion: ""