apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "46810" uid: 1e4f6463-4d67-4111-a8f9-cd85dd8e5b26 spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T13:32:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.036868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 913.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 1.022078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 1.167478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:50:51Z" - latency: 1.770579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:49:51Z" - latency: 1.181112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:48:51Z" - latency: 931.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:47:51Z" - latency: 1.15552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:46:51Z" - latency: 1.2957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:45:51Z" - latency: 1.193744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "49005" uid: bd333cc5-4e47-499b-bdc6-765640f34370 spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T13:31:51Z" message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.511559ms message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:55:51Z" - latency: 6.664255ms message: 'load-balancer-api-external: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:55:51Z" - latency: 5.203177ms message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:54:51Z" - latency: 6.84252ms message: 'load-balancer-api-external: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:54:51Z" - latency: 4.647665ms message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 6.678622ms message: 'load-balancer-api-external: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:53:51Z" - latency: 4.672173ms message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 7.106086ms message: 'load-balancer-api-external: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:52:51Z" - latency: 4.353238ms message: 'load-balancer-api-external: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 6.407382ms message: 'load-balancer-api-external: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "49006" uid: 69d71713-62ab-4d8a-a5ee-4f1962b0620e spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T13:31:51Z" message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.487116ms message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:55:51Z" - latency: 6.729896ms message: 'load-balancer-api-internal: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:55:51Z" - latency: 5.078781ms message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:54:51Z" - latency: 6.910459ms message: 'load-balancer-api-internal: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:54:51Z" - latency: 4.61646ms message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 6.74555ms message: 'load-balancer-api-internal: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:53:51Z" - latency: 4.687743ms message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 7.130219ms message: 'load-balancer-api-internal: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:52:51Z" - latency: 4.331787ms message: 'load-balancer-api-internal: tcp connection to affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 6.45662ms message: 'load-balancer-api-internal: resolved host name affb78f60cad14e6fb0028e1ef483bdc-f103e07a3a87b1d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T13:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-network-check-target-ip-10-0-129-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "46809" uid: d0b7ca45-e2a8-4760-8ce4-a2d50aab8bea spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T13:32:51Z" message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.147429ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 2.015719ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 2.027133ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 1.973454ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:50:51Z" - latency: 2.06825ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:49:51Z" - latency: 2.043093ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:48:51Z" - latency: 1.899897ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:47:51Z" - latency: 1.909197ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:46:51Z" - latency: 2.026056ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:45:51Z" - latency: 2.034285ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-network-check-target-ip-10-0-137-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "46808" uid: c9eb380d-c163-49d9-b5d1-61dbab27a792 spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T13:32:51Z" message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.190797ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 2.170412ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 2.182871ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 2.469564ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:50:51Z" - latency: 2.164173ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:49:51Z" - latency: 2.103111ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:48:51Z" - latency: 2.375697ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:47:51Z" - latency: 2.060297ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:46:51Z" - latency: 2.379303ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:45:51Z" - latency: 2.070691ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-network-check-target-ip-10-0-138-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "46807" uid: e1b15e1a-9b78-4c49-b327-4c4582ae8710 spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T13:32:51Z" message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.167448ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 917.276µs message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 840.659µs message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 1.026276ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:50:51Z" - latency: 1.194169ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:49:51Z" - latency: 1.499624ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:48:51Z" - latency: 1.505094ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:47:51Z" - latency: 987.005µs message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:46:51Z" - latency: 1.350454ms message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:45:51Z" - latency: 943.242µs message: 'network-check-target-ip-10-0-138-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T13:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-212-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-212.ec2.internal uid: a1306d7e-fa45-43c3-aba1-d5d47a8f68b4 resourceVersion: "49004" uid: 4c0f6f61-33f0-4470-86c2-636b5c2f945c spec: sourcePod: network-check-source-989f8b8dc-c7tkn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T13:31:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:55:51Z" - latency: 2.144251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T13:55:51Z" - latency: 912.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:54:51Z" - latency: 1.742566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T13:54:51Z" - latency: 1.077243ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:53:51Z" - latency: 2.161078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T13:53:51Z" - latency: 1.234827ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:52:51Z" - latency: 1.689527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T13:52:51Z" - latency: 990.858µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T13:51:51Z" - latency: 2.026819ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T13:51:51Z" kind: List metadata: resourceVersion: ""