apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14636"
    uid: b1c6756e-8794-497a-9044-21af5c355dc2
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:46:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:40Z"
    - latency: 1.26213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 1.452268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 1.22022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 882.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 941.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 953.13µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14274"
    uid: edcb9c17-c9e8-4bc8-9791-d99a55c139f7
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:40Z"
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.551441ms
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 11.948385ms
      message: 'load-balancer-api-external: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 4.522136ms
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 6.930151ms
      message: 'load-balancer-api-external: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 4.830317ms
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 8.029155ms
      message: 'load-balancer-api-external: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 3.859691ms
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 6.863022ms
      message: 'load-balancer-api-external: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 4.841746ms
      message: 'load-balancer-api-external: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 6.551844ms
      message: 'load-balancer-api-external: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14273"
    uid: bfb8c010-60c1-48df-856f-3c4b4459b4be
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:40Z"
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.515683ms
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 11.991236ms
      message: 'load-balancer-api-internal: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 3.324642ms
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 6.964001ms
      message: 'load-balancer-api-internal: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 4.861923ms
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 7.995557ms
      message: 'load-balancer-api-internal: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 4.000733ms
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 6.836892ms
      message: 'load-balancer-api-internal: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 4.828894ms
      message: 'load-balancer-api-internal: tcp connection to a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 6.572799ms
      message: 'load-balancer-api-internal: resolved host name a3fc7a70f1af64c10953be8c0efc2155-23c9b6e899c6c7cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-network-check-target-ip-10-0-131-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14634"
    uid: b1787043-adbc-4ea1-8fe7-d9a58bdbb525
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:46:40Z"
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.354238ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:40Z"
    - latency: 3.663981ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 2.297233ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 2.831905ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 2.339277ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 2.139098ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 2.767483ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-network-check-target-ip-10-0-135-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14633"
    uid: d64b9682-ba4f-4054-a8bb-98e9ca5a4e35
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:46:40Z"
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.346µs
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:40Z"
    - latency: 1.060282ms
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 1.02263ms
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 848.448µs
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 962.255µs
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 1.215562ms
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 1.253275ms
      message: 'network-check-target-ip-10-0-135-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-network-check-target-ip-10-0-137-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14635"
    uid: fc18f671-f25f-4394-a0b4-ad8952885ba8
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:46:40Z"
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.402147ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:40Z"
    - latency: 3.748586ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 2.366298ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 2.701098ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 2.383532ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 2.478047ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 2.684167ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:39:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-0.ec2.internal
      uid: 0dc83f02-e422-4fc8-8422-5efea934daba
    resourceVersion: "14272"
    uid: 75e31a3b-69f4-43b2-b271-a8393bcaee73
  spec:
    sourcePod: network-check-source-869dcfcdcd-lq8pm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.687294ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 3.814783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:45:40Z"
    - latency: 911.636µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 1.654017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:40Z"
    - latency: 1.149974ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 1.714053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:40Z"
    - latency: 740.992µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 1.673474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:40Z"
    - latency: 819.711µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:40Z"
    - latency: 1.608797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:40Z"
kind: List
metadata:
  resourceVersion: ""