apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "44951" uid: c19192e4-ac20-4cda-a177-33b6ccbf95e3 spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T17:46:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 1.366302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 1.06335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 884.044µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:04:30Z" - latency: 1.119892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:03:30Z" - latency: 1.06198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:02:30Z" - latency: 1.074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:01:30Z" - latency: 1.044723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:00:30Z" - latency: 961.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:59:30Z" - latency: 1.130851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "46963" uid: 2c16dac2-b78a-464a-80fd-88f9557a017d spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T17:45:30Z" message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.875069ms message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:09:30Z" - latency: 8.921597ms message: 'load-balancer-api-external: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:09:30Z" - latency: 10.7398ms message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:08:30Z" - latency: 15.234756ms message: 'load-balancer-api-external: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:08:30Z" - latency: 3.677473ms message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 9.925452ms message: 'load-balancer-api-external: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:07:30Z" - latency: 5.79756ms message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 8.371787ms message: 'load-balancer-api-external: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:06:30Z" - latency: 5.429695ms message: 'load-balancer-api-external: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 8.549651ms message: 'load-balancer-api-external: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:05:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "46962" uid: 516aa9e4-a457-4992-b8ce-120ea898fd53 spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T17:45:30Z" message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.883818ms message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:09:30Z" - latency: 8.852527ms message: 'load-balancer-api-internal: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:09:30Z" - latency: 4.936963ms message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:08:30Z" - latency: 15.151202ms message: 'load-balancer-api-internal: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:08:30Z" - latency: 3.574764ms message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 10.013545ms message: 'load-balancer-api-internal: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:07:30Z" - latency: 6.173918ms message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 8.41299ms message: 'load-balancer-api-internal: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:06:30Z" - latency: 5.101769ms message: 'load-balancer-api-internal: tcp connection to a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 8.578968ms message: 'load-balancer-api-internal: resolved host name a589337ece5374fc0b8a4a38753524f1-41a9b3f72a0980c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T18:05:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-129-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "44950" uid: 5ebe0643-90c2-453b-b743-ac15545113ef spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-21T17:46:30Z" message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319067ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 1.955339ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 2.052782ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 1.79162ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:04:30Z" - latency: 2.057586ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:03:30Z" - latency: 1.965402ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:02:30Z" - latency: 1.822263ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:01:30Z" - latency: 1.854594ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:00:30Z" - latency: 1.863363ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:59:30Z" - latency: 1.769076ms message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-134-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "44948" uid: 4dce054e-d44e-4ef7-a4ae-7f11323ae972 spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T17:46:30Z" message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.310839ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 868.011µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 1.266791ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 724.606µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:04:30Z" - latency: 947.319µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:03:30Z" - latency: 822.818µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:02:30Z" - latency: 1.408496ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:01:30Z" - latency: 976.607µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:00:30Z" - latency: 1.203682ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:59:30Z" - latency: 753.246µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-143-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "44949" uid: 7586a7d2-a88e-490b-a9fa-5a9959954b2d spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-21T17:46:30Z" message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.792132ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 2.13008ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 2.271361ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 1.99526ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:04:30Z" - latency: 2.127159ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:03:30Z" - latency: 2.311395ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:02:30Z" - latency: 2.223508ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:01:30Z" - latency: 2.377228ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:00:30Z" - latency: 2.062017ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:59:30Z" - latency: 2.111555ms message: 'network-check-target-ip-10-0-143-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T17:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T17:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 601fcff9-7004-492b-8d54-05d7813750d4 resourceVersion: "46961" uid: b3d7716a-548a-466f-9404-0dc6a694ee34 spec: sourcePod: network-check-source-8894fc9bd-ndw4b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T17:45:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:09:30Z" - latency: 1.95243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T18:09:30Z" - latency: 1.172235ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:08:30Z" - latency: 1.73079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T18:08:30Z" - latency: 812.32µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:07:30Z" - latency: 2.26775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T18:07:30Z" - latency: 903.638µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:06:30Z" - latency: 2.045693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T18:06:30Z" - latency: 1.268562ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T18:05:30Z" - latency: 1.814901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T18:05:30Z" kind: List metadata: resourceVersion: ""