apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "26143" uid: 46bab90a-ab6d-4061-8aec-2ad480626870 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T14:41: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.137228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:49Z" - latency: 900.269µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:49Z" - latency: 827.15µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 741.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 1.042435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 1.102081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 1.150733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 821.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:49Z" - latency: 996.097µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:49Z" - latency: 914.972µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "24948" uid: e6b021e0-d7a4-4a32-a35e-dbe46e0e1114 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:40:49Z" message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.033669ms message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 10.339882ms message: 'load-balancer-api-external: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:49Z" - latency: 5.536785ms message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 11.137583ms message: 'load-balancer-api-external: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:49Z" - latency: 5.468161ms message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 10.141227ms message: 'load-balancer-api-external: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:49Z" - latency: 5.022404ms message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 12.38562ms message: 'load-balancer-api-external: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:43:49Z" - latency: 5.872768ms message: 'load-balancer-api-external: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 9.654985ms message: 'load-balancer-api-external: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:42:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "24947" uid: 8243316d-49e2-436c-a68c-6f6266dd1a77 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:40:49Z" message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.171167ms message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 10.246462ms message: 'load-balancer-api-internal: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:49Z" - latency: 5.515501ms message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 11.073512ms message: 'load-balancer-api-internal: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:49Z" - latency: 3.967603ms message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 10.094177ms message: 'load-balancer-api-internal: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:49Z" - latency: 5.05876ms message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 12.27454ms message: 'load-balancer-api-internal: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:43:49Z" - latency: 5.862833ms message: 'load-balancer-api-internal: tcp connection to a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 9.638433ms message: 'load-balancer-api-internal: resolved host name a7578e2dac98b4325bc2f54633185952-7e8a69f3291ea50c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:42:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-135-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "26140" uid: 8b2534b4-e191-491d-be44-a7242d6a3dd6 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:41:49Z" message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.847µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:49Z" - latency: 1.262835ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:49Z" - latency: 1.087492ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 1.132257ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 855.431µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 733.594µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 1.243138ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 934.47µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:49Z" - latency: 826.895µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:49Z" - latency: 971.983µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-136-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "26142" uid: 080da17f-73f5-47aa-862a-9019648cd797 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:41:49Z" message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.162149ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:49Z" - latency: 2.233299ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:49Z" - latency: 2.357119ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 1.705133ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 2.084268ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 2.002406ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 2.239839ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 2.089951ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:49Z" - latency: 2.120505ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:49Z" - latency: 2.002301ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-142-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "26141" uid: c61c5ecf-5fe1-4b65-b966-3de470377329 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:41:49Z" message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.704711ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:49Z" - latency: 1.594432ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:49Z" - latency: 1.7564ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 1.735462ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 1.867913ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 1.65543ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 1.806948ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 1.717192ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:49Z" - latency: 2.013677ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:49Z" - latency: 2.028172ms message: 'network-check-target-ip-10-0-142-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:34:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 8caab949-0650-441f-9a24-d16e1b01d8fd resourceVersion: "24946" uid: a0afea25-25dc-4260-a6b2-d190077451c8 spec: sourcePod: network-check-source-989f8b8dc-9bv4b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T14:40:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:49Z" - latency: 1.77205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:49Z" - latency: 912.411µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:49Z" - latency: 2.060414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:49Z" - latency: 731.587µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:49Z" - latency: 2.026451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:49Z" - latency: 786.132µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:49Z" - latency: 2.133791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:43:49Z" - latency: 816.853µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:49Z" - latency: 1.576108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:42:49Z" kind: List metadata: resourceVersion: ""