apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61523" uid: fd866626-ff0e-495d-b4f3-6ca9539c8c6c spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T16:27:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.1294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 1.125542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 1.678506ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 896.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 982.174µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 1.12805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:34Z" - latency: 1.612682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:34Z" - latency: 1.85368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:34Z" - latency: 1.022064ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:34Z" - latency: 932.222µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61525" uid: daff8b94-f181-4245-b5a2-c98975f39bf9 spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:26:34Z" message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.194627ms message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 8.299564ms message: 'load-balancer-api-external: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:02:34Z" - latency: 3.757528ms message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 9.354866ms message: 'load-balancer-api-external: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:01:34Z" - latency: 3.822016ms message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 8.795829ms message: 'load-balancer-api-external: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:00:34Z" - latency: 5.406382ms message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 7.756226ms message: 'load-balancer-api-external: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:34Z" - latency: 4.36205ms message: 'load-balancer-api-external: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 11.51272ms message: 'load-balancer-api-external: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61524" uid: 475d0f5a-e32d-4c94-8612-5e7c823b920f spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:26:34Z" message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.548727ms message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 8.39625ms message: 'load-balancer-api-internal: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:02:34Z" - latency: 3.743856ms message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 9.395737ms message: 'load-balancer-api-internal: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:01:34Z" - latency: 3.726418ms message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 8.842005ms message: 'load-balancer-api-internal: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:00:34Z" - latency: 5.416371ms message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 7.855566ms message: 'load-balancer-api-internal: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:34Z" - latency: 4.914655ms message: 'load-balancer-api-internal: tcp connection to ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 11.550523ms message: 'load-balancer-api-internal: resolved host name ab36543983eef4133a18ebfe3c4a5b02-66c6581781024fb4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-network-check-target-ip-10-0-134-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61520" uid: 283e0476-7735-42be-a970-327cbf69fd24 spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:27:34Z" message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.183748ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 2.337026ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 2.326147ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 2.21432ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 2.411382ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 2.515449ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:34Z" - latency: 2.314295ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:34Z" - latency: 2.258253ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:34Z" - latency: 2.24006ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:34Z" - latency: 1.980412ms message: 'network-check-target-ip-10-0-134-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-network-check-target-ip-10-0-136-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61521" uid: bc83e3ab-f905-47b2-9681-00cb616ed38c spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:27:34Z" message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.227516ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 2.182837ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 2.315604ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 2.169354ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 2.424049ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 2.535686ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:34Z" - latency: 2.192768ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:34Z" - latency: 2.204777ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:34Z" - latency: 1.987039ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:34Z" - latency: 2.210873ms message: 'network-check-target-ip-10-0-136-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-network-check-target-ip-10-0-141-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61519" uid: 33f8231c-7814-4635-ba2a-a4fbab37d110 spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:27:34Z" message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.879µs message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 899.47µs message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 1.038378ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 947.39µs message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 1.185262ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 1.700143ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:34Z" - latency: 1.806133ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:34Z" - latency: 981.377µs message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:34Z" - latency: 931.965µs message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:34Z" - latency: 1.200242ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-253-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-253.ec2.internal uid: e69364db-b80a-4a0a-841e-5b8f809920db resourceVersion: "61522" uid: c1525034-1e01-41b9-a199-93584a4587b9 spec: sourcePod: network-check-source-869dcfcdcd-lgdvx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T16:26:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:34Z" - latency: 1.729888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:02:34Z" - latency: 972.171µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:34Z" - latency: 2.219671ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:01:34Z" - latency: 905.136µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:34Z" - latency: 2.177165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:00:34Z" - latency: 1.313847ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:34Z" - latency: 1.754325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:34Z" - latency: 877.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:34Z" - latency: 1.878723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:34Z" kind: List metadata: resourceVersion: ""