apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "34820" uid: 9c9ad567-fa70-4e24-a6d5-099595eada8b spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T06:03:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.117µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 1.021317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 1.073134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 1.456805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 1.698863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:09:41Z" - latency: 1.034245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:08:41Z" - latency: 1.489391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:07:41Z" - latency: 1.543913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:06:41Z" - latency: 1.534598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:05:41Z" - latency: 1.361661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "35123" uid: c15af8f1-eee2-4581-bf89-26a45642c094 spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T06:02:41Z" message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.710694ms message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:14:41Z" - latency: 6.745284ms message: 'load-balancer-api-external: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:14:41Z" - latency: 16.943306ms message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 7.484366ms message: 'load-balancer-api-external: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:13:41Z" - latency: 14.887783ms message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 6.959162ms message: 'load-balancer-api-external: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:12:41Z" - latency: 18.224078ms message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 6.898863ms message: 'load-balancer-api-external: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:11:41Z" - latency: 18.097851ms message: 'load-balancer-api-external: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 7.055427ms message: 'load-balancer-api-external: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:10:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "35122" uid: 9513d159-3a22-448d-84c8-d48d5da2ecf7 spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T06:02:41Z" message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.482866ms message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:14:41Z" - latency: 6.734279ms message: 'load-balancer-api-internal: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:14:41Z" - latency: 13.313787ms message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 7.543562ms message: 'load-balancer-api-internal: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:13:41Z" - latency: 16.650828ms message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 6.909317ms message: 'load-balancer-api-internal: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:12:41Z" - latency: 15.5942ms message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 6.978905ms message: 'load-balancer-api-internal: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:11:41Z" - latency: 18.085619ms message: 'load-balancer-api-internal: tcp connection to aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 7.105932ms message: 'load-balancer-api-internal: resolved host name aa04f1eab01bf47998775d7bac28fea0-b5f4ba9e9203b633.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T07:10:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-network-check-target-ip-10-0-134-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "34817" uid: 575c3f31-ccd0-4c0d-97fb-671cf5ecc19e spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T06:03:41Z" message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.476277ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 1.256246ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 965.014µs message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 1.613851ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 1.848074ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:09:41Z" - latency: 1.409733ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:08:41Z" - latency: 1.584103ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:07:41Z" - latency: 882.112µs message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:06:41Z" - latency: 1.034107ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:05:41Z" - latency: 823.063µs message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-network-check-target-ip-10-0-136-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "34818" uid: 9e6adc5d-2dd9-4a35-b183-d645daeab370 spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T06:03:41Z" message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.490092ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 2.686348ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 2.276157ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 2.435576ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 2.343771ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:09:41Z" - latency: 2.341289ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:08:41Z" - latency: 2.858897ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:07:41Z" - latency: 2.534627ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:06:41Z" - latency: 2.159237ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:05:41Z" - latency: 4.63453ms message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-network-check-target-ip-10-0-137-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "34819" uid: d5e553dc-acf8-4852-9d2a-bbe8b2c9189d spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T06:03:41Z" message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.51917ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 2.097149ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 2.16375ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 2.48579ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 2.849415ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:09:41Z" - latency: 2.55095ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:08:41Z" - latency: 2.663221ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:07:41Z" - latency: 2.338391ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:06:41Z" - latency: 2.431854ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:05:41Z" - latency: 2.342504ms message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T05:56:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-19-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-19.ec2.internal uid: f3640923-8034-42c2-9a43-ee69f17660b5 resourceVersion: "35121" uid: 4297c2a1-56f0-4e6f-a96a-223b56b91d8c spec: sourcePod: network-check-source-6f78d59f99-2zbdk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T06:02:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10971ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:14:41Z" - latency: 1.776852ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T07:14:41Z" - latency: 1.016621ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:13:41Z" - latency: 1.94331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T07:13:41Z" - latency: 939.878µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:12:41Z" - latency: 1.735991ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T07:12:41Z" - latency: 887.966µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:11:41Z" - latency: 1.623616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T07:11:41Z" - latency: 1.178035ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T07:10:41Z" - latency: 1.868423ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T07:10:41Z" kind: List metadata: resourceVersion: ""