apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "11501"
    uid: 215959c4-5d03-4d79-80d3-4eacb743709b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "22561"
    uid: 98ee0dab-137c-401c-92a3-6a8643687264
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:27:16Z"
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.684132ms
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 7.262571ms
      message: 'load-balancer-api-external: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 4.405312ms
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 7.277589ms
      message: 'load-balancer-api-external: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 8.639833ms
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 6.767707ms
      message: 'load-balancer-api-external: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 5.431009ms
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 7.465912ms
      message: 'load-balancer-api-external: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 7.308752ms
      message: 'load-balancer-api-external: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:23:16Z"
    - latency: 9.178215ms
      message: 'load-balancer-api-external: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:23:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "22562"
    uid: 884072e9-f009-4454-8381-23571a73c706
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:27:16Z"
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.667439ms
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 7.32229ms
      message: 'load-balancer-api-internal: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 4.368322ms
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 7.3037ms
      message: 'load-balancer-api-internal: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 8.673967ms
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 6.720603ms
      message: 'load-balancer-api-internal: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 5.450307ms
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 7.547232ms
      message: 'load-balancer-api-internal: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 7.301195ms
      message: 'load-balancer-api-internal: tcp connection to a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:23:16Z"
    - latency: 9.310809ms
      message: 'load-balancer-api-internal: resolved host name a6eab8d0fa0f34929a9f47f4002be702-896be319bfeed81e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:23:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-128-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "11499"
    uid: 86d8bb9d-b858-4d13-907d-54934600a642
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-129-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "11498"
    uid: 2298c969-bc38-41b3-9681-05d147349863
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-131-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "11500"
    uid: b21e66e1-6c28-4cde-875b-5e07c51a68c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:21:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-63.ec2.internal
      uid: af8859f7-2353-4e5f-b8e1-87cf266e3ed5
    resourceVersion: "22560"
    uid: 36742182-3c8e-497d-92ce-d973d84a0203
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tnxg9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:27:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 2.092892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:16Z"
    - latency: 959.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 2.055619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:16Z"
    - latency: 989.573µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 1.831399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:25:16Z"
    - latency: 942.895µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 1.867228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:24:16Z"
    - latency: 1.237852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:23:16Z"
    - latency: 1.89556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:23:16Z"
kind: List
metadata:
  resourceVersion: ""