apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "16070" uid: 0234e4c9-f7ab-4143-8200-0b51f2efefad spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T07:43:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.015812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:43:46Z" - latency: 1.139774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 975.923µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 1.034636ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 1.018942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 4.735558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 1.243855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:37:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "15657" uid: 23f31789-d919-48a3-b4dd-3770beced18a spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T07:42:46Z" message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.128919ms message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 7.944696ms message: 'load-balancer-api-external: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:42:46Z" - latency: 5.092434ms message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 8.430707ms message: 'load-balancer-api-external: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:41:46Z" - latency: 5.436118ms message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 8.469168ms message: 'load-balancer-api-external: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:40:46Z" - latency: 5.959356ms message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 8.385678ms message: 'load-balancer-api-external: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:39:46Z" - latency: 4.40762ms message: 'load-balancer-api-external: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 11.506937ms message: 'load-balancer-api-external: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:38:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "15656" uid: ed6aafdd-d10c-445a-a81a-4a85b2c8c580 spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T07:42:46Z" message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.16606ms message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 7.899882ms message: 'load-balancer-api-internal: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:42:46Z" - latency: 5.093405ms message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 8.404384ms message: 'load-balancer-api-internal: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:41:46Z" - latency: 5.475541ms message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 8.439905ms message: 'load-balancer-api-internal: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:40:46Z" - latency: 5.938802ms message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 8.352948ms message: 'load-balancer-api-internal: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:39:46Z" - latency: 3.526023ms message: 'load-balancer-api-internal: tcp connection to a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 11.486428ms message: 'load-balancer-api-internal: resolved host name a2889a65f139445a5b6ade9c26827b7b-99805cd8206895e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:38:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-network-check-target-ip-10-0-132-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "16069" uid: 3bafa1af-7b30-4fc5-aa03-840928ca758e spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:43:46Z" message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.284845ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:43:46Z" - latency: 2.268763ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 2.110663ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 2.215649ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 2.3954ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 5.740198ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 3.079007ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:37:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-network-check-target-ip-10-0-135-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "16067" uid: b56ef62f-304d-452d-9ffd-dc78a9a5b3f9 spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:43:46Z" message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.087928ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:43:46Z" - latency: 1.536151ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 1.033542ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 1.499246ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 1.241282ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 1.048714ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 1.236895ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:37:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-network-check-target-ip-10-0-137-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "16068" uid: 424bfadd-d881-4640-b8a9-3ed965dd1af8 spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:43:46Z" message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.338756ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:43:46Z" - latency: 2.413061ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 2.463328ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 2.687038ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 2.419752ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 3.958696ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 2.497877ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:37:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-12.ec2.internal uid: 19f687e1-537c-47d5-a416-81ae9c561079 resourceVersion: "15655" uid: 589eefe1-1d73-498c-a7db-0bbed040e531 spec: sourcePod: network-check-source-dbd9cf844-cfdl4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T07:42:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.94µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:42:46Z" - latency: 1.5069ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:42:46Z" - latency: 880.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:41:46Z" - latency: 1.637862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:41:46Z" - latency: 1.094665ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:40:46Z" - latency: 1.614671ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:40:46Z" - latency: 760.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:39:46Z" - latency: 1.612872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:39:46Z" - latency: 919.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:38:46Z" - latency: 4.854075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:38:46Z" kind: List metadata: resourceVersion: ""