apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "15312"
    uid: cfc436da-512d-4e7c-9d62-087719dd6bd7
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:57:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:57:26Z"
    - latency: 1.153081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 1.091457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 1.182925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 1.15262ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 1.072598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 828.121µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "14976"
    uid: 25b12c42-32ec-4df5-9578-8c13d07cd484
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:56:26Z"
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.022562ms
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 8.404381ms
      message: 'load-balancer-api-external: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 4.746908ms
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 8.01745ms
      message: 'load-balancer-api-external: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 4.56992ms
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 8.346005ms
      message: 'load-balancer-api-external: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 4.362764ms
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 8.860882ms
      message: 'load-balancer-api-external: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 3.114811ms
      message: 'load-balancer-api-external: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 6.825326ms
      message: 'load-balancer-api-external: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "14977"
    uid: 33d0d303-fad6-4efc-98a6-b852ae6220a0
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:56:26Z"
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.02303ms
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 8.476599ms
      message: 'load-balancer-api-internal: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 4.727943ms
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 8.065684ms
      message: 'load-balancer-api-internal: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 4.534577ms
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 8.370821ms
      message: 'load-balancer-api-internal: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 4.335819ms
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 8.910751ms
      message: 'load-balancer-api-internal: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 4.70518ms
      message: 'load-balancer-api-internal: tcp connection to a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 6.921977ms
      message: 'load-balancer-api-internal: resolved host name a78f56db035bc4a04962bd05d8f8d037-27ae96f700c25f99.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-network-check-target-ip-10-0-134-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "15310"
    uid: 5b5acc24-b1eb-4e6b-a707-c4655b4da5fc
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:57:26Z"
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.134243ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:57:26Z"
    - latency: 2.337103ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 2.187022ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 2.289084ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 2.158744ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 2.398659ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 2.248114ms
      message: 'network-check-target-ip-10-0-134-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-network-check-target-ip-10-0-136-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "15311"
    uid: 6dda1d17-4b04-4c71-94fc-76f1715f582c
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:57:26Z"
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.7346ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:57:26Z"
    - latency: 2.919919ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 2.165201ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 2.320273ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 2.160647ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 2.297687ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 1.848858ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-network-check-target-ip-10-0-138-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "15309"
    uid: c13e3789-19a1-42b4-bcc6-463934486ad4
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:57:26Z"
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.475µs
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:57:26Z"
    - latency: 1.386015ms
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 1.046493ms
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 925.758µs
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 801.447µs
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 900.287µs
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 1.062701ms
      message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-176-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-176.ec2.internal
      uid: c5341ece-cb72-4254-a765-b60085bea06d
    resourceVersion: "14975"
    uid: 94c52ba9-099f-4125-bd1b-277533aec609
  spec:
    sourcePod: network-check-source-6f8b768455-g5bz4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:56:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075109ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 2.040505ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:56:26Z"
    - latency: 973.405µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 2.049584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:55:26Z"
    - latency: 880.287µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 1.658824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:54:26Z"
    - latency: 1.103314ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 1.821155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:53:26Z"
    - latency: 852.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:52:26Z"
    - latency: 1.837105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:52:26Z"
kind: List
metadata:
  resourceVersion: ""