apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "46304" uid: f76172bd-69d6-4243-9f60-e24c17e284f7 spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T03:28:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.015833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 1.129795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 1.25286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 1.166989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:46:01Z" - latency: 926.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:45:01Z" - latency: 1.122145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:44:01Z" - latency: 1.332605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:43:01Z" - latency: 857.182µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:42:01Z" - latency: 1.211632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:41:01Z" - latency: 931.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:40:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "48400" uid: 62c8db2b-ec0d-4dbf-a3b0-e59160bc7435 spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T03:27:01Z" message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.136585ms message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:51:01Z" - latency: 9.032559ms message: 'load-balancer-api-external: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:51:01Z" - latency: 4.830538ms message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:50:01Z" - latency: 7.606587ms message: 'load-balancer-api-external: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:50:01Z" - latency: 5.076545ms message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 10.21267ms message: 'load-balancer-api-external: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:49:01Z" - latency: 5.478471ms message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 7.673482ms message: 'load-balancer-api-external: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:48:01Z" - latency: 4.909144ms message: 'load-balancer-api-external: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 7.805108ms message: 'load-balancer-api-external: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:47:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "48399" uid: f023d8ef-89a0-49c5-85e2-800ef115d84f spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T03:27:01Z" message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.820679ms message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:51:01Z" - latency: 9.074729ms message: 'load-balancer-api-internal: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:51:01Z" - latency: 4.997236ms message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:50:01Z" - latency: 7.700558ms message: 'load-balancer-api-internal: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:50:01Z" - latency: 5.072333ms message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 10.347178ms message: 'load-balancer-api-internal: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:49:01Z" - latency: 5.446528ms message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 7.745118ms message: 'load-balancer-api-internal: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:48:01Z" - latency: 4.971961ms message: 'load-balancer-api-internal: tcp connection to a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 7.876418ms message: 'load-balancer-api-internal: resolved host name a9a168a6cea994357b01ca1f7ad43a8a-05ab570d20c40c05.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T03:47:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-network-check-target-ip-10-0-131-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "46302" uid: a1d628e8-f983-45da-8a77-394f892fb013 spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T03:28:01Z" message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.926213ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 2.038299ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 1.984682ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 1.8138ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:46:01Z" - latency: 1.695562ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:45:01Z" - latency: 2.06784ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:44:01Z" - latency: 2.019187ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:43:01Z" - latency: 2.091163ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:42:01Z" - latency: 2.040053ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:41:01Z" - latency: 1.852004ms message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:40:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-network-check-target-ip-10-0-136-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "46301" uid: 02e846e6-8563-4b8d-849c-995f595009af spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T03:28:01Z" message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.692µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 775.439µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 1.767704ms message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 939.87µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:46:01Z" - latency: 823.699µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:45:01Z" - latency: 799.633µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:44:01Z" - latency: 1.524667ms message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:43:01Z" - latency: 1.069295ms message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:42:01Z" - latency: 859.507µs message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:41:01Z" - latency: 1.32844ms message: 'network-check-target-ip-10-0-136-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:40:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-network-check-target-ip-10-0-141-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "46303" uid: 6ba9a553-476d-4195-949c-032e39f546a2 spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T03:28:01Z" message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.990258ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 2.092961ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 2.252443ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 2.037203ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:46:01Z" - latency: 2.183429ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:45:01Z" - latency: 1.93188ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:44:01Z" - latency: 2.426574ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:43:01Z" - latency: 1.95734ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:42:01Z" - latency: 2.139938ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:41:01Z" - latency: 2.196055ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:40:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T03:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-13-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-13.ec2.internal uid: cd91622e-1272-448e-ba20-a39ffd9d26ee resourceVersion: "48397" uid: 33526868-c01c-47f4-846b-680bd5ababc1 spec: sourcePod: network-check-source-dbd9cf844-mmcnw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T03:27:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.357µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:51:01Z" - latency: 2.013017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T03:51:01Z" - latency: 983.317µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:50:01Z" - latency: 1.856193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T03:50:01Z" - latency: 982.887µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:49:01Z" - latency: 1.733954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T03:49:01Z" - latency: 860.923µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:48:01Z" - latency: 1.945829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T03:48:01Z" - latency: 808.774µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T03:47:01Z" - latency: 1.912095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T03:47:01Z" kind: List metadata: resourceVersion: ""