apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15728"
    uid: 4a958fb3-dac0-434c-9c9f-d35c4d39ee05
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:51:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:18Z"
    - latency: 1.048136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 1.537696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 877.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 809.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 996.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 1.079058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15313"
    uid: 8b0e361e-1f78-47d9-a790-2e8e8c99bdb4
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:50:18Z"
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.588373ms
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 11.861732ms
      message: 'load-balancer-api-external: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 5.429499ms
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 12.634699ms
      message: 'load-balancer-api-external: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 5.306769ms
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 7.330628ms
      message: 'load-balancer-api-external: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 5.145872ms
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 9.760297ms
      message: 'load-balancer-api-external: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 4.881005ms
      message: 'load-balancer-api-external: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 8.089816ms
      message: 'load-balancer-api-external: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15314"
    uid: 5556342c-b846-4f9d-8726-1f2f34c06929
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:50:18Z"
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.530266ms
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 11.952359ms
      message: 'load-balancer-api-internal: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 5.401877ms
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 12.778098ms
      message: 'load-balancer-api-internal: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 5.325421ms
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 7.183038ms
      message: 'load-balancer-api-internal: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 4.887878ms
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 9.826453ms
      message: 'load-balancer-api-internal: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 5.689606ms
      message: 'load-balancer-api-internal: tcp connection to af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 8.17189ms
      message: 'load-balancer-api-internal: resolved host name af3421189621c46f9b466301fbeac0a8-1a0c271c9aae0e55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-network-check-target-ip-10-0-134-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15726"
    uid: 3ac77374-be46-4092-b5e7-a4fbf0791282
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:51:18Z"
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.283791ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:18Z"
    - latency: 2.413902ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 2.55343ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 2.516348ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 2.122444ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 2.135012ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 2.401613ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-network-check-target-ip-10-0-134-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15725"
    uid: 988016c6-c468-4546-94cc-731249aeaee2
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:51:18Z"
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.27419ms
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:18Z"
    - latency: 1.029168ms
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 1.632528ms
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 916.433µs
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 836.44µs
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 1.263398ms
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 1.683086ms
      message: 'network-check-target-ip-10-0-134-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-network-check-target-ip-10-0-136-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15727"
    uid: 6f368a1b-c4d5-448f-b4ff-7d56ffb23815
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:51:18Z"
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.594122ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:51:18Z"
    - latency: 2.248938ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 1.983031ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 1.880855ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 1.753553ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 1.77968ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 1.964889ms
      message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T02:44:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-245.ec2.internal
      uid: 5dceb0ea-8a49-43f5-b433-d79770667987
    resourceVersion: "15312"
    uid: 2eefcb49-0d1e-48c3-9a46-6b668d393893
  spec:
    sourcePod: network-check-source-6f8b768455-67c5r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T02:50:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 722.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 2.205563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:50:18Z"
    - latency: 853.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 2.400559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:49:18Z"
    - latency: 848.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 1.675789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:48:18Z"
    - latency: 978.877µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 1.737714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:47:18Z"
    - latency: 1.072467ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T02:46:18Z"
    - latency: 1.473251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T02:46:18Z"
kind: List
metadata:
  resourceVersion: ""