apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "85450" uid: ea0d5c17-3f05-4298-9e9c-9ba655851fb8 spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:09:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.649196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:49Z" - latency: 1.824378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:49Z" - latency: 1.029214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:49Z" - latency: 1.179303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 1.080744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 3.304352ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 842.374µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 1.090153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 1.5499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:57:49Z" - latency: 1.074345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:56:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "83121" uid: 4b9bd534-6e72-4fb9-b1aa-63fcbdb622b6 spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:08:49Z" message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.994606ms message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 9.733285ms message: 'load-balancer-api-external: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:02:49Z" - latency: 4.518352ms message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 9.026579ms message: 'load-balancer-api-external: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:01:49Z" - latency: 3.987513ms message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 19.709643ms message: 'load-balancer-api-external: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:00:49Z" - latency: 5.81691ms message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 8.78201ms message: 'load-balancer-api-external: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:59:49Z" - latency: 5.624836ms message: 'load-balancer-api-external: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 10.36936ms message: 'load-balancer-api-external: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:58:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "83122" uid: aa3cb184-099f-4a4d-babf-4dc143cf8d97 spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:08:49Z" message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.003721ms message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 9.761256ms message: 'load-balancer-api-internal: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:02:49Z" - latency: 4.617403ms message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 8.908336ms message: 'load-balancer-api-internal: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:01:49Z" - latency: 3.167398ms message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 19.823737ms message: 'load-balancer-api-internal: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:00:49Z" - latency: 5.820576ms message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 8.723762ms message: 'load-balancer-api-internal: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:59:49Z" - latency: 5.826ms message: 'load-balancer-api-internal: tcp connection to a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 10.443383ms message: 'load-balancer-api-internal: resolved host name a8a5151de232c4d17bcddb77f04ba192-8b6d346f41c3ac83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:58:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-133-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "85449" uid: 8ba6be20-771c-48c9-b8d3-f8531d51a9c5 spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:09:49Z" message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.998393ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:49Z" - latency: 2.362118ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:49Z" - latency: 2.385272ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:49Z" - latency: 2.379525ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 2.24023ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 10.169119ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 2.341107ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 2.390491ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 3.134158ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:57:49Z" - latency: 2.19272ms message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:56:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-135-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "85446" uid: e43c5e60-7b46-42c8-86ef-47da97d5ea6e spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:09:49Z" message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.115097ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:49Z" - latency: 1.090114ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:49Z" - latency: 832.181µs message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:49Z" - latency: 765.054µs message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 926.962µs message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 9.918971ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 1.370567ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 1.369007ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 2.003442ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:57:49Z" - latency: 1.540697ms message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:56:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-139-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "85447" uid: b488a563-282d-486c-9935-3e7aae9569f9 spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:09:49Z" message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.292416ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:49Z" - latency: 2.316701ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:49Z" - latency: 2.283037ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:49Z" - latency: 2.828504ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 2.629602ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 9.756105ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 2.400169ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 2.34403ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 3.036817ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:57:49Z" - latency: 2.375514ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:56:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:02:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-124.ec2.internal uid: e552513f-741f-40c7-addd-271e57ff0fd6 resourceVersion: "83119" uid: 2407ad79-0e54-4ff3-8ce2-4ee95cf9f1db spec: sourcePod: network-check-source-65bdbbff45-qjxkc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:08:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.108759ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:49Z" - latency: 2.097076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:02:49Z" - latency: 889.871µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:49Z" - latency: 2.24447ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:01:49Z" - latency: 1.921749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:49Z" - latency: 10.180876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:00:49Z" - latency: 1.303444ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:59:49Z" - latency: 1.840255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:59:49Z" - latency: 950.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:58:49Z" - latency: 2.442974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:58:49Z" kind: List metadata: resourceVersion: ""