apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "56445" uid: a85abab5-41e5-4774-8575-61e0178fa52d spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T22:47:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.228582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 792.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 937.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 1.131042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 1.167124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:11:29Z" - latency: 985.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:10:29Z" - latency: 1.839511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:09:29Z" - latency: 1.177569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:08:29Z" - latency: 1.702559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:07:29Z" - latency: 1.320384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:06:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "57675" uid: 6b37ff84-f10a-4da0-95f9-e4602cdbc717 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:46:29Z" message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.223663ms message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:16:29Z" - latency: 9.284248ms message: 'load-balancer-api-external: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:16:29Z" - latency: 5.578634ms message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 9.11001ms message: 'load-balancer-api-external: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:15:29Z" - latency: 4.664387ms message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 9.362174ms message: 'load-balancer-api-external: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:14:29Z" - latency: 5.07836ms message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 9.206362ms message: 'load-balancer-api-external: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:13:29Z" - latency: 4.526934ms message: 'load-balancer-api-external: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 6.266027ms message: 'load-balancer-api-external: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:12:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "57676" uid: b30ffedf-ae51-43ab-aa21-f45cedb80730 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:46:29Z" message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.006278ms message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:16:29Z" - latency: 9.349841ms message: 'load-balancer-api-internal: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:16:29Z" - latency: 5.566498ms message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 9.104328ms message: 'load-balancer-api-internal: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:15:29Z" - latency: 4.702327ms message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 9.353822ms message: 'load-balancer-api-internal: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:14:29Z" - latency: 4.715516ms message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 9.259978ms message: 'load-balancer-api-internal: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:13:29Z" - latency: 4.519608ms message: 'load-balancer-api-internal: tcp connection to a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 6.203609ms message: 'load-balancer-api-internal: resolved host name a51a84259752a460986cf0452fc262e3-3c18087ceb71db99.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T23:12:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-132-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "56443" uid: cea829f9-4c90-400b-b579-271c28a07157 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:47:29Z" message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.243907ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 1.793312ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 1.808878ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 2.000559ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 2.244687ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:11:29Z" - latency: 1.943446ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:10:29Z" - latency: 2.318354ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:09:29Z" - latency: 2.280057ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:08:29Z" - latency: 2.577322ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:07:29Z" - latency: 2.036849ms message: 'network-check-target-ip-10-0-132-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:06:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-135-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "56444" uid: 04eb9dd5-ecab-4175-bddb-f0edd3823662 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:47:29Z" message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.471µs message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 904.587µs message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 872.148µs message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 1.183333ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 1.027828ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:11:29Z" - latency: 985.94µs message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:10:29Z" - latency: 1.464068ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:09:29Z" - latency: 866.672µs message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:08:29Z" - latency: 1.63164ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:07:29Z" - latency: 1.436293ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:06:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-142-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "56442" uid: aeaef657-3ed8-4e86-bb0f-32e013c34eb7 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:47:29Z" message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.144664ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 1.708645ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 1.865583ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 1.801323ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 1.902424ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:11:29Z" - latency: 1.713519ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:10:29Z" - latency: 1.800299ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:09:29Z" - latency: 1.887405ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:08:29Z" - latency: 2.068872ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:07:29Z" - latency: 1.834952ms message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:06:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:40:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-80-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-80.ec2.internal uid: cbd24acb-a869-4e81-b588-5ae382e2d804 resourceVersion: "57674" uid: c7380040-94cc-40d6-8416-eab511772302 spec: sourcePod: network-check-source-989f8b8dc-j22gw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T22:46:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.945µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:16:29Z" - latency: 1.897292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T23:16:29Z" - latency: 919.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:15:29Z" - latency: 2.044395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T23:15:29Z" - latency: 905.131µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:14:29Z" - latency: 2.752349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T23:14:29Z" - latency: 854.551µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:13:29Z" - latency: 2.341429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T23:13:29Z" - latency: 851.567µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T23:12:29Z" - latency: 1.873666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T23:12:29Z" kind: List metadata: resourceVersion: ""